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 6 · Lesson 2 of 5
False negatives, failed credentials and stale plugin feeds
1 min read
A false negative is a real exposure the scan did not report. It is the more serious defect because a false positive at least appears in the queue and gets removed by validation, while a false negative is never triaged, never tracked and quietly makes the program claim coverage it does not have.
The exam rarely says false negative in the stem. Instead it shows a clean result next to a detail that undermines it, and asks what the clean result means.
- Credential failures: if authentication worked on only some hosts, the rest were checked only for what a network probe sees, with no visibility into patches or local settings.
- Stale detection content: a scanner can only find what its plugin feed knows, so anything disclosed since the last update is invisible and reports issued meanwhile understate exposure.
- Incomplete coverage: hosts outside scope, offline or behind a filtering device produce silence that looks exactly like a clean host.
Example: a subnet of 40 servers shows no critical findings, and the summary says authentication succeeded on 12. Only 12 / 40 = 30% of the subnet had patch visibility, so the correct reading is that 28 servers were never really assessed.
Fix the credentials and rescan; do not publish the clean result as evidence of health, and do not close the coverage question with a single access-control ticket.
Check yourself
1. A scan of a 50-host database subnet returns no critical findings. The report summary shows that credential authentication succeeded on 9 hosts and failed on 41, and that those 41 were assessed from the network only. What should the analyst conclude?
2. An analyst discovers that the scanner's vulnerability plugin feed was last updated seven months ago, and that several quarterly reports were issued and signed off during that period. What does this do to those reports?
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 →