312-50 ยท Vulnerability analysis
Reading and trusting a vulnerability report
Report structure, false positives and false negatives, risk ratings, remediation recommendations.
Key points
- A good report: executive summary, scope and method, findings with severity, evidence and affected assets, remediation by priority.
- False positive: reported flaw that does not exist.
- False negative: real flaw the scan missed; more dangerous, gives false assurance.
- Validate findings; credentialed scans reduce errors.
- Rate risk by severity, likelihood and asset impact.
Practice questions
What is a false positive in vulnerability scanning?
- A real flaw the scanner missed
- A reported flaw that does not exist
- A flaw that was patched
- A low severity finding
Show answer
Answer: B. A reported flaw that does not exist
A false positive is a finding reported although the flaw is not actually present. The reverse, a real flaw not reported, is a false negative.
Which items belong in a useful vulnerability report?
- Scope and methodology
- Findings with severity and evidence
- Employee salary data
- Prioritized remediation recommendations
- Full raw packet captures of all traffic
Show answer
Answer: A. Scope and methodology, B. Findings with severity and evidence, D. Prioritized remediation recommendations
Scope, severity-rated findings with evidence, and prioritized remediation make a report actionable. Employee salaries and raw packet dumps of all traffic are irrelevant.
A scan report with zero findings proves the system has no vulnerabilities.
Show answer
Answer: False
False. The scan may have false negatives: limited coverage, outdated checks, blocked probes or missing credentials.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
