OSCP Report Writing: Offensive Security Report Format Requirements
1. OSCP Exam Report Requirements
The Two-Part Exam Structure
The OSCP exam consists of two parts:
| Part | Description | Time Limit | Passing Requirement |
|---|---|---|---|
| Practical Exam | 24-hour penetration testing window | 24 hours (can be taken within 24 hours of lab voucher) | Compromise required number of machines |
| Report | Written penetration test report | 1 working day after closing the exam | Must meet grading criteria |
Important: You must pass BOTH parts to earn the OSCP certification. Passing the practical exam does not guarantee certification if the report fails.
Mandatory Report Requirements
| Requirement | Description | Status |
|---|---|---|
| Format | PDF or Word document | Mandatory |
| Template | Use the Offensive Security provided template | Mandatory |
| Executive Summary | High-level overview for management | Mandatory |
| Technical Findings | Each machine with vulnerabilities and exploitation details | Mandatory |
| Proof of Exploitation | Evidence of successful exploitation (screenshots) | Mandatory |
| Remediation | Recommendations for each finding | Mandatory |
| Original Work | Must be your own writing | Mandatory |
| Plagiarism-Free | No copied content from other sources | Mandatory |
| Professional Quality | Proper formatting, grammar, and spelling | Mandatory |
2. OSCP Report Structure (Required)
Required Sections
OSCP EXAM REPORT
├── Executive Summary
│ ├── Engagement Overview
│ ├── Overall Risk Assessment
│ └── Summary of Findings
├── Technical Findings
│ ├── Machine 1 - [IP Address]
│ │ ├── Vulnerabilities Found
│ │ ├── Exploitation Steps
│ │ ├── Proof Screenshots
│ │ └── Remediation
│ ├── Machine 2 - [IP Address]
│ │ ├── Vulnerabilities Found
│ │ ├── Exploitation Steps
│ │ ├── Proof Screenshots
│ │ └── Remediation
│ └── Machine N - [IP Address]
│ ├── Vulnerabilities Found
│ ├── Exploitation Steps
│ ├── Proof Screenshots
│ └── Remediation
└── Appendix
├── References
├── Tools Used
└── Glossary (optional)
Section-by-Section Requirements
Executive Summary
Required Content:
- Brief overview of the engagement
- Overall risk assessment
- Summary of findings by severity
- High-level recommendations
Minimum Length: At least 1 paragraph (but should be more comprehensive)
Writing Style: Professional, concise, business-focused
Technical Findings
Required Content per Machine:
- Machine IP address and hostname (if discovered)
- Vulnerabilities discovered and exploited
- Step-by-step exploitation process
- Screenshots as evidence
- Remediation recommendations
Minimum Content:
- At least one finding per machine you claim to have compromised
- Screenshots showing successful exploitation
- Screenshots showing flag capture (user.txt and root.txt/proof.txt)
Appendix
Required Content:
- References to sources used (exploits, tools, documentation)
- List of tools used during the engagement
Optional Content:
- Glossary of terms
- Additional screenshots
- Tool output
3. OSCP-Specific Requirements
Per-Machine Documentation
For each machine you compromised, you must document:
| Element | What to Include | Why It Matters |
|---|---|---|
| Machine IP address | All target IPs tested | Scope verification |
| Initial reconnaissance | nmap output, service enumeration | Shows your methodology |
| Vulnerability identification | How you found the vulnerability | Demonstrates skill |
| Exploitation steps | Step-by-step for each machine | Reproducibility |
| Screenshots | Evidence of each step | Verification |
| User flag capture | Screenshot of reading user.txt | Proof of user access |
| Privilege escalation | How you escalated privileges | Demonstrates advanced skill |
| Root flag capture | Screenshot of reading root.txt/proof.txt | Proof of full compromise |
| Vulnerability descriptions | What was exploited and why | Technical understanding |
| Remediation | How to fix each issue | Professional value |
Screenshot Requirements
Minimum screenshots per machine:
- Initial scan output (nmap)
- Vulnerability identification
- Exploitation command/payload
- Successful shell access
- User flag capture (user.txt)
- Privilege escalation method
- Root flag capture (root.txt/proof.txt)
Screenshot quality requirements:
- Clear and readable
- Show the full context (command + output)
- Annotated if necessary
- Properly named and referenced in the text
4. OSCP Report Grading Criteria
Grading Rubric
| Criteria | Weight | Description |
|---|---|---|
| Completeness | High | All machines and findings documented |
| Clarity | High | Easy to understand and follow |
| Technical Accuracy | High | Correct vulnerability descriptions and exploitation steps |
| Evidence Quality | Medium | Clear and relevant screenshots |
| Remediation Quality | Medium | Actionable and specific recommendations |
| Professionalism | Medium | Proper formatting, grammar, and spelling |
| Originality | Critical | Must be your own work (plagiarism = automatic failure) |
What Graders Look For
-
Did you actually do the work?
- Screenshots should match the described steps
- Commands should be consistent with the output shown
- Timeline should be logical and consistent
-
Do you understand what you did?
- Vulnerability descriptions should be accurate
- Exploitation steps should be explained, not just listed
- Remediation should be relevant to the specific finding
-
Is the report professional?
- Proper grammar and spelling
- Consistent formatting
- Clear and organized structure
-
Is the work original?
- Written in your own words
- No copied content from exploits, tutorials, or other sources
- References are properly cited
Common Reasons for Report Failure
| Reason | Description | How to Avoid |
|---|---|---|
| Plagiarism | Copied content from other sources | Write everything in your own words |
| Missing evidence | No screenshots or insufficient proof | Take screenshots at every step |
| Incomplete findings | Missing machines or vulnerabilities | Document every machine you compromised |
| Poor quality | Bad grammar, spelling, or formatting | Proofread multiple times |
| Missing remediation | No fix recommendations | Include remediation for each finding |
| Missing flags | No proof of user.txt/root.txt capture | Always show flag capture screenshots |
| Wrong template | Not using the provided template | Use the Offensive Security template |
| Late submission | Submitted after the deadline | Submit well before the deadline |
5. Practical Tips for OSCP Report
During the 24-Hour Exam
- Document as you go. Don’t wait until the end to start documenting.
- Take screenshots at every step. You will forget details later.
- Copy command output to a notes file. Use this as raw material for the report.
- Record timestamps. Note when you started and finished each machine.
- Save all exploit code. You’ll need to reference it in the report.
- Keep a lab notebook. Record your thought process and decisions.
During the Report Writing Day
- Start with the template. Use the Offensive Security provided template.
- Write in past tense. “I exploited…” not “I will exploit…”
- Be thorough. Document every step, even if it seems obvious.
- Be honest. Report what you actually did, not what you think you should have done.
- Include exact commands. Copy from your terminal history.
- Proofread. Check for grammar, spelling, and formatting errors.
- Verify screenshots. Make sure they match the described steps.
- Submit early. Don’t wait until the last minute.
Writing Style Guidelines
| Guideline | Description |
|---|---|
| Past tense | Write in past tense (“I ran nmap” not “I will run nmap”) |
| First person | Use first person (“I discovered” not “the tester discovered”) |
| Active voice | Use active voice (“I exploited the vulnerability” not “the vulnerability was exploited”) |
| Clear and concise | Avoid unnecessary words and jargon |
| Professional tone | Maintain a professional, objective tone throughout |
| Consistent formatting | Use consistent headings, fonts, and styles |
Common Writing Mistakes to Avoid
| Mistake | Correction |
|---|---|
| “I used Metasploit to get a shell” | “I used the Metasploit Framework module exploit/multi/http/apache_struts2_content_type_ognl to obtain a reverse shell” |
| “The machine was easy” | “The machine was compromised through a known vulnerability in Apache Struts 2.5.30” |
| “I found a vulnerability” | “During enumeration, I identified that the Apache Struts application was running version 2.5.30, which is vulnerable to CVE-2024-1234” |
| “I escalated to root” | “I achieved local privilege escalation to root by exploiting a kernel vulnerability (CVE-2019-13272) in the running kernel version 4.15.0-20-generic” |
6. Report Submission
Submission Requirements
| Requirement | Details |
|---|---|
| Format | PDF or Word document |
| Naming | Follow the naming convention specified in the exam instructions |
| Upload | Through the Proving Grounds portal |
| Deadline | 1 working day after closing the exam |
| File size | No specific limit, but keep reasonable |
Pre-Submission Checklist
□ Used the Offensive Security provided template
□ Executive summary is complete and professional
□ All compromised machines are documented
□ Each machine has:
□ Vulnerability description
□ Exploitation steps
□ Screenshots as evidence
□ User flag capture screenshot
□ Privilege escalation documentation
□ Root flag capture screenshot
□ Remediation recommendations
□ All screenshots are clear and readable
□ All commands are included with output
□ References are included
□ Report is free of spelling and grammar errors
□ Report is saved in the correct format (PDF or Word)
□ Report is named correctly
□ Report is original work (no plagiarism)
7. Key Takeaways
- Use the provided template. Do not create your own format.
- Document every machine. Include all machines you compromised.
- Show flag capture. Always include screenshots of user.txt and root.txt/proof.txt.
- Be thorough. Document every step with screenshots and commands.
- Be original. Write in your own words. Plagiarism = automatic failure.
- Be professional. Proofread for grammar, spelling, and formatting.
- Submit on time. Don’t wait until the last minute.
- Start early. Begin documenting during the 24-hour exam window.
8. Further Reading
- Offensive Security OSCP Exam Guide (provided with course)
- Offensive Security Report Template (provided with course)
- OSCP Exam FAQ: https://www.offensive-security.com/oscp-exam-faq/