Cybernion
← Insights

Security

What Is in a Penetration Test Report?

30 Aug 2026 · Updated 30 Aug 2026

A penetration test report has two parts: an executive summary for management focused on business impact, and a technical section for the people fixing the issues. It describes the scope and methodology, the findings with evidence, a severity rating for each (usually CVSS), and clear remediation guidance, plus retesting to verify fixes. A report only improves security if its findings are acted on.

The report is the deliverable an organisation actually pays for, and its quality varies enormously. Knowing what a good one contains is what makes it possible to judge whether a test was thorough and, more importantly, to act on it.

What is in a penetration test report?

A penetration test report is the record of what was tested, what was found, and what to do about it. Recognised methodologies converge on a two part structure: an executive summary written for management, and a technical report written for the people who will remediate the issues. This split matters, because the two audiences need different things from the same engagement.

Beyond that structure, NIST describes the core content simply: a report describes the vulnerabilities identified, presents a risk rating for each, and gives guidance on how to mitigate them. A good report adds an assessment of the overall security posture and a prioritised remediation plan, and it addresses retesting to confirm the fixes. The Penetration Testing Execution Standard sets out this structure in detail, and using it is a sign of a credible provider. The rest of this article walks through each part, so it is clear what to expect and what to insist on.

What is in the executive summary?

The executive summary is written for management and focuses on business impact rather than technical detail. Its job is to let a non technical decision maker understand, in a few pages, how exposed the organisation is and what needs to happen.

Following the PTES structure, a strong executive summary covers the background and scope of the engagement, the organisation’s overall security posture, an overall risk ranking or profile, a plain language summary of the general findings, a summary of the recommendations, and a strategic roadmap that prioritises the remediation. The value of this section is that it translates a technical exercise into business terms, risk, priorities and a plan, so that leadership can make informed decisions about resourcing the fixes. If a report’s executive summary is just a list of technical findings with no posture assessment or prioritised plan, it is not doing its job. This is the part to share with the board or leadership team.

How are penetration test findings rated?

Findings are rated by severity so they can be prioritised, because not every vulnerability deserves equal urgency. The standard method is the Common Vulnerability Scoring System, or CVSS, maintained by FIRST, which produces a numerical score that maps to a qualitative rating such as low, medium, high or critical. The current version is CVSS v4.0, released in 2023, though the earlier v3.1 is still widely used.

CVSS gives a consistent, defensible way to rank findings, but a good tester does not stop at the raw score. The severity of a vulnerability in isolation is not always its real risk to the organisation, and a critical rated flaw on a system with no sensitive data and no external exposure may matter less than a medium rated flaw on the most important system. NIST makes this point directly: assessors should determine the appropriate risk level for each vulnerability rather than simply accepting the score a tool assigns. So the best reports pair a standard CVSS score with a risk rating adjusted to the actual environment, which is far more useful for deciding what to fix first.

What is in the technical section, and what should we do with the report?

The technical section documents the engagement in detail for the people who will fix the issues. Following PTES, it covers the introduction, scope, objectives and approach, the information gathering, the vulnerabilities identified, the exploitation and confirmation of those vulnerabilities, any post exploitation that demonstrates the real business impact of a successful attack, and the risk and exposure. Each finding should include enough evidence and reproduction detail for the remediation team to understand and fix it, and this is where a thorough report proves its worth.

What happens with the report matters more than the report itself. Use it to drive remediation: prioritise the findings by risk, assign and track the fixes, and then retest to verify the corrections actually worked. Good engagements include a retest, and frameworks like PCI DSS require that exploitable findings are corrected and re-tested. Share the executive summary with leadership so the risk is understood and the remediation is resourced. A penetration test only improves security if its findings are acted on and the fixes are verified, and a report that is filed and forgotten has bought nothing but a false sense of assurance. For an organisation that wants a penetration test with a clear, actionable report and a retest of the fixes, Cybernion offers penetration testing.

Frequently asked questions

What is in a penetration test report?

A penetration test report typically has two parts, an executive summary for management and a technical report for the people fixing the issues. It describes the scope and methodology, the vulnerabilities found with evidence, a risk rating for each, and clear remediation guidance. Good reports also include an overall assessment of the organisation’s security posture and a prioritised plan for fixing the issues, and cover retesting to verify the fixes.

What is in the executive summary of a penetration test report?

The executive summary is written for management and focuses on business impact rather than technical detail. It typically covers the background and scope, the overall security posture, an overall risk ranking, a plain summary of the general findings, a summary of recommendations, and a prioritised roadmap for remediation. Its job is to let a non-technical decision maker understand how exposed the organisation is and what to do about it.

How are penetration test findings rated?

Findings are rated by severity so they can be prioritised. Most reports use the Common Vulnerability Scoring System (CVSS), which produces a numerical score that maps to a qualitative rating such as low, medium, high or critical. The current version is CVSS v4.0. A good tester also adjusts the rating to the real risk in the environment, because a vulnerability’s severity in isolation is not always its actual risk to the organisation.

What is in the technical section of a penetration test report?

The technical section documents the engagement in detail for the people who will fix the issues. It covers the scope, objectives and approach, the information gathering, the vulnerabilities identified, the exploitation and confirmation of those vulnerabilities, any post exploitation showing business impact, and the risk and exposure. Each finding should include enough evidence and detail to reproduce and remediate it.

What should we do with a penetration test report?

Use it to drive remediation, not just to file it. Prioritise the findings by risk, assign and track the fixes, and then retest to verify the corrections actually worked, which good engagements include. Share the executive summary with leadership so the risk is understood and resourced. A penetration test report only improves security if its findings are acted on and the fixes are verified, otherwise it is just a document.


Written by Gaurav Vikash, an ASD endorsed IRAP assessor and senior cyber security leader with 18 years of experience across Australia, the UK and Asia, including CISO and senior security leadership roles. He holds CISSP, CISA, CISM and CRISC and is an ISO 27001 Lead Auditor and ISO 42001 Lead Implementer, and speaks regularly at industry conferences.

Talk to us.

Sources:

  1. NIST SP 800-115, Technical Guide to Information Security Testing and Assessment, National Institute of Standards and Technology, September 2008
  2. The Penetration Testing Execution Standard — Reporting, PTES, 2026
  3. Common Vulnerability Scoring System, FIRST, 2026
  4. PCI DSS, PCI Security Standards Council, 2026

Last updated: 30 August, 2026

Talk to us about your engagement

A scoped proposal within one business day.