312-50V11 · Question #179
An attacker is using nmap to do a ping sweep and a port scanning in a subnet of 254 addresses. In which order should he perform these steps?
The correct answer is C. First the ping sweep to identify live hosts and then the port scan on the live hosts. This way he. Efficient reconnaissance requires identifying live hosts via ping sweep before running a port scan, avoiding wasted effort on inactive addresses.
Question
An attacker is using nmap to do a ping sweep and a port scanning in a subnet of 254 addresses. In which order should he perform these steps?
Options
- AThe sequence does not matter. Both steps have to be performed against all hosts.
- BFirst the port scan to identify interesting services and then the ping sweep to find hosts
- CFirst the ping sweep to identify live hosts and then the port scan on the live hosts. This way he
- DThe port scan alone is adequate. This way he saves time.
How the community answered
(38 responses)- A3% (1)
- B8% (3)
- C87% (33)
- D3% (1)
Why each option
Efficient reconnaissance requires identifying live hosts via ping sweep before running a port scan, avoiding wasted effort on inactive addresses.
Performing both steps against all hosts regardless of order wastes resources by port scanning addresses that are not alive.
Port scanning before a ping sweep means scanning potentially dead hosts, which is inefficient and generates unnecessary traffic.
Performing a ping sweep first narrows the target list to only live hosts, which significantly reduces the time and noise generated by the subsequent port scan. Port scanning all 254 addresses when many may be down wastes time and increases detection risk. Scanning only confirmed live hosts is the standard efficient reconnaissance workflow.
A port scan alone against all 254 addresses is slower than first filtering live hosts, and may miss hosts blocking port probes but responding to ICMP.
Concept tested: Nmap reconnaissance ordering - ping sweep then port scan
Source: https://nmap.org/book/man-host-discovery.html
Topics
Community Discussion
No community discussion yet for this question.