OSCP Report Writing: Executive Summary Writing
1. Purpose and Audience
Why the Executive Summary Matters Most
The executive summary is the most important section of your report because it is often the only section that decision-makers will read. If you cannot communicate risk effectively in this section, the rest of your report may never be seen by the people who need to act on it.
Primary Audience
| Audience Member | What They Need | How They Use the Report |
|---|---|---|
| CISO | Risk overview, budget justification, compliance status | Decides resource allocation and prioritization |
| CTO | Technical impact, remediation effort, timeline | Plans engineering resources and schedules |
| VP of Engineering | Team impact, development effort required | Assigns remediation tasks to teams |
| Board Members | Business risk, financial exposure, strategic direction | Makes high-level risk acceptance decisions |
| External Auditors | Evidence of security testing and due diligence | Verifies compliance with regulatory requirements |
Reading Time Constraint
The executive summary should be consumable in 5-10 minutes. This means:
- 2-4 pages maximum
- Clear headings and short paragraphs
- Bullet points over prose where possible
- Charts and tables for quick comprehension
- No technical deep-dives
2. Executive Summary Structure
Required Sections
EXECUTIVE SUMMARY
├── 1. Engagement Overview
├── 2. Overall Risk Assessment
├── 3. Key Findings Summary
├── 4. Business Impact
├── 5. Strategic Recommendations
└── 6. Remediation Timeline
Section 1: Engagement Overview
Purpose: Set the context for the reader.
Content:
- What was tested (scope)
- Why the test was performed (objective)
- When the test occurred (timeline)
- How the test was performed (methodology, high-level)
Example:
Offensive Security conducted an internal penetration test of
Acme Corporation's network infrastructure from August 1-5, 2026.
The engagement targeted 15 systems across 3 subnets, including
web servers, domain controllers, and database servers. The test
followed a black-box methodology with no prior knowledge of the
target environment.
Section 2: Overall Risk Assessment
Purpose: Provide a quick understanding of the overall security posture.
Content:
- Overall risk rating (Critical / High / Medium / Low)
- Number of findings by severity
- Visual representation (chart or table)
Example:
The penetration test identified 12 vulnerabilities across 8 systems.
The overall risk rating is HIGH.
Findings by Severity:
┌─────────────┬───────┬──────────┐
│ Severity │ Count │ Percent │
├─────────────┼───────┼──────────┤
│ Critical │ 2 │ 17% │
│ High │ 3 │ 25% │
│ Medium │ 4 │ 33% │
│ Low │ 2 │ 17% │
│ Informational │ 1 │ 8% │
└─────────────┴───────┴──────────┘
Section 3: Key Findings Summary
Purpose: Highlight the most important findings in business terms.
Content:
- Limit to Critical and High findings only
- Describe each in business terms (not technical terms)
- Include business impact for each
- Reference the technical finding ID for cross-reference
Example:
Critical Findings:
1. Complete Server Compromise via Web Application Vulnerability (VULN-001)
A critical vulnerability in the customer portal web application
allows attackers to execute arbitrary commands on the server.
This could result in complete compromise of the system and
exposure of all customer data stored on the server.
2. Domain Administrator Access via Credential Reuse (VULN-002)
Weak and reused passwords across multiple systems allowed
escalation from a single compromised account to full domain
administrator access, potentially compromising all systems
in the Active Directory environment.
Section 4: Business Impact
Purpose: Quantify the business consequences of the findings.
Content:
- Potential financial impact
- Regulatory compliance implications
- Reputational risk
- Operational disruption potential
Example:
The identified vulnerabilities pose significant business risks:
- Data Breach Risk: The web application vulnerability could allow
unauthorized access to customer data including names, email
addresses, and payment information for approximately 50,000
customers.
- Regulatory Impact: A data breach involving customer payment
information could result in PCI-DSS non-compliance, potential
fines, and mandatory breach notification requirements.
- Operational Disruption: Complete server compromise could result
in service downtime, data loss, and extended recovery time.
- Reputational Damage: A publicized security breach could erode
customer trust and result in customer churn.
Section 5: Strategic Recommendations
Purpose: Provide clear, prioritized next steps.
Content:
- Immediate actions (0-30 days)
- Short-term actions (30-90 days)
- Long-term improvements (90+ days)
Example:
Immediate Actions (0-30 days):
1. Patch the web application vulnerability on the customer portal server
2. Force password reset for all domain accounts
3. Implement multi-factor authentication for administrative access
Short-term Actions (30-90 days):
1. Deploy a web application firewall for all public-facing applications
2. Implement network segmentation to limit lateral movement
3. Conduct organization-wide vulnerability assessment
Long-term Improvements (90+ days):
1. Establish a regular penetration testing program (quarterly)
2. Implement a security awareness training program
3. Develop and test an incident response plan
Section 6: Remediation Timeline
Purpose: Provide a realistic timeline for risk reduction.
Content:
- Prioritized remediation schedule
- Resource requirements
- Expected risk reduction at each milestone
Example:
Remediation Timeline:
Week 1-2: Address Critical findings (expected risk reduction: 40%)
Week 3-4: Address High findings (expected risk reduction: 70%)
Month 2-3: Address Medium findings (expected risk reduction: 90%)
Month 4+: Implement long-term improvements (sustained risk reduction)
3. Writing Guidelines
Language and Tone
| Guideline | Description | Example |
|---|---|---|
| Plain language | Avoid technical jargon | “Attackers can access customer data” not “SQLi enables UNION-based data exfiltration” |
| Active voice | Use direct, clear statements | “We found a vulnerability” not “A vulnerability was found” |
| Quantify | Use numbers and metrics | “50,000 customer records” not “many customer records” |
| Be specific | Name systems and impacts | “The customer portal server” not “one of the servers” |
| Be honest | Don’t exaggerate or minimize | “High risk” not “Critical emergency” |
| Be concise | Every sentence should add value | Remove filler words and redundant statements |
The Jargon Translation Table
| Technical Term | Business Translation |
|---|---|
| SQL Injection | Database vulnerability allowing unauthorized data access |
| Remote Code Execution (RCE) | Ability to run arbitrary programs on the server |
| Cross-Site Scripting (XSS) | Ability to inject malicious scripts into web pages |
| Privilege Escalation | Ability to gain higher-level access than intended |
| Brute Force Attack | Systematic password guessing attack |
| Man-in-the-Middle | Interception of communications between communicating parties |
| Buffer Overflow | Software vulnerability allowing code execution |
| Directory Traversal | Ability to access files outside intended directory |
| Server-Side Request Forgery (SSRF) | Ability to force server to access internal resources |
| XML External Entity (XXE) | Ability to read local files through XML processing |
Visual Elements
Effective executive summaries use visual elements to convey information quickly:
- Findings Distribution Chart: Bar chart or pie chart showing findings by severity
- Risk Matrix: Visual representation of likelihood vs. impact
- Timeline Gantt Chart: Remediation timeline visualization
- Summary Tables: Quick-reference tables for key metrics
4. Common Executive Summary Mistakes
Mistake 1: Too Technical
Bad: “The application is vulnerable to UNION-based SQL injection via the ‘username’ parameter in the POST request to /api/login, which allows extraction of the ‘users’ table from the MySQL 5.7 backend database.”
Good: “A critical vulnerability in the user login page allows attackers to access the entire customer database, potentially exposing 50,000 customer records including names, email addresses, and encrypted passwords.”
Mistake 2: Too Vague
Bad: “Several vulnerabilities were found that need to be fixed.”
Good: “Twelve vulnerabilities were identified across eight systems, including two critical findings that allow complete server compromise and unauthorized access to customer data.”
Mistake 3: No Business Context
Bad: “SQL injection found on /login endpoint. CVSS 9.8.”
Good: “A critical vulnerability in the customer login page (CVSS 9.8) allows attackers to access the entire customer database of 50,000 records. This could result in regulatory fines under PCI-DSS and significant reputational damage.”
Mistake 4: Listing All Findings
Bad: Including every finding (including Low and Informational) in the executive summary.
Good: Limiting the executive summary to Critical and High findings only, with a summary table showing the full distribution.
Mistake 5: No Recommendations
Bad: Ending the executive summary with findings but no guidance on what to do next.
Good: Including clear, prioritized recommendations with timelines for remediation.
5. Executive Summary Template (Complete)
EXECUTIVE SUMMARY
1. ENGAGEMENT OVERVIEW
[Company] conducted a penetration test of [Client]'s [environment]
from [Start Date] to [End Date]. The engagement targeted [Number]
systems within the scope of [Scope Description]. The test followed
a [Methodology Type] methodology.
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
Immediate Actions (0-30 days):
1. [Specific action]
2. [Specific action]
3. [Specific action]
Short-term Actions (30-90 days):
1. [Specific action]
2. [Specific action]
Long-term Improvements (90+ days):
1. [Specific action]
2. [Specific action]
6. REMEDIATION TIMELINE
[Timeline with expected risk reduction at each milestone]
6. Key Takeaways
- The executive summary is the most read section. Make it count.
- Write for non-technical readers. Use plain language and business terms.
- Limit to 2-4 pages. Be concise and focused.
- Focus on Critical and High findings. Don’t clutter with low-severity issues.
- Translate technical to business. Every finding should have a business impact statement.
- Provide clear recommendations. Tell the reader exactly what to do next.
- Use visual elements. Charts and tables convey information faster than text.
- Cross-reference technical findings. Use finding IDs so technical readers can dive deeper.
7. Further Reading
- SANS Executive Summary Best Practices
- OWASP Reporting Guidelines
- NIST SP 800-115 Executive Summary Section
- “The Business of Information Security” by Gary McGraw