An enterprise security team deploys an automated vulnerability scanner to conduct network-based discovery across a newly created subnet housing microservices. Although monitoring tools verify that the microservices are online and actively serving traffic, the scanner's report indicates zero active hosts were discovered on the target subnet. Which of the following best explains why the vulnerability scanner failed to identify the active hosts?
- Network security controls or host firewalls on the target subnet are blocking the initial ICMP echo requests and TCP/UDP discovery probes.Answer
- BThe scanner was configured with a non-credentialed account, preventing it from binding to container runtime APIs during the discovery phase.
- CAn inline Web Application Firewall (WAF) compensated for network vulnerabilities by encrypting internal container-to-container communication.
- DThe vulnerability scanner automatically suppresses discovery alerts whenever targeted systems use dynamic IP address allocations.
Answer
The vulnerability scanner failed to identify active hosts because network security controls or host firewalls on the target subnet dropped the ICMP echo requests and initial TCP/UDP discovery probes used during host identification.
Vulnerability scanners initiate assessments with a host discovery phase using ICMP echo requests and TCP/UDP probes to identify active targets. When firewalls or network access control lists (ACLs) silently drop these discovery packets, the scanner concludes that no hosts are live at those IP addresses, resulting in a scan report showing zero active systems despite services running.
Step-by-Step Solution
Key Concept
Host Discovery Suppressions and Firewall Interferences in Vulnerability Scanning