Vulnerability Assessment Report Components
A large organization has recently performed a vulnerability assessment using Nessus Professional, and the security team is now preparing the final report. They have identified a high-risk vulnerability, named XYZ, which could potentially allow unauthorized access to the network. In preparing the report, which of the following elements would NOT be typically included in the detailed documentation for this specific vulnerability?
Community Votes
78% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The common trap is confusing the scope of a vulnerability assessment with that of a full penetration test or an executive summary; students often mistakenly believe PoC (Option A) belongs only in pentests.
This question tests the specific documentation requirements for a vulnerability assessment report versus a penetration test. The correct answer is B, as aggregate statistics are not part of the detailed documentation for a single specific vulnerability.
Many learners select A, arguing that Proof of Concept (PoC) is exclusive to penetration testing, but CEH guidelines explicitly include PoC in vulnerability reports if feasible.
Community Discussion (13 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Correct answer: B — The total number of high, medium, and low-risk vulnerabilities detected throughout the network is NOT typically included in the detailed documentation for a specific vulnerability like XYZ. While an executive summary might contain aggregate data, the detailed section for a single finding focuses on that specific issue's mechanics, impact, and remediation.Why the Other Options Are Wrong
Options A, C, and D are all standard components of a detailed vulnerability report. Option D (CVE ID) is essential for tracking and patching. Option C (affected systems) is critical for scoping the remediation effort. Option A (Proof of Concept) is often included in professional vulnerability reports (especially from tools like Nessus) to validate the finding and demonstrate impact, even though it is more aggressive in a pentest context.Community Comment Notes
Community consensus strongly supports B. As user athicalacker noted, the report must include "The vulnerability's name and its mapped CVE ID" and "Details regarding the affected systems." User insaniunt referenced CEH v12 page 576, confirming that PoC is listed as a potential inclusion. Some users incorrectly chose A, arguing that PoC is for pentesting, but this distinction is blurred in modern vulnerability reporting where validation is key.Exam Strategy
When reading questions about 'detailed documentation for a specific vulnerability,' look for options that describe global or aggregate data (like totals across the whole network). Those belong in summaries, not individual item details. Conversely, do not automatically exclude technical validation steps like PoC unless the question strictly distinguishes between passive scanning and active exploitation.
Frequently Asked Questions
Is Proof of Concept (PoC) included in vulnerability assessments?
Yes, if possible. CEH guidelines state that a vulnerability assessment report may include a PoC to demonstrate the impact of the vulnerability, distinguishing it from simple detection.
Why isn't the total number of vulnerabilities included?
That figure belongs in the Executive Summary or Overview sections. The 'detailed documentation' for a specific vulnerability (XYZ) focuses on that specific flaw's ID, scope, and proof, not the global tally.