04 · What you receiveWhat's actually in the report.
Six artifacts. Each one written to be the answer to a specific auditor question — so when control evidence is requested, you forward a section, not a 100-page PDF.
Part 01pp. 1 — 6
Executive summary & risk posture
One-page board view: severity distribution, attestation, posture trend versus last engagement, and the three remediations that close the biggest exposure.
Audit answer →"What is the current risk position?"
Part 02pp. 7 — 12
Methodology & scope statement
Frameworks followed (PTES, OWASP, NIST SP 800-115), targets in/out of scope, dates, tooling, and rules of engagement — signed and dated.
Audit answer →"Was the test conducted to a recognised standard?"
Part 03pp. 13 — 58
Findings with CVSS, CWE & OWASP
Every finding carries CVSS 3.1, CWE class, OWASP category, framework cross-references (ISO A.8.29, SOC 2 CC7.1, PCI 11.3), and machine-readable JSON for ingestion into GRC tools.
Audit answer →"Show me the issues, classified."
Part 04pp. 59 — 74
Evidence & chain-of-custody
Timestamped logs, screenshots, request/response captures, and the hash trail proving the test happened, when, and by whom. The bit auditors keep asking for.
Audit answer →"How do I know the test was actually performed?"
Part 05pp. 75 — 88
Remediation guidance
Per-finding fix steps, owner role suggested, effort estimate, and detection rules so blue-team can verify when the fix lands.
Audit answer →"What is the remediation plan?"
Part 06pp. 89 — 92
Tester attestation & sign-off
Reviewed and signed by a certified security professional. Re-test addendum issued within 30 days of remediation and bundled with the original engagement, no second SOW.
Audit answer →"Who signed this off, and against what?"