What a Penetration Test Report Should Include (With a Sample)
Harsh
Cybersecurity Experts
Table of Contents
- 01Why the penetration test report matters more than the test
- 02The sections every report needs
- 03The executive summary
- 04Scope and methodology
- 05The CVSS findings report
- 06Pen test report example: one finding written properly
- 07What separates a useful report from scanner output
- 08Using a penetration testing report template
- 09Checklist before you accept a report
- 10What Digisecuritas delivers
- 11Read a full sample before you choose a vendor
- 12Frequently Asked Questions
Why the penetration test report matters more than the test
The penetration test report is the only part of the engagement your company keeps. The testing takes a week or two. The report is what your developers work from for months, what your auditor files as evidence and what your customers ask to see.
A weak report wastes a good test. If findings cannot be reproduced, they do not get fixed. If severity is unexplained, everything looks urgent or nothing does. This guide lists what a report should contain, shows a sample finding and gives a checklist for judging one before you accept it.
The sections every report needs
Section | Who reads it | What it should contain
|
|---|---|---|
Executive summary | Leadership, customers, auditors | Overall risk in plain language, the most serious findings, what to do first |
Scope and rules of engagement | Auditors, security team | Exact targets, dates, test type, accounts used, exclusions |
Methodology | Auditors, security team | Standards followed and the phases of work |
Findings summary | Engineering managers | A table of every finding with severity and status |
Detailed findings | Developers | Description, affected asset, steps to reproduce, proof, impact, fix |
Compliance mapping | Compliance team | Findings mapped to SOC 2, PCI DSS, ISO 27001 or HIPAA as needed |
Re-test results | Everyone | Which findings were verified as fixed, and when |
Appendices | Security team | Tools used, raw evidence, tester credentials |
The executive summary
A good executive summary fits on one or two pages and can be read by someone with no security background. It states what was tested and when, gives an overall risk rating with the reason for it, and names the handful of findings that matter most with their business impact.
"We found 14 vulnerabilities" tells a reader nothing. "An authenticated customer could view invoices belonging to any other customer" tells them what is at stake.
Scope and methodology
The scope section should be precise enough that an auditor can match it to your system description: URLs, IP ranges, application versions, API collections, user roles tested and the testing window. It should also state what was excluded and why.
The methodology section names the standards the tester followed, such as the OWASP Top 10 for web applications, the OWASP API Security Top 10 or the OWASP Mobile Top 10, and describes the phases from discovery through re-testing. It should say how much of the work was manual.
The CVSS findings report
Most reports include a findings table scored with the Common Vulnerability Scoring System. A CVSS findings report gives each issue a base score from 0.0 to 10.0 and a severity band.
CVSS base score | Severity
|
|---|---|
9.0 to 10.0 | Critical |
7.0 to 8.9 | High |
4.0 to 6.9 | Medium |
0.1 to 3.9 | Low |
0.0 | Informational |
The score measures technical severity. It does not know your business. A medium-scored flaw on the system that holds payment data can deserve attention before a high-scored flaw on a test server. Good reports give the CVSS vector for each finding and add a short note on business context where the two differ.
Pen test report example: one finding written properly
The pen test report example below shows the level of detail a single finding should carry. The application and data are illustrative.
Finding 3: Customers can read other customers' invoices
Severity: High (CVSS 3.1 base score 7.7, vector AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N)
Category: Broken access control (OWASP A01)
Affected asset: GET /api/v2/invoices/{invoiceId} on app.example.com
Description. The invoice endpoint returns an invoice to any logged-in user who supplies a valid invoice ID. The server checks that the session is valid. It does not check that the invoice belongs to the account making the request.
Steps to reproduce.
Log in as test user A and open any invoice. Note the request to /api/v2/invoices/48213.
Log in as test user B in a separate browser session.
As user B, send the same request with user B's session token.
The server returns user A's invoice, including name, billing address and line items.
Proof. Request and response pair captured on the test date, included as Figure 7.
Impact. Invoice IDs are sequential. Any customer could retrieve the billing records of every other customer by counting through IDs.
Remediation. Enforce an ownership check on the server for every invoice request. Apply the same check to the export and PDF endpoints, which use the same lookup. Consider non-sequential identifiers as an additional measure.
Status. Open at report date. Verified fixed at re-test.
Everything a developer needs is there: where the flaw is, how to trigger it, what it exposes and how to close it.
What separates a useful report from scanner output
Findings are verified by exploitation, with evidence, and false positives are removed
Steps to reproduce work when a developer follows them
Fix guidance is specific to your stack
Related findings are grouped by root cause, so one fix closes several issues
Severity is explained
Positive observations are noted, so you know which controls held up
A report that lists hundreds of items with generic descriptions and links to public advisories is a scan export.
Using a penetration testing report template
A penetration testing report template is useful as a structure. It fixes the order of sections and makes sure nothing is left out. If you run internal tests, a template keeps reports consistent from one quarter to the next.
The template is the easy part. The value sits in the findings, and those depend on the tester. When you compare vendors, read a completed sample, since a blank template shows you headings and nothing about the quality of work.
Checklist before you accept a report
Does the scope match what you contracted?
Can a developer reproduce each finding from the steps given?
Does every finding have a CVSS score and vector?
Is there proof for each exploited issue?
Is remediation advice specific enough to act on?
Are findings mapped to the frameworks you report against?
Is there a summary you can share with customers without exposing detail?
Are re-test terms and dates stated?
What Digisecuritas delivers
Each engagement produces an executive summary report, a technical findings report, a CVSS risk matrix, proof of exploitation, remediation guidance, compliance mapping and a re-test report. Average delivery is within 72 hours of testing completion. More detail is on the VAPT services page.
Read a full sample before you choose a vendor
Our sample report shows every section described above, with redacted findings from web, API and network testing.
