<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>cosmotic</author><text>Can confirm. I just spent many hours trying to diagnose why an API was timing out. Turns out Snort blocked the IP address of the certificate authority which chrome was secretly using to verify the API&amp;#x27;s certificate. My local machine had the verification cached but the docker container I was using did not. No indication of what was going on in the top-level network tools; I had to use the hard-to-find network diagnostics recorder in Chrome to even realize chrome was connecting to the certificate authority.</text><parent_chain><item><author>yabones</author><text>To any NIDS newbies out there... Please don&amp;#x27;t deploy this in-line. Ever. You should always have your IDS out-of-band. Software like Snort is great for detecting threats, but if you block every &amp;quot;threat&amp;quot; you&amp;#x27;re going to have a bad time. Not to disparage the quality of their rulesets, they are very high quality, but there absolutely will be false positives. I&amp;#x27;ve spent many evenings and weekends troubleshooting IPS problems, 0&amp;#x2F;10 cannot recommend.&lt;p&gt;The best option is to mirror all traffic from switches directly to capture boxes where the detection and logging happens. This should be sent to a central system that has a full picture of the network and traffic patterns. That central system should be the one making the decisions, and it should be very smart. Automatic firewall rules should be close to the source, and shutdown switchports should be close to the client.&lt;p&gt;For safe IPS operation there needs to be several layers of filters, not just a list of &amp;quot;allowed rule IDs&amp;quot;. This is the sort of project that takes at least a year to fully roll out - it&amp;#x27;s not the kind of thing a &amp;quot;security whiz&amp;quot; can set up in an afternoon.&lt;p&gt;At best, it can be a very useful diagnostic, logging, and threat detection tool. At worst, it can cause very difficult to predict and troubleshoot network problems.</text></item></parent_chain></comment><story><title>Snort – Network Intrusion Detection and Prevention System</title><url>https://www.snort.org/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>nubb</author><text>great comment. thing i’d add for folks who want to play with this, follow this setup exactly and turn every rule on but don’t perform any blocking. then review the logs and dial back unnecessary rules. very “fun” exercise in a lab for a student xD</text><parent_chain><item><author>yabones</author><text>To any NIDS newbies out there... Please don&amp;#x27;t deploy this in-line. Ever. You should always have your IDS out-of-band. Software like Snort is great for detecting threats, but if you block every &amp;quot;threat&amp;quot; you&amp;#x27;re going to have a bad time. Not to disparage the quality of their rulesets, they are very high quality, but there absolutely will be false positives. I&amp;#x27;ve spent many evenings and weekends troubleshooting IPS problems, 0&amp;#x2F;10 cannot recommend.&lt;p&gt;The best option is to mirror all traffic from switches directly to capture boxes where the detection and logging happens. This should be sent to a central system that has a full picture of the network and traffic patterns. That central system should be the one making the decisions, and it should be very smart. Automatic firewall rules should be close to the source, and shutdown switchports should be close to the client.&lt;p&gt;For safe IPS operation there needs to be several layers of filters, not just a list of &amp;quot;allowed rule IDs&amp;quot;. This is the sort of project that takes at least a year to fully roll out - it&amp;#x27;s not the kind of thing a &amp;quot;security whiz&amp;quot; can set up in an afternoon.&lt;p&gt;At best, it can be a very useful diagnostic, logging, and threat detection tool. At worst, it can cause very difficult to predict and troubleshoot network problems.</text></item></parent_chain></comment><story><title>Snort – Network Intrusion Detection and Prevention System</title><url>https://www.snort.org/</url></story>