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 10 · Lesson 5 of 5
Credibility: honest severity, controlled disclosure and AI-drafted reports
1 min read
A vulnerability report works only if readers believe it. Severity is useful because it discriminates between findings.
An analyst who labels almost everything critical, including isolated hosts with no known exploit, removes that discrimination: owners start deferring everything equally, and the genuinely urgent finding no longer earns priority. Over-rating feels safe, but it spends the analyst's credibility, which is the mechanism that gets urgent work done.
Details of an unremediated flaw are exploitable information with contractual and legal consequences.
When an integration partner asks the analyst directly for full details before the organization has decided what to disclose, the request is legitimate but is routed through legal and the communications owner, and only what the approved process releases is shared. Ignoring the partner and sending raw scan output are both wrong.
Check yourself
1. For a year an analyst has labeled almost every finding 'critical — remediate immediately', including findings on isolated hosts with no known exploit. Owners now ignore the labels. What is the MOST accurate account of what this practice cost?
2. An integration partner emails the analyst directly asking for full details of an unremediated flaw in the shared interface, before the organization has agreed what to disclose. What should the analyst do?
Facts checked 2026-11-15 · Sources: CompTIA: CySA+ (CS0-004) certification and exam objectives, NIST SP 800-40 Rev. 4: Guide to Enterprise Patch Management Planning
CompTIA CySA+ cheat sheet: every key fact on one page →