Detect network reconnaissance and port scanning using Suricata and Snort IDS signatures, threshold-based detection rules, and traffic anomaly analysis to identify Nmap, Masscan, and custom scanning activity. Use when detecting network reconnaissance and port scanning using suricata and snort.
Detect network reconnaissance and port scanning using Suricata and Snort IDS signatures, threshold-based detection rules, and traffic anomaly analysis to identify Nmap, Masscan, and custom scanning activity. Use when detecting network reconnaissance and port scanning using suricata and snort.
Network scanning is typically the first phase of an attack, where adversaries enumerate live hosts, open ports, running services, and OS versions using tools like Nmap, Masscan, ZMap, and custom scanners. Detecting this reconnaissance activity provides early warning of potential attacks. IDS/IPS systems like Suricata and Snort can identify scanning through signature-based detection (matching known scanner packet patterns), threshold-based detection (counting connection attempts over time), and anomaly detection (identifying unusual traffic patterns). This skill covers writing and deploying IDS signatures for scan detection, configuring threshold-based alerting, and correlating scan activity with downstream attack indicators.
When to Use
Trigger phrases:
"detecting network scanning with ids signatures"
"Detect network reconnaissance and port scanning using Suricata and Snort IDS sig"
When investigating security incidents that require detecting network scanning with ids signatures
When building detection rules or threat hunting queries for this domain
When SOC analysts need structured procedures for this analysis type
When validating security monitoring coverage for related attack techniques
Prerequisites
Suricata 7.0+ or Snort 3.0+ deployed in IDS/IPS mode
Network TAP or SPAN port for traffic visibility
Emerging Threats ruleset enabled
Logging infrastructure for alert analysis (ELK Stack, Splunk)
Baseline understanding of normal network traffic patterns
Core Concepts
This section covers core concepts for detecting network scanning with ids signatures.
Ensure all prerequisites are met before proceeding
Follow the documented workflow steps in sequence
Record results and any anomalies encountered during this phase
Scanning Techniques and Detection Indicators
Scan Type
Nmap Flag
Packet Characteristics
Detection Method
TCP SYN
-sS
SYN flag only, no completion
SYN without SYN/ACK response pattern
TCP Connect
-sT
Full 3-way handshake
Multiple connections from single source
TCP FIN
-sF
FIN flag only
FIN to closed port (RST response)
TCP Xmas
-sX
FIN+PSH+URG flags
Unusual flag combination
TCP NULL
-sN
No flags set
Zero-flag TCP packet
UDP Scan
-sU
UDP to many ports
ICMP port unreachable responses
ACK Scan
-sA
ACK flag only (firewall probing)
Unsolicited ACK packets
SYN/ACK Scan
Custom
SYN+ACK without prior SYN
State violation
OS Fingerprint
-O
Unusual TCP options/window sizes
Specific option combinations
Version Detect
-sV
Service probe strings
Known probe payloads
Nmap Timing Templates
Template
Nmap Flag
Speed
Detection Difficulty
Paranoid
-T0
1 probe/5 min
Very difficult
Sneaky
-T1
1 probe/15 sec
Difficult
Polite
-T2
1 probe/0.4 sec
Moderate
Normal
-T3
Default parallelism
Easy
Aggressive
-T4
Parallel, 1.25s timeout
Very easy
Insane
-T5
Maximum parallelism
Trivial
Workflow
Scope the task — define objectives, boundaries, and success criteria
Gather information — collect all necessary data and context before proceeding
Execute the core workflow — follow the domain-specific steps methodically
Validate results — verify outputs against expected outcomes or baselines
Document findings — record results, anomalies, and recommendations