Know a company with years of records? Refer it and earn up to $100K
Security testing reference

Penetration Test Report: Example, Template and Sections

A penetration test report example with a template: executive summary, scope, findings, severity ratings and remediation, plus who owns the report.

Critical
9.0 to 10.0CVSS v3.1 base score
High
7.0 to 8.9CVSS v3.1 base score
Medium
4.0 to 6.9CVSS v3.1 base score
Low
0.1 to 3.9CVSS v3.1 base score
A server rack with blue patch cables and a laptop showing a ticket queue
Short answer

A penetration test report records what was tested, how, what was found and how to fix it. The standard sections are version control and scope, an executive summary for managers, a findings summary with severity ratings, a detailed write-up of each finding with evidence and remediation, and appendices. A good report lets an engineer reproduce each finding and lets an executive see the business risk in one page.

  • Write for two readers: executives read the summary, engineers read the findings.
  • Each finding needs an ID, a severity, evidence, impact and a specific fix.
  • CVSS v3.1 maps a 0 to 10 base score to None, Low, Medium, High or Critical.
  • A retest report updates the status of each finding. It does not replace the original.

What is a penetration test report for?

NIST defines penetration testing as "security testing in which assessors mimic real-world attacks to identify methods for circumventing the security features of an application, system, or network" (NIST SP 800-115). The report is the only lasting product of that work. NIST's guidance is that "a report should be generated that identifies system, network, and organizational vulnerabilities and their recommended mitigation actions".

The same guide lists what the results are used for: as a reference point for corrective action, to define mitigation activities, and as a benchmark for tracking progress against security requirements. It also warns that one document rarely fits everyone: "Because a report may have multiple audiences, multiple report formats may be required to ensure that all are appropriately addressed."

Penetration test report template: the sections in order

The outline below follows the reporting chapter of the OWASP Web Security Testing Guide and the Penetration Testing Execution Standard, which describes itself as "the base criteria for penetration testing reporting". Both split the report into a summary for decision makers and a technical body.

SectionWhat goes in itReader
1.1 Version controlReport version, date, author and what changedEveryone
1.2 Table of contentsSections and appendicesEveryone
1.3 The teamTesters, with expertise and qualificationsClient security lead
1.4 ScopeTargets, test type, dates, what was agreed to be in and outClient security lead, auditors
1.5 LimitationsOut-of-bounds areas, broken functionality, lack of time, access or credentialsAnyone relying on the result
1.6 TimelineWhen testing ranOperations
1.7 DisclaimerA test is a point-in-time sample, not proof that no other flaws existLegal, management
2. Executive summaryObjective, key findings in business terms, strategic recommendationsExecutives
3.1 Findings summaryA table of findings with ID, title and risk levelBoth teams
3.2 Findings detailsOne write-up per finding: description, evidence, impact, remediation, referencesEngineers
AppendicesMethodology, tools, test accounts and source addresses, raw output, severity scaleEngineers, auditors

NIST SP 800-115 adds a planning document that belongs with the report: the rules of engagement, for which its Appendix B provides a template.

Penetration test report example: one finding, written up

OWASP says the findings section "is aimed at the technical team. It should include all the necessary information to understand the vulnerability, replicate it, and resolve it." The example below is a fictional SQL injection finding (CWE-89) written to that standard, followed by the findings summary table it would sit in.

IDTitleCVSS v3.1 baseSeverityStatus
F-01SQL injection in order search9.8CriticalOpen
F-02Order details readable by any logged-in user (missing object-level check)6.5MediumOpen
F-03Reflected cross-site scripting in the returns form6.1MediumFixed, confirmed at retest
F-04Weak TLS cipher suites accepted on the legacy endpoint3.7LowRisk accepted by client
Finding F-01: example write-up
Finding F-01: SQL injection in order search
Severity:      Critical
CVSS v3.1:     9.8  (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)
Weakness:      CWE-89
Asset:         https://shop.example.com/api/orders/search  (parameter: q)
Status:        Open (first reported in this test)

Description
The q parameter is placed into a database query without parameterization.
An unauthenticated request can change the query and read any table the
application account can reach.

Evidence
1. Request sent on 14 May, 10:42 UTC, from the test address listed in
   Appendix B. A single quote in q returned a database syntax error.
2. A boolean test (q=a' AND '1'='1 and q=a' AND '1'='2) returned different
   result counts, confirming injection.
3. The tester listed table names and read 5 rows of the customers table to
   prove impact. No data was changed. Screenshots: Appendix C, C-01 to C-04.

Impact
Read access to all customer and order records. Write access was not tested.
The database account also owns the admin_users table.

Remediation
1. Use parameterized queries for every statement in OrderSearchRepository.
2. Give the application account read access only to the tables it needs.
3. Add a test that sends quote characters to each search endpoint.

Retest
Not yet retested. Target fix date agreed with the client: 28 May.

Illustrative example written for this page. The domain, dates and class names are fictional.

How are pentest findings rated?

Most reports use the Common Vulnerability Scoring System. Its specification gives a qualitative scale for the 0 to 10 score: None is 0.0, Low is 0.1 to 3.9, Medium is 4.0 to 6.9, High is 7.0 to 8.9 and Critical is 9.0 to 10.0 (FIRST CVSS v3.1).

Be clear about what that number means. The specification says "the Base Score reflects the severity of a vulnerability according to its intrinsic characteristics which are constant over time and assumes the reasonable worst case impact across different deployed environments". It does not know that the affected server holds payment data or sits behind a VPN. Good reports give the CVSS base score and then a separate risk rating for this client, with one sentence explaining any difference.

  • Print the full vector string, not only the score, so the client can check it.
  • State the scoring version (v3.1 or v4.0) once, in the appendix.
  • Rate chained findings as a chain: two Mediums that together give account takeover are not a Medium.

Executive summary vs technical detail: who reads what?

OWASP calls the executive summary "the elevator pitch of the report" and tells authors to "focus on the business impact and leave out technical details for now". The Penetration Testing Execution Standard names its audience: "those who are in charge of the oversight and strategic vision of the security program".

A workable rule: the executive summary fits on one or two pages, uses no tool names and no payloads, and answers three questions. What did we test and why? What could an attacker do today? What needs to happen, in what order? Everything an engineer needs to reproduce and fix a finding belongs in the technical section.

Retests and how reports change over time

A report is not finished when it is delivered. PCI guidance describes the next step: "When the organization has completed these steps, the tester should perform a retest to validate the newly implemented controls mitigate the original risk" (PCI SSC Penetration Testing Guidance). It also warns that "remediation efforts extending for a long period after the initial test may require a new testing engagement".

Handle the retest as a new version of the same report. Keep every finding ID, change the status (open, fixed, partly fixed, risk accepted), add the retest date and evidence, and record the change in version control. OWASP suggests that a retest report include a subsection summarizing the previous findings and their updated status. Reports for the same system over several years, with stable IDs, show whether the same classes of flaw keep coming back.

Who owns a pentest report: the tester or the client?

The contract decides. Read the statement of work for three things: who owns the deliverable, who may see it, and what the testing firm may keep. Where the contract is silent, copyright law gives a default. Copyright "vests initially in the author or authors of the work" (17 U.S.C. 201), which is the testing firm for a report its employees wrote. Most contracts change that default by assigning the report to the client or granting the client a broad license.

Ownership of the document is not the whole answer. The report describes the client's systems and weaknesses, which is the client's confidential information under almost any services agreement, whoever holds the copyright. The methodology, templates and tooling normally stay with the tester. A client that wants to show the report to customers or auditors should check the sharing terms, and many testing firms issue a short attestation letter for that purpose.

Common mistakes in penetration test reports

Reports fail their readers in predictable ways.

  • Scanner output pasted in as findings, with no proof that anything is exploitable.
  • Findings without steps to reproduce, so the engineer cannot confirm the fix.
  • Severity given as a word with no vector or reasoning behind it.
  • An executive summary that lists vulnerability names instead of business impact.
  • Scope and limitations left out, so the reader assumes everything was tested.
  • Live passwords, tokens or customer records shown in screenshots.
  • A retest issued as a new report with new finding IDs, which breaks the history.

Are pentest reports and security case records also a data asset?

They can be, with the right permissions. Listings read on 15 November 2026 name penetration-testing firms, managed security providers and companies with an in-house security operations team. They ask for "alert-to-resolution records the company owns, or private security software", and they list penetration test reports and "repositories already scrubbed of secrets" among the things that add value. Logs without case context are named as not a fit.

The same listings set the condition: "the right to license them; customer data only with customer agreement". For a testing firm that means the client contract governs, as described above. For a company holding reports on its own systems, the question is whether it wants the weaknesses described at all, even when fixed.

For scale, one buyer's public listings, read 15 November 2026, put what a company earns for security case records at $20,000 to $750,000. Read that as a published ceiling, not a typical outcome: most archives qualify for less, and some do not qualify at all.

  • Client identifiers: names, domains, IP ranges, hostnames, employee names and email addresses in every finding and screenshot.
  • Secrets: credentials, tokens, keys and session cookies captured as evidence. See the agent trace redaction checklist for a method that also fits security records.
  • Sampled data: customer rows or files retrieved to prove impact.
  • Open findings: anything not yet fixed stays out.
  • Context to keep: finding IDs, severity, vectors, remediation and retest status, which is what makes a report set useful.

See licensing security incident data, SOC case data and audit log examples.

Origin Data Partners is an independent data partner. Your company decides what is shared and signs any license itself, and a buyer may pay Origin when a deal closes.

Does your company hold records like these? See what your data is worth.

Common questions

What should a penetration test report include?

A penetration test report should include version control, scope and limitations, an executive summary, a findings summary with severity ratings, a detailed write-up of each finding with evidence, impact and remediation, and appendices covering methodology and tools.

How long is a typical pentest report?

Length follows the scope and the number of findings, so there is no standard page count. The executive summary should stay at one or two pages. Each finding usually takes one to three pages with evidence.

Who owns a pentest report?

The contract between the tester and the client decides. Many contracts assign the report to the client. Whoever owns the document, the information about the client's systems is confidential to the client, and the tester keeps its methods and tools.

How are penetration test findings rated?

Most reports rate findings with CVSS. In version 3.1 a base score of 0.1 to 3.9 is Low, 4.0 to 6.9 is Medium, 7.0 to 8.9 is High and 9.0 to 10.0 is Critical. Good reports add a client-specific risk rating.

What is the difference between a pentest report and a vulnerability scan report?

A scan report lists possible weaknesses found by a tool. A pentest report shows what a tester actually exploited, with evidence, impact and reproduction steps, and it reflects human judgement about chained attacks and business risk.

Can a testing firm license anonymized pentest reports?

Only if its client contracts allow it or the clients agree. The report describes a client's systems, which is the client's confidential information. Removing names does not replace that agreement.

Sources and further reading

What is your company’s data worth?

AI companies pay $20K to $5M for company records. Six questions, no files.