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 5 of 5
Consolidating and deduplicating findings
1 min read
Raw output overcounts. The same CVE on one host can be reported once per open port and again by a second scanner's plugin.
Before a number is reported, results are consolidated across tools and deduplicated to unique vulnerability-per-asset pairs, so the total counts distinct conditions rather than repeated detections. Without this, totals rise and fall with tool coverage, and trend lines track scanning changes instead of remediation.
Example: one host runs a vulnerable service on 3 ports and two scanners each flag it on all 3. That is 3 x 2 = 6 detections but 1 finding for that host. Report the 1, and keep the 6 detections attached as supporting evidence for the owner.
Consolidation must not erase real instances. A vulnerable serialization library on 63 hosts is best represented as one library defect with 63 affected instances, traced through the software inventory to the builds that bundle it, with each host still closed by its own rescan.
Fourteen SQL injection findings across six in-house applications that share one CWE weakness class are not duplicates: each is its own code path. The cluster points to a shared development practice, so the durable fix adds secure coding standards and pipeline checks on top of the fourteen fixes.
Check yourself
1. A monthly report counts 4,812 open findings. Review shows that the same CVE on one host is counted once per open port, and counted again from a second scanner's plugin for the same condition. What must be done before the number is reported?
2. Consolidated results list fourteen distinct findings across six in-house applications. They differ in location and parameter, but all fourteen map to the same weakness class, improper neutralization of special elements used in an SQL command. What does that pattern indicate?
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 →