OSCP Report Writing: Report Templates and Standards
1. Industry Standards and Frameworks
Why Standards Matter
Industry standards provide a consistent, recognized framework for penetration testing and reporting. Using established standards:
- Ensures completeness. Standards define what must be included in a report.
- Demonstrates professionalism. Following standards shows you know the industry expectations.
- Enables comparison. Standardized reports can be compared across engagements and organizations.
- Supports compliance. Many regulations reference specific standards.
- Improves quality. Standards are based on years of industry experience and best practices.
Major Standards Overview
| Standard | Organization | Focus Area | Report Requirements |
|---|---|---|---|
| PTES | Penetration Testing Execution Standard | Complete testing lifecycle | Technical report, executive summary, methodology documentation |
| OSSTMM | Open Source Security Testing Methodology | Operational security testing | Test plan, results, metrics, recommendations |
| ISSAF | Information Systems Security Assessment | Comprehensive assessment | Executive summary, technical findings, risk assessment |
| NIST SP 800-115 | NIST | Technical guide for security testing | Scope definition, risk assessment, findings, recommendations |
| OWASP Testing Guide | OWASP | Web application testing | Web-specific findings, CVSS scoring, remediation guidance |
| ISO 27001 | ISO | Information security management | Risk-based approach, management review, continuous improvement |
| PCI-DSS | PCI SSC | Payment card security | Quarterly external scans, annual penetration test, detailed report |
| COBIT | ISACA | IT governance and management | Control objectives, risk assessment, compliance reporting |
2. PTES (Penetration Testing Execution Standard)
Overview
PTES is one of the most widely adopted penetration testing frameworks. It defines a complete testing lifecycle with seven phases.
PTES Phases
| Phase | Description | Report Section |
|---|---|---|
| 1. Pre-Engagement Interactions | Scope definition, rules of engagement, legal authorization | Engagement Overview, Disclaimer |
| 2. Intelligence Gathering | Open-source intelligence, reconnaissance | Technical Overview, Appendix |
| 3. Threat Modeling | Identifying potential threats and attack vectors | Technical Overview |
| 4. Vulnerability Analysis | Identifying and validating vulnerabilities | Findings |
| 5. Exploitation | Attempting to exploit vulnerabilities | Findings, PoC |
| 6. Post-Exploitation | Maintaining access, privilege escalation, lateral movement | Findings, PoC |
| 7. Reporting | Documenting findings and recommendations | Full Report |
PTES Report Requirements
PTES requires the following report components:
- Executive Summary: High-level overview for management
- Technical Report: Detailed findings with technical evidence
- Methodology Documentation: Description of testing approach
- Risk Assessment: Risk rating for each finding
- Recommendations: Prioritized remediation guidance
- Appendices: Supporting documentation and raw data
PTES Report Template Structure
PTES Report
├── 1. Executive Summary
├── 2. Technical Report
│ ├── 2.1 Methodology
│ ├── 2.2 Scope
│ ├── 2.3 Findings
│ │ ├── 2.3.1 Finding 1
│ │ ├── 2.3.2 Finding 2
│ │ └── 2.3.N Finding N
│ └── 2.4 Risk Assessment
├── 3. Recommendations
├── 4. Conclusion
└── 5. Appendices
├── A. Tool Output
├── B. References
└── C. Glossary
3. NIST SP 800-115
Overview
NIST SP 800-115 is the National Institute of Standards and Technology’s technical guide for information security testing and assessment. It is widely used in government and enterprise environments.
NIST Testing Phases
| Phase | Description | Report Section |
|---|---|---|
| 1. Preparation | Planning, scoping, and resource allocation | Engagement Overview |
| 2. Execution | Conducting the security testing | Findings, Evidence |
| 3. Post-Execution | Reporting, follow-up, and remediation verification | Full Report |
NIST Report Requirements
NIST SP 800-115 requires:
- Scope Definition: What was tested and what was excluded
- Methodology: Testing approach and techniques used
- Findings: Detailed vulnerability documentation
- Risk Assessment: Risk rating and business impact
- Recommendations: Prioritized remediation guidance
- Follow-up Plan: Plan for remediation verification
4. OWASP Testing Guide
Overview
The OWASP Testing Guide is the definitive guide for web application security testing. It is essential for any engagement involving web applications.
OWASP Testing Phases
| Phase | Tests Included | Report Section |
|---|---|---|
| 1. Information Gathering | Application inventory, technology identification | Technical Overview |
| 2. Configuration and Deployment Management | Server config, framework config, network config | Findings |
| 3. Identity Management | Authentication, session management, authorization | Findings |
| 4. Authorization Testing | Access control, function-level, file-level | Findings |
| 5. Session Management | Session handling, cookie flags, token management | Findings |
| 6. Input Validation | Injection, XSS, file upload, CSRF | Findings |
| 7. Error Handling | Error messages, stack traces, debug info | Findings |
| 8. Authentication Testing | Credential strength, MFA, password reset | Findings |
| 9. Business Logic Testing | Workflow manipulation, state manipulation | Findings |
| 10. Cryptography Testing | Encryption, key management, certificate validation | Findings |
| 11. Weak Logging | Log content, log security, audit trails | Findings |
| 12. Client-side Testing | JavaScript, HTML5, browser security | Findings |
OWASP Report Requirements
OWASP recommends:
- Finding Description: Clear description of the vulnerability
- Risk Rating: CVSS score and risk level
- Proof of Concept: Step-by-step reproduction instructions
- Impact: Technical and business impact
- Remediation: Specific fix guidance with code examples
- References: OWASP Top 10 category, CWE, CVE
5. Report Template Sources
Available Templates
| Source | Format | Cost | Notes |
|---|---|---|---|
| Offensive Security | PDF/Word | Included with OSCP | Official OSCP template, mandatory for exam |
| Rapid7 | Word | Free | Professional quality, customizable |
| Qualys | Word | Free | Comprehensive, enterprise-focused |
| PTES | Free | Framework-aligned template | |
| Custom | Markdown/PDF | Free | Tailored to your style and needs |
| LaTeX templates | LaTeX | Free | Academic quality, professional typesetting |
Offensive Security Template (OSCP)
The Offensive Security report template is the mandatory template for the OSCP exam. It includes:
- Executive Summary section
- Technical Findings section (per machine)
- Appendix section
Key requirements:
- Must use the provided template
- Must be in PDF or Word format
- Must include all required sections
- Must be original work (no plagiarism)
6. Customizing Templates
When to Customize
| Scenario | Customization Level |
|---|---|
| OSCP Exam | None (use provided template exactly) |
| Internal engagement | Moderate (add internal branding, adjust sections) |
| Client engagement | High (client branding, specific requirements) |
| Compliance audit | High (compliance-specific sections, mappings) |
| Bug bounty | Low (platform-specific format) |
Customization Best Practices
| Practice | Description |
|---|---|
| Maintain structure | Keep the standard report structure even when customizing |
| Add, don’t remove | Add sections as needed, but don’t remove required sections |
| Consistent branding | Use consistent colors, fonts, and logos |
| Version control | Track template changes over time |
| Review regularly | Update templates to reflect current standards and practices |
7. Report Standards Compliance
Compliance Mapping
| Regulation | Standard Reference | Report Requirements |
|---|---|---|
| PCI-DSS | Requirement 11.3 | Annual penetration test, detailed report, remediation plan |
| HIPAA | NIST 800-66 | Risk assessment, security testing, remediation |
| SOC 2 | Trust Services Criteria | Security testing evidence, remediation tracking |
| ISO 27001 | Control A.12.6.1 | Technical vulnerability management, testing |
| GDPR | Article 32 | Security testing, risk assessment, remediation |
| FedRAMP | NIST 800-53 | Security assessment, penetration testing, reporting |
Standards Alignment Checklist
□ Report follows recognized standard (PTES, NIST, OWASP)
□ Executive summary included
□ Technical findings documented with consistent structure
□ CVSS scores provided for each finding
□ Risk assessment included
□ Remediation recommendations provided
□ Evidence and screenshots included
□ References to CVEs, CWEs, and standards included
□ Document control and version history included
□ Disclaimer and scope definition included
8. Key Takeaways
- Use established standards. PTES, NIST, and OWASP provide recognized frameworks for reporting.
- For OSCP: Use the Offensive Security provided template. Do not create your own.
- Standards ensure completeness. They define what must be included in a professional report.
- Customize when appropriate. Adapt templates to client and engagement specifics, but maintain the core structure.
- Compliance matters. Many regulations reference specific standards for penetration testing reports.
- Version control. Track template changes and review regularly.
- Consistency is key. Use the same template structure across all engagements.
9. Further Reading
- PTES Official Website: https://www.pentest-standard.org/
- NIST SP 800-115: https://nvlpubs.nist.gov/nistpubs/SpecialPublications/800-115.pdf
- OWASP Testing Guide: https://owasp.org/www-project-web-security-testing-guide/
- ISO 27001: https://www.iso.org/standard/27001
- PCI-DSS Requirements: https://www.pcisecuritystandards.org/