What should a penetration test report include?

A useful penetration test report includes an executive summary, the assessed scope and limitations, and a prioritized list of findings supported by evidence. It gives leadership enough context to make a risk decision and engineering enough detail to assign, fix, and verify each issue.

An open ivory report with an amber tab and three embossed sections.

What should leadership see first?

The executive summary should identify which product and business workflows were assessed, which risks need attention first, and what coverage was excluded or constrained. It should name the decisions the organization needs to make, such as whether to limit a rollout, fund a fix, or accept residual risk for a defined period.

For a release decision, ask for the highest-priority findings and the business consequences in plain language. If evidence comes from a staging environment, record any known differences from production that affect the decision.

What does an engineering-ready finding contain?

  1. Stable identifier and affected scope. Record the finding ID, component, environment, affected roles, and relevant version so the same issue can be tracked through a fix and retest.
  2. Evidence and impact. Record what the assessor observed, what access or data was affected, and which parts of the impact are still uncertain. Store sensitive evidence with restricted access.
  3. Severity and priority. Explain the technical severity and the organization’s remediation priority. For example, a finding in an active billing workflow may take precedence over a technically similar issue in a disabled feature.
  4. Remediation and acceptance criteria. Describe the expected behavior after the fix so engineering can write a clear work item and agree on how to close it.
  5. Verification status. Track the difference between an implemented fix, a scheduled retest, and a fix independently verified against the agreed criteria.

If a report uses the Common Vulnerability Scoring System (CVSS), ask for the score, vector, and version. Use the score as one input alongside affected assets, exposure, and the potential business impact. FIRST’s CVSS v4.0 User Guide.

How should the report reach the team?

Agree on who receives the full report, who gets a summary, and who can access attachments. Redact secrets and identifiable data before transferring findings into a shared issue tracker. Link each engineering ticket back to the stable finding ID and assign an owner before the readout ends.

Use NIST SP 800-115 for context on analyzing findings and developing mitigation strategies. For the handoff after a fix is deployed, see the pentest retest guide.

All articles