Nmap
Nmap is the default answer to 'what is running on that host?', so read its output past -sV. Expect questions on port states, scan-type choice and what a scan looks like to a defender.
on this pageshowhide
explore
- Host Discovery6 questions
- Scan Types5 questions
- Port & Service Detection6 questions
- OS Fingerprinting5 questions
- Timing & Performance6 questions
- NSE Scripting6 questions
questions
page 2 of 2What does an Nmap -O probe round look like in the target's firewall and sensor logs, and what does a result expose about an Internet-facing host?
basics
~20 sA round is about sixteen crafted TCP, ICMP and UDP probes from one source in a short burst, repeated if nothing matches. It shows in firewall and sensor logs, not application logs, and exposes the device class and OS family.
Your web tier's Server header exposes nginx/1.18.0 to Nmap -sV; why is trimming the version a weak control, and what do you do instead?
basics
~20 sTrimming removes a label, not the exposure: Nmap's database still recognises a bare nginx header, other responses may carry the version, and the flaw stays. Patch, limit exposure, and use your own authorised -sV scans to check the inventory.
What do Nmap's -f and --mtu options send, and what does a defender's firewall or sensor see and do about those tiny IP fragments?
basics
~20 s-f splits probes into IP fragments of eight bytes or less after the IP header; --mtu sets a multiple of eight. A defender sees bursts of tiny fragments from one source; a firewall or sensor that reassembles them inspects whole packets.
How does a defender recognise a slow Nmap scan that touches one port every five minutes for days, and what can an empty log not prove?
basics
~20 sA slow scan shows as one source touching many distinct ports or hosts at a steady pace, so count them per source over hours or days, not seconds. An empty log proves only what the control logged, sampled and kept.
showing 31–34 of 34