Reporting for Penetration Testers
Reporting turns technical findings into a document that the client can act on. A good report has an executive summary, a scope and method section, and findings with severity ratings, evidence, reproduction steps and fixes. Ratings often use CVSS, and a retest confirms that remediated issues are actually closed.
Stage: Post-exploitation and Reporting · Part of the Penetration Tester roadmap · Last reviewed 19 November 2026
What to learn in Reporting
- Write an executive summary that a non-technical manager can follow
- Rate a finding using CVSS and explain the score
- Document reproduction steps so a developer can repeat the issue
- Write a specific remediation instead of a vague recommendation
- Plan a retest and update finding status as fixed or open
Reporting interview questions
What should every finding in a pentest report contain?
A clear title, affected asset, severity with its reasoning, a description of the risk, evidence such as screenshots or requests, steps to reproduce, and a concrete fix. This lets developers verify and repair the issue without further contact.
Why does a pentest engagement often include a retest?
Fixes can be incomplete or introduce new problems. A retest checks each reported issue again and records it as resolved, partly resolved or still open, giving the client evidence for managers and auditors that the risk has been reduced.
Where Reporting fits in the Penetration Tester roadmap
Reporting belongs to the Post-exploitation and Reporting stage (advanced level). Finish well.
Other units in this stage
Back to the full Penetration Tester roadmap