Domain 1Recon & ReportingCORE

Report Types

Comprehensive guide to the different types of penetration test reports, including executive summaries, technical reports, and full reports, with detailed guidance on when and how to use each type.

Domain: Domain 1: Reconnaissance & Reporting•Updated: 2026-09-01
#report-types#executive-summary#technical-report#audience#oscp-exam

OSCP Report Writing: Report Types

1. Overview of Report Types

Penetration test engagements produce different types of reports tailored to different audiences and purposes. Understanding these report types is essential for delivering value to all stakeholders.

Report Type Comparison

Report Type Audience Length Detail Level Purpose OSCP Relevance
Executive Summary C-Suite, Management 2-4 pages High-level Decision making, budget approval Required section in OSCP report
Technical Report Engineers, Admins, Devs 15-50+ pages Detailed Remediation implementation Required section in OSCP report
Full Report All stakeholders Combined Both Complete engagement record The OSCP report IS a full report
Briefing Slides Management, Board 10-20 slides Visual Presentation and discussion Not required for OSCP
Raw Data Package Auditors, Security Team Unbounded Raw Verification and deep analysis Appendix material in OSCP

2. Executive Summary

Purpose

The executive summary enables leadership to understand the security risk without needing technical expertise. It is the most read section of the report and often the only section that C-level executives will read.

Key Characteristics

  • Length: 2-4 pages maximum. Never exceed this limit.
  • Tone: Professional, business-focused, concise. No technical jargon without explanation.
  • Reading time: Should be consumable in 5-10 minutes.
  • Primary goal: Enable informed decision-making about risk and resource allocation.

Required Elements

  1. Engagement Overview

    • What was tested and why
    • When the engagement occurred
    • Scope and objectives
    • Methodology used (high-level)
  2. Overall Risk Rating

    • Overall risk rating (Critical / High / Medium / Low)
    • Number of findings by severity (use a table or chart)
    • Key risk areas identified
  3. Critical and High Findings Summary

    • Limit to Critical and High findings only
    • Describe each in business terms (not technical terms)
    • Include business impact for each
  4. Business Impact Assessment

    • Potential financial impact
    • Regulatory compliance implications
    • Reputational risk
    • Operational disruption potential
  5. Strategic Recommendations

    • Immediate actions (0-30 days)
    • Short-term actions (30-90 days)
    • Long-term improvements (90+ days)
  6. Remediation Timeline

    • Prioritized remediation schedule
    • Resource requirements
    • Expected risk reduction

Executive Summary Template

EXECUTIVE SUMMARY

1. ENGAGEMENT OVERVIEW
   Offensive Security conducted a penetration test of [Client Name]'s 
   internal network infrastructure from [Start Date] to [End Date]. 
   The engagement targeted [Number] systems within the scope of 
   [Scope Description].

2. OVERALL ASSESSMENT
   The penetration test identified [Number] vulnerabilities across 
   [Number] systems. The overall risk rating is [Critical/High/Medium/Low].

   Findings by Severity:
   - Critical: [Number]
   - High: [Number]
   - Medium: [Number]
   - Low: [Number]
   - Informational: [Number]

3. CRITICAL FINDINGS
   [Business-impact description of each critical/high finding]

4. BUSINESS IMPACT
   [Financial, regulatory, and reputational impact analysis]

5. RECOMMENDATIONS
   [Prioritized remediation plan with timelines]

Writing Guidelines for Executive Summary

Do Don’t
Use plain business language Use technical jargon without explanation
Focus on risk and impact Focus on technical mechanics
Provide clear numbers and metrics Use vague descriptions like “several” or “many”
Prioritize findings by severity List findings chronologically
Recommend actionable next steps Leave remediation open-ended
Keep it concise (2-4 pages) Write a novel
Use charts and visualizations Use walls of text

Translating Technical to Business Language

Technical Description Business Translation
“SQL injection on login form allows database extraction” “Attackers can access all customer data including names, emails, and payment information”
“CVE-2024-1234 in Apache Struts 2.5.30 allows RCE” “Known critical vulnerability allows complete server takeover”
“Weak TLS 1.0 configuration detected” “Encrypted communications can be intercepted, exposing sensitive data in transit”
“Default credentials on admin panel” “Unauthorized users can access administrative functions without authentication”
“Local privilege escalation via kernel vulnerability” “An attacker with basic user access can gain complete control of the server”

3. Technical Report

Purpose

The technical report provides engineers, system administrators, and developers with everything needed to understand and fix the identified vulnerabilities.

Key Characteristics

  • Length: Varies by engagement size (15-50+ pages typical)
  • Tone: Technical, precise, reproducible
  • Primary goal: Enable remediation teams to fix vulnerabilities efficiently

Required Elements

  1. Detailed Methodology

    • Testing phases and approach
    • Tools and techniques used
    • Scope and limitations
  2. Individual Vulnerability Reports

    • Each vulnerability documented separately
    • Consistent structure for each finding
    • Unique identification number (e.g., VULN-001)
  3. Proof of Concept (PoC)

    • Step-by-step reproduction instructions
    • Exact commands and payloads used
    • Screenshots and evidence
  4. Technical Evidence

    • Command output
    • HTTP requests/responses
    • Network captures
    • Code snippets
  5. Remediation Guidance

    • Specific fix steps
    • Code examples
    • Configuration changes
    • Verification procedures
  6. References

    • CVE identifiers
    • CWE categories
    • Vendor advisories
    • OWASP guidance

Technical Report Structure per Finding

### VULN-001: [Vulnerability Title]

**Severity:** [Critical/High/Medium/Low]
**CVSS Score:** [Score] ([Vector String])
**Affected System:** [Hostname/IP]
**Affected Component:** [Specific component]
**Discovered:** [Date]

#### Summary
[Brief technical description]

#### Technical Details
[Detailed explanation of the vulnerability]

#### Proof of Concept
[Step-by-step reproduction with commands and output]

#### Evidence
[Screenshots and supporting evidence]

#### Impact
[Technical and business impact]

#### Remediation
[Specific fix steps with examples]

#### References
[CVEs, CWEs, advisories]

4. Full Report

Purpose

The full report serves as the complete record of the engagement, combining the executive summary, technical report, and supporting appendices into a single document.

Structure

FULL REPORT
├── Cover Page
├── Table of Contents
├── Document Control
├── Disclaimer
├── Executive Summary (2-4 pages)
├── Engagement Overview (2-3 pages)
├── Technical Overview (2-3 pages)
├── Findings (varies)
│   ├── VULN-001
│   ├── VULN-002
│   └── VULN-N
├── Risk Summary (1-2 pages)
├── Recommendations (2-3 pages)
├── Conclusion (1 page)
└── Appendices (varies)
    ├── Appendix A: Tool Output
    ├── Appendix B: Network Diagrams
    ├── Appendix C: Glossary
    ├── Appendix D: References
    └── Appendix E: Additional Evidence

The OSCP Report is a Full Report

For the OSCP exam, you are expected to produce a full report that includes:

  • An executive summary section
  • Technical findings for each machine you compromised
  • Proof of exploitation with screenshots
  • Remediation recommendations
  • References and appendices

5. Report Type Selection Matrix

When to Use Each Type

Scenario Recommended Report Type Reason
OSCP Exam Full Report Required by Offensive Security
Internal penetration test Full Report Complete record for internal teams
Compliance audit support Full Report + Raw Data Auditors need complete evidence
Quick vulnerability assessment Technical Report Technical team needs details
Board presentation Executive Summary + Slides Leadership needs high-level view
Client debrief meeting Executive Summary + Briefing Slides Discussion-focused presentation
Legal investigation Full Report + Chain of Custody Legal admissibility required

Layered Reporting Principle

The key insight is that the same findings can be presented at different detail levels for different audiences:

  1. Same data, different presentation: The SQL injection finding appears in the executive summary as “customer data exposure risk” and in the technical report as “UNION-based SQL injection on /login endpoint with full PoC.”
  2. Consistent numbering: VULN-001 in the executive summary references the same finding as VULN-001 in the technical report.
  3. Cross-referencing: The executive summary says “See Technical Finding VULN-001 for details” to guide technical readers to the full details.

6. Report Format Considerations

File Formats

Format Pros Cons Best For
PDF Fixed layout, universal, professional Hard to edit, large file size Final delivery, OSCP submission
Word (DOCX) Editable, track changes, templates Formatting can shift Drafting, client review
Markdown Lightweight, version control friendly Limited formatting Notes, internal documentation
LaTeX Professional typesetting, consistent Steep learning curve Academic, formal reports
HTML Web-friendly, interactive Not standard for delivery Internal portals, dashboards

OSCP Format Requirements

  • Accepted formats: PDF or Word document
  • Template: Use the Offensive Security provided template
  • Naming: Follow the naming convention specified in the exam instructions
  • Submission: Upload through the Proving Grounds portal within the deadline

7. Key Takeaways

  1. Three main report types: Executive Summary (management), Technical Report (engineers), Full Report (everyone).
  2. OSCP requires a Full Report with both executive summary and technical findings sections.
  3. Layered reporting means the same findings presented at different detail levels for different audiences.
  4. Executive summary is critical because it’s often the only section leadership reads.
  5. Technical report must be actionable with specific remediation steps engineers can follow.
  6. Consistency across layers through numbering, cross-referencing, and aligned messaging.

8. Further Reading

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