Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I know I'm getting way too many and want to optimize, but I don't want to optimize too much. How many alerts/day should I try to get it down to?
I think your aim should not be to bring the amount of alerts down (quantity) but what it trips on (quality).
First prune rulesets that you don't need (anything P2P, etc, etc). Log for a while. Then assess which services are exposed to world and should need watching, then gather statistics to see what it trips on. Correlate stats with services and prune rules further (MS-.*, Solaris, Websphere). Then add a BPF filter for services that need watching but are accessed from "trusted" ranges if it trips on that. Log for a while. Search logs for false positives and also see threshold.conf for alert/warn ratios.
I think your aim should not be to bring the amount of alerts down (quantity) but what it trips on (quality).
First prune rulesets that you don't need (anything P2P, etc, etc). Log for a while. Then assess which services are exposed to world and should need watching, then gather statistics to see what it trips on. Correlate stats with services and prune rules further (MS-.*, Solaris, Websphere). Then add a BPF filter for services that need watching but are accessed from "trusted" ranges if it trips on that. Log for a while. Search logs for false positives and also see threshold.conf for alert/warn ratios.
Thanks! I did my first batch of pruning and am letting it run a while now.
Can you give an example of one of the rules I should be concerned about if I see?
Either from Emerging Threats or one of the Snort VRT rules.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Apache, php, mysql, ssh, pop, exim
