A penetration test report has two audiences, and a good one serves both. The
executive summary is written for leadership: it describes what was tested, what was found, the
overall risk level, and what needs to change, without requiring technical background to understand.
The technical findings section is written for the security team and system administrators: it
documents each finding with a CVE reference where applicable, the exact evidence of exploitation
(screenshots, captured data, shell access confirmations), the attack chain that led to the finding,
and specific remediation steps with enough detail that an engineer can implement them without
further research. Reports that blur these two audiences, technical language in the executive
section, vague remediation guidance in the findings, are the most common quality problem in
commercial penetration testing.
CVSS (Common Vulnerability Scoring System) scores appear in most professional penetration
test reports, but they require context to be useful. A CVSS 9.8 (Critical) remote code
execution vulnerability on an internet facing server is a different emergency than the
same score on an isolated internal system with no network path to sensitive data. Risk
ratings in PwnInspect reports account for exploitability, business impact, and
compensating controls, so the remediation priority list reflects actual organizational
risk, not just the theoretical severity of each finding in isolation. The difference
matters when the IT team has three weeks to address findings before the assessment and
needs to allocate limited resources to the highest impact remediations first.
Remediation verification is the step that distinguishes a penetration test engagement from
a onetime scan. After the initial report is delivered and the organization implements
fixes, a verification retest confirms that each finding has been fully addressed and that
the remediation hasn't introduced new vulnerabilities. PwnInspect includes a retest as
part of every engagement because a fix that resolves the specific exploit technique but
leaves the underlying misconfiguration in place is not a complete remediation, and the
next auditor or attacker will find it the same way we did.