Repository navigation
Reliable way to alert/log nmap scans on a network? #16334
Replies: 2 comments
|
There should be a bunch of Suricata rules for NMAP in Detections, have you tried searching in Detections for "nmap"? A lot are disabled by default. |
|
Adding to what @cm-ops said: enabling the nmap rules in Detections is worth doing, but signature rules alone won't give you a consistent alert, and the variation you're seeing is expected rather than a misconfiguration. Those rules match specific things nmap puts on the wire: the NSE HTTP User-Agent, OS detection probes ( For something consistent, alert on the behaviour (one source touching many ports in a short time) instead of on the tool. 1. A threshold rule in SuricataCreate a custom Suricata detection in Detections:
Tune 2. Validate it with Zeek dataBefore trusting the rule, run a test scan and look at the Zeek With both in place you get the specific nmap signatures (useful context about how someone scanned) plus one reliable alert that something is scanning. |
Uh oh!
There was an error while loading. Please reload this page.
With my SO 3.3 grid, I'm working on trying to find a consistent way to alert on nmap scans on my network. I've looked through Suricata rules when running scans, but depending on what type of server is scanned, there are different varied logs that return. For a simple scan on a section of my network, I get these group of rules.
Is there a more consistent way to alert on a scan, or are there any other services/tools that could be implemented?
All reactions