Chapters0/54 ▾
- 1.Architecture & Log Sources0/5
- 2.Indicators of Malicious Activity0/5
- 3.Investigation Tools & Threat Hunting0/5
- 4.Process Improvement, Automation & AI0/5
- 5.Vulnerability Scanning Methods0/5
- 6.Analyzing Scan Output0/5
- 7.Prioritization, Mitigation & Controls0/5
- 8.Attack Frameworks & the Response Process0/5
- 9.Incident Response Techniques0/5
- 10.Vulnerability Reporting & Communication0/5
- 11.Incident Reporting & Metrics0/4
Chapter 5 · Lesson 3 of 5
Scanner placement: internal, external and what sits in between
1 min read
A scan result describes a path, not only a host. An external scan from the internet measures the attack surface an outside attacker can reach today. An internal scan from the same subnet measures what an insider, or an attacker who has already bypassed the perimeter, would find.
When a firewall allows only HTTPS inbound, the external scan reporting one service and the internal scan reporting three are both correct, and filtering is the expected reason they differ. The exam wants you to keep both views rather than call one of them a false result.
The same logic explains many empty reports. An access list between a core scanner and a branch segment drops the probes, and every branch host looks closed even though staff use file and print services on them all day.
An inline prevention system may classify the scanner as an attacker halfway through a run and block it, leaving the rest of the hosts marked unreachable. In both cases the silence measures the network device, not the hosts.
- Fix a filtered path by placing a scanner inside the segment or by an agreed exception for the scanner's traffic.
- Record a truncated run as partial and repeat it; do not turn prevention off across the whole estate.
- Raising the scan rate to beat the prevention system, or reading a blocked segment as hardened, are classic wrong answers.
Check yourself
1. A perimeter firewall permits only tcp/443 to a web server, which also listens internally on tcp/22 and tcp/1433. A scanner on the server's own subnet reports all three services; a scanner hosted outside the network reports only the HTTPS service. Which conclusion is correct?
2. A scanner in the datacenter core reports every host in a remote branch segment as having no open ports and no findings, although staff there use file and print services on those hosts all day. What is the most likely explanation, and the correct fix?
Facts checked 2026-11-15 · Sources: CompTIA: CySA+ (CS0-004) certification and exam objectives, NIST SP 800-115: Technical Guide to Information Security Testing and Assessment
CompTIA CySA+ cheat sheet: every key fact on one page →