How to Write a Professional Penetration Testing Report

A penetration testing report is the primary deliverable of any engagement — it communicates findings to both technical staff and executive leadership, drives remediation, and justifies the value of the security investment. Many technically skilled penetration testers underestimate report quality. A poorly written report with critical findings may be ignored, while a clear, well-structured report with medium findings drives immediate action. This guide covers professional report writing for penetration tests.

Report Structure

A professional penetration testing report contains two main sections: an Executive Summary for non-technical stakeholders and a Technical Report for the security and IT teams.

1. Cover Page
   - Engagement title and date
   - Client organization name
   - Prepared by (company and lead tester)
   - Classification (Confidential)
   - Report version and status

2. Table of Contents

3. Executive Summary (1-2 pages)
   - Engagement overview
   - Overall risk rating
   - Key findings summary (non-technical)
   - Critical recommendations

4. Methodology
   - Scope and rules of engagement
   - Testing approach (black/gray/white box)
   - Tools and frameworks used
   - Testing timeline

5. Findings Summary Table
   - ID, Title, Severity, CVSS Score, Status

6. Detailed Findings (one section per finding)

7. Appendices
   - Tools used
   - Additional evidence
   - Methodology notes

Executive Summary

The executive summary is read by CISOs, CTOs, and board members who may not understand technical details. Write it last, in plain language:

Key elements:
- Overall security posture (Critical/High/Medium/Low risk)
- Number of findings by severity
- Most impactful finding in business terms
- What an attacker could have done with the access gained
- Top 3-5 strategic recommendations

Example opening paragraph:
"During the external network penetration test conducted November 1-5, 2024, 
[Company] identified 12 security vulnerabilities across the assessed scope. 
Three findings were rated Critical severity, including an SQL injection 
vulnerability that allowed complete database access, exposing customer 
payment data for approximately 50,000 users. Immediate remediation of 
the Critical and High findings is recommended."

DO: Use business impact language ('exposed 50,000 customer records')
DO NOT: Use technical jargon ('CVE-2024-XXXX exploited via SQLi')

Writing Individual Findings

Each finding should follow a consistent structure:

Finding: SQL Injection in Login Form
Severity: Critical
CVSS 3.1 Score: 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)
Affected Asset: https://target.com/login
CWE: CWE-89 (Improper Neutralization of Special Elements in SQL Command)
CVE: N/A (not a known CVE, custom vulnerability)

Description:
The login endpoint at /login does not properly sanitize user-supplied 
input before incorporating it into SQL queries. An unauthenticated 
attacker can inject SQL code via the 'username' parameter.

Impact:
Successful exploitation allows an attacker to:
- Bypass authentication and log in as any user including administrators
- Extract the entire user database including password hashes
- Potentially execute OS commands if xp_cmdshell is enabled

Steps to Reproduce:
1. Navigate to https://target.com/login
2. Enter the following in the username field: admin'--
3. Enter any value in the password field
4. Click Login
5. Observe successful authentication as the admin user

Proof of Concept:
[Screenshot of successful admin login]
[Screenshot of database dump]

Remediation:
Use parameterized queries (prepared statements) for all database interactions.
Example fix in PHP:
$stmt = $pdo->prepare('SELECT * FROM users WHERE username = ? AND password = ?');
$stmt->execute([$username, $password]);

References:
- OWASP SQL Injection Prevention Cheat Sheet
- CWE-89
- OWASP Testing Guide v4.2, section 4.7.5

CVSS Scoring

CVSS 3.1 Base Score Metrics:
Attack Vector (AV): Network(N) | Adjacent(A) | Local(L) | Physical(P)
Attack Complexity (AC): Low(L) | High(H)
Privileges Required (PR): None(N) | Low(L) | High(H)
User Interaction (UI): None(N) | Required(R)
Scope (S): Unchanged(U) | Changed(C)
Confidentiality (C): None(N) | Low(L) | High(H)
Integrity (I): None(N) | Low(L) | High(H)
Availability (A): None(N) | Low(L) | High(H)

Score ranges:
9.0-10.0: Critical
7.0-8.9:  High
4.0-6.9:  Medium
0.1-3.9:  Low
0.0:      Informational

# Calculate at: https://www.first.org/cvss/calculator/3.1

Writing the Remediation Section

Remediation guidance should be specific, actionable, and prioritized. Avoid vague recommendations like ‘improve input validation.’ Good remediation:

BAD: 'Implement proper input validation'
GOOD: 'Replace the string concatenation in login.php line 47 with 
parameterized queries. See attached code diff for the exact change.'

BAD: 'Update the application'
GOOD: 'Upgrade Apache from 2.4.49 to 2.4.51 or later to patch CVE-2021-41773 
(CVSS 9.8). Apply the patch within 48 hours given active exploitation in the wild.'

Include:
- Specific files, functions, or configurations to change
- Code examples where applicable
- Reference to vendor patch or CVE advisory
- Suggested timeline based on severity

Report Quality Checklist

Before delivery:
[ ] All screenshots are clear and annotated with arrows/highlights
[ ] Proof-of-concept steps are reproducible by another tester
[ ] No copy-paste errors from previous reports
[ ] Client name spelled consistently throughout
[ ] All finding severities match CVSS scores
[ ] Remediation is specific, not generic
[ ] Executive summary matches technical findings
[ ] No internal/personal notes accidentally included
[ ] Report is spell-checked and grammar-checked
[ ] Classification/handling markings on every page
[ ] Report delivered via encrypted channel (PGP, secure portal)

Tools for Report Writing

Several tools streamline the reporting process for penetration testers:

Pwndoc    - Self-hosted collaborative report generator (open source)
SysReptor - Modern self-hosted pentest reporting platform
Dradis    - Collaboration and reporting platform
CherryTree- Note-taking during engagements (organize findings as you go)
Faraday   - Vulnerability management and report generation
Plextrac  - Commercial pentest reporting platform

Conclusion

A professional penetration testing report separates average testers from sought-after professionals. Focus on business impact in the executive summary, provide reproducible proof-of-concept steps in findings, and give specific actionable remediation guidance — not generic advice. Use CVSS 3.1 for objective severity scoring, follow a consistent finding structure, and use tools like Pwndoc or SysReptor to streamline report generation. The report is what clients pay for — the technical work is worthless without clear communication of the findings.

Related Articles

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top