What a good penetration test report contains

The sections a useful report has, and what to check before you accept one.

A developer working through code on a laptop

The parts of a useful report

A report has two readers: the people who decide and the people who fix. A good one serves both.

  • Executive summary: overall risk and the few things that matter most, in plain language.
  • Scope and dates: exactly what was tested, when, and from where.
  • Method: the standards followed, such as OWASP or NIST SP 800-115.
  • Findings: each with severity, CVSS score, affected asset, evidence and steps to reproduce.
  • Fix guidance: what to change, specific to your stack.
  • Retest results: which findings were fixed and verified.

Warning signs

Scanner output pasted without validation, findings with no evidence, and no statement of scope are signs that little manual testing was done.

See an ESCOSS report

Ask for a sample report with your proposal request and we will send a redacted example by email.

Need this done?

Tell us what needs testing and when. We reply within 1 business day.

Request a sample report
Ready to test?

Tell us what needs testing and by when.

You receive a written proposal with scope, method, timeline and a fixed price. We reply within 1 business day.