Domain 1Recon & ReportingCORE

Report Structure and Components

Detailed breakdown of every component in a professional penetration test report, from cover page to appendices, with templates and guidelines for each section.

Domain: Domain 1: Reconnaissance & Reporting•Updated: 2026-09-01
#structure#components#template#organization#oscp-exam

OSCP Report Writing: Report Structure and Components

1. Standard Penetration Test Report Structure

A professional penetration test report follows a well-defined structure that ensures all necessary information is presented in a logical, accessible order. This structure is recognized across the industry and expected by clients, auditors, and certification bodies.

High-Level Structure

PENETRATION TEST REPORT
├── 1. Cover Page
├── 2. Table of Contents
├── 3. Document Control
├── 4. Disclaimer
├── 5. Executive Summary
├── 6. Engagement Overview
├── 7. Technical Overview
├── 8. Findings
│   ├── 8.1 VULN-001
│   ├── 8.2 VULN-002
│   └── 8.N VULN-00N
├── 9. Risk Summary
├── 10. Recommendations
├── 11. Conclusion
└── 12. Appendices
    ├── A: Tool Output
    ├── B: Network Diagrams
    ├── C: Glossary
    ├── D: References
    └── E: Additional Evidence

2. Detailed Component Breakdown

Component 1: Cover Page

Purpose: Identify the document, client, and classification level at a glance.

Required Elements:

  • Report title (e.g., “Penetration Test Report”)
  • Client name and logo
  • Report date
  • Author name and credentials
  • Classification marking (e.g., “CONFIDENTIAL”)
  • Report version number
  • Engagement reference number

Template:

┌─────────────────────────────────────────┐
│           PENETRATION TEST REPORT       │
│                                         │
│         Prepared for: [Client Name]     │
│                                         │
│         Prepared by: [Your Name]        │
│         [Your Credentials]              │
│                                         │
│         Date: [Report Date]             │
│         Version: 1.0                    │
│         Reference: [Engagement ID]      │
│                                         │
│         *** CONFIDENTIAL ***            │
└─────────────────────────────────────────┘

Component 2: Table of Contents

Purpose: Enable quick navigation through the document.

Requirements:

  • Auto-generated with page numbers
  • Include all sections and subsections
  • Include appendix entries
  • Update after final editing

Best Practices:

  • Use your word processor’s auto-TOC feature (never manual)
  • Include at least 3 levels of heading depth
  • Verify all page numbers are correct before submission

Component 3: Document Control

Purpose: Track document versions, changes, and approvals.

Template:

Version Date Author Reviewer Changes
0.1 2026-08-01 [Name] - Initial draft created
0.5 2026-08-15 [Name] - Added findings, internal review
0.8 2026-08-20 [Name] [Reviewer] Incorporated reviewer feedback
1.0 2026-08-25 [Name] [Reviewer] Final version, client approved

Why it matters:

  • Demonstrates professional document management
  • Provides audit trail for changes
  • Shows who approved the final version

Component 4: Disclaimer

Purpose: Define legal boundaries and scope limitations.

Required Elements:

  • Statement of authorized testing
  • Scope limitations
  • Limitation of liability
  • Confidentiality notice
  • Intended audience statement

Template:

DISCLAIMER

This report contains the results of an authorized security assessment 
conducted by [Tester/Company] for [Client Name] during the period of 
[Start Date] to [End Date]. The testing was performed within the 
agreed scope defined in the Rules of Engagement document.

This document is classified as CONFIDENTIAL and is intended solely for 
the use of [Client Name] and its authorized personnel. Distribution 
outside of [Client Name] requires written approval from [Authorizing Party].

The findings and recommendations in this report reflect the state of 
the tested systems at the time of assessment. Future changes to the 
systems, network, or threat landscape may affect the validity of these 
findings.

Component 5: Executive Summary

Purpose: High-level overview for management and leadership.

Length: 2-4 pages maximum.

Content:

  • Engagement overview and scope
  • Overall risk rating
  • Critical and high findings summary
  • Business impact assessment
  • Strategic recommendations
  • Remediation timeline

(See Chapter 2 for detailed executive summary guidance.)

Component 6: Engagement Overview

Purpose: Provide context about the testing engagement.

Required Elements:

  • Objectives: What was the goal of the engagement?
  • Scope: What systems, networks, and applications were in scope?
  • Out of Scope: What was explicitly excluded?
  • Timeline: When did the engagement occur?
  • Methodology: What testing approach was used?
  • Rules of Engagement: What constraints and guidelines applied?
  • Team: Who performed the testing?

Template:

ENGAGEMENT OVERVIEW

Objectives:
The objective of this penetration test was to assess the security 
posture of [Client Name]'s internal network infrastructure by 
attempting to exploit vulnerabilities and gain unauthorized access 
to critical systems.

Scope:
The following systems were included in the scope of testing:
- [System 1]: [IP Address] - [Description]
- [System 2]: [IP Address] - [Description]
- [System 3]: [IP Address] - [Description]

Out of Scope:
- Production database servers
- External-facing web applications
- Social engineering attacks

Timeline:
- Planning: [Date Range]
- Execution: [Date Range]
- Reporting: [Date Range]

Methodology:
The testing followed the PTES (Penetration Testing Execution Standard) 
methodology, consisting of the following phases:
1. Reconnaissance
2. Scanning and Enumeration
3. Vulnerability Analysis
4. Exploitation
5. Post-Exploitation
6. Reporting

Component 7: Technical Overview

Purpose: Provide technical context about the tested environment.

Required Elements:

  • Network Architecture: Diagram or description of the target network
  • Systems Tested: List of all systems with OS, roles, and configurations
  • Tools Used: List of tools and their versions
  • Testing Approach: Technical methodology details

Template:

TECHNICAL OVERVIEW

Network Architecture:
The target environment consists of [Number] systems across [Number] 
subnets. The network topology is described below:

[Include network diagram or description]

Systems Tested:
| Hostname | IP Address | Operating System | Role |
|---|---|---|---|
| webserver01 | 10.10.10.100 | Ubuntu 20.04 | Web Application Server |
| dc01 | 10.10.10.200 | Windows Server 2019 | Domain Controller |
| db01 | 10.10.10.150 | CentOS 8 | Database Server |

Tools Used:
| Tool | Version | Purpose |
|---|---|---|
| nmap | 7.94 | Port scanning and service enumeration |
| Metasploit Framework | 6.3 | Exploitation framework |
| Burp Suite | 2024.1 | Web application testing |
| John the Ripper | 1.9.0 | Password cracking |
| LinPEAS | 2024.06 | Linux privilege escalation enumeration |

Component 8: Findings

Purpose: Document each vulnerability discovered during the engagement.

Structure per Finding:

  • Finding ID and Title
  • Severity Rating and CVSS Score
  • Affected System and Component
  • Summary
  • Technical Details
  • Proof of Concept
  • Evidence (Screenshots)
  • Impact
  • Remediation
  • References

(See Chapter 5 for detailed findings documentation guidance.)

Component 9: Risk Summary

Purpose: Provide an aggregate view of all findings and their risk levels.

Required Elements:

  • Findings summary table
  • Risk matrix visualization
  • Risk distribution chart
  • Overall risk assessment

Template:

RISK SUMMARY

Findings Distribution:
| Severity | Count | Percentage |
|---|---|---|
| Critical | 2 | 15% |
| High | 4 | 30% |
| Medium | 5 | 35% |
| Low | 3 | 22% |
| Informational | 1 | 7% |
| Total | 15 | 100% |

Overall Risk Assessment:
Based on the findings identified during this engagement, the overall 
risk posture of the tested environment is assessed as HIGH. The presence 
of [Number] Critical and [Number] High severity vulnerabilities indicates 
significant security weaknesses that require immediate attention.

Component 10: Recommendations

Purpose: Provide prioritized remediation guidance.

Required Elements:

  • Prioritized remediation plan
  • Short-term, medium-term, and long-term actions
  • Resource requirements
  • Expected risk reduction

Template:

RECOMMENDATIONS

Immediate Actions (0-30 days):
1. Patch Critical vulnerabilities VULN-001 and VULN-002
2. Implement network segmentation for sensitive systems
3. Enable multi-factor authentication for administrative access

Short-term Actions (30-90 days):
1. Conduct organization-wide password policy review
2. Implement web application firewall for public-facing applications
3. Deploy vulnerability scanning solution for continuous monitoring

Long-term Actions (90+ days):
1. Establish regular penetration testing program
2. Implement security awareness training for all employees
3. Develop and maintain incident response plan

Component 11: Conclusion

Purpose: Provide final assessment and next steps.

Required Elements:

  • Summary of overall findings
  • Assessment of security posture
  • Recommendations for follow-up testing
  • Final remarks

Template:

CONCLUSION

This penetration test identified [Number] vulnerabilities across 
[Number] systems, including [Number] Critical and [Number] High 
severity findings. The most significant risks were [brief description].

The overall security posture of the tested environment is assessed 
as [High/Medium/Low] risk. Immediate attention should be given to 
the Critical and High severity findings to reduce the organization's 
attack surface.

A follow-up penetration test is recommended after remediation of 
the Critical and High severity findings to verify that the 
vulnerabilities have been effectively addressed.

Component 12: Appendices

Purpose: Provide supporting documentation and raw data.

Common Appendices:

  • Appendix A: Tool Output (raw scanner results, nmap output)
  • Appendix B: Network Diagrams (architecture diagrams)
  • Appendix C: Glossary (technical terms and definitions)
  • Appendix D: References (CVEs, advisories, documentation)
  • Appendix E: Additional Evidence (extra screenshots, captures)
  • Appendix F: Custom Scripts (exploitation scripts used)
  • Appendix G: Legal Documents (rules of engagement, authorization)

(See Chapter 17 for detailed appendices guidance.)

3. Page Estimates by Component

Component Estimated Pages Required for OSCP?
Cover Page 1 Yes
Table of Contents 1-2 Yes
Document Control 1 Yes
Disclaimer 1 Yes
Executive Summary 2-4 Yes
Engagement Overview 2-3 Yes
Technical Overview 2-3 Yes
Findings Varies (5-15 per finding) Yes
Risk Summary 1-2 Yes
Recommendations 2-3 Yes
Conclusion 1 Yes
Appendices Varies Partially

4. Key Concepts

Modular Design

Each finding should be self-contained and independently readable. A reader should be able to understand VULN-003 without reading VULN-001 or VULN-002.

Numbering Scheme

Use consistent, sequential IDs for all findings:

  • VULN-001, VULN-002, VULN-003 (recommended)
  • FINDING-001, FINDING-002 (alternative)
  • H-001, M-001, L-001 (by severity, less common)

Classification Marking

Clearly mark the sensitivity of the document:

  • CONFIDENTIAL (most common for pentest reports)
  • RESTRICTED (for highly sensitive engagements)
  • INTERNAL USE ONLY (for internal assessments)

Place classification on:

  • Cover page
  • Each page header/footer
  • Email transmissions
  • File names

5. Key Takeaways

  1. Follow a standard structure. Use the recognized report structure for professionalism and completeness.
  2. Every component serves a purpose. Don’t skip sections even if they seem optional.
  3. Modular findings. Each finding should be self-contained and independently readable.
  4. Consistent numbering. Use a clear, sequential numbering scheme for all findings.
  5. Classification matters. Mark the document sensitivity appropriately.
  6. Document control. Track versions, changes, and approvals professionally.

6. Further Reading

  • PTES Technical Report Template: https://www.pentest-standard.org/
  • NIST SP 800-115 Reporting Guidelines
  • OWASP Testing Guide Reporting Section
  • Offensive Security Report Template (provided with OSCP course)