External Penetration Test Report
Every engagement concludes with a formal report — written for engineers, summarised for the board, accepted by auditors.
Reflected XSS in /search via `q` parameter
Host: example.com
Report structure
Eight sections, built for both your security team and your auditors.
One page. Plain English. A non-technical decision-maker should be able to read this and understand what was tested, how bad it is, and what to do about it.
In-scope assets, out-of-scope exclusions, testing window, allowed techniques, and written authorisation record.
Six-phase engagement structure aligned with PTES and OWASP WSTG, including the CVSS v3.1 rating methodology used for every finding.
A table of every finding with ID, title, severity, CVSS score, and affected asset — at-a-glance prioritisation for your engineering team.
Per-finding: severity, CVSS vector, affected asset, description, business impact, reproduction steps, evidence, remediation, and references.
Prose walkthrough of the most interesting attack chain found — written so a non-technical reader can follow it.
Prioritised fix list with effort estimates and recommended timelines (immediate / 30 days / 90 days).
Tools used with versions, engagement timeline, evidence index, and a glossary of terms for non-technical readers.