OSCP Report Writing: Appendices and Supporting Documentation
1. Purpose of Appendices
Why Appendices Matter
Appendices provide supporting documentation that would clutter the main body of the report but is still important for completeness, verification, and reference. They serve several key purposes:
- Completeness: Include all raw data and supporting evidence without overwhelming the main report.
- Verification: Allow auditors and reviewers to verify findings with raw data.
- Reference: Provide quick access to tools, commands, and resources used.
- Clarity: Keep the main report focused on findings and recommendations.
- Professionalism: Demonstrate thorough documentation practices.
Appendix Types
| Appendix | Content | When to Include | OSCP Relevance |
|---|---|---|---|
| A: Tool Output | Raw scanner output, nmap results, scan logs | Always | High |
| B: Network Diagrams | Target architecture, network topology | When relevant | Medium |
| C: Glossary | Technical terms and abbreviations | For non-technical readers | Low |
| D: References | CVEs, advisories, documentation, exploit sources | Always | High |
| E: Additional Evidence | Extra screenshots, captures, logs | When space is limited in main body | Medium |
| F: Custom Scripts | Exploitation scripts, enumeration scripts | When used | Medium |
| G: Configuration | Tool configurations, settings, parameters | When relevant | Low |
| H: Legal Documents | Rules of engagement, authorization letters | Always (professional engagements) | Low (OSCP provides this) |
2. Appendix A: Tool Output
Purpose
Include raw output from scanning and enumeration tools to support findings in the main report.
What to Include
| Tool | Output to Include | Format |
|---|---|---|
| nmap | Full scan output (ports, services, OS detection) | Plain text |
| Nessus/OpenVAS | Scan summary and critical findings | PDF/HTML |
| Burp Suite | Site map, request/response logs | JSON/Burp project |
| enum4linux | SMB enumeration output | Plain text |
| gobuster/dirb | Directory enumeration results | Plain text |
| LinPEAS/WinPEAS | Privilege escalation enumeration output | Plain text |
| searchsploit | Exploit search results | Plain text |
Tool Output Template
#### Appendix A: Tool Output
##### A.1: nmap Initial Scan
Target: 10.10.10.100
Command: nmap -sC -sV -oA initial 10.10.10.100
Date: 2026-08-06
Nmap 7.94 scan initiated Mon Aug 6 10:00:00 2026 as: nmap -sC -sV -oA initial 10.10.10.100
Nmap scan report for 10.10.10.100 Host is up (0.0023s latency). Not shown: 998 closed ports PORT STATE SERVICE VERSION 22/tcp open ssh OpenSSH 7.2p2 Ubuntu 4ubuntu2.2 80/tcp open http Apache httpd 2.4.18 ((Ubuntu)) |_http-title: Welcome to Struts Showcase |_http-server-header: Apache/2.4.18 (Ubuntu) Service Info: OS: Linux; CPE: cpe:/o:linux:linux_kernel
Service detection performed.
Nmap done at Mon Aug 6 10:05:00 2026 – 1 IP address (1 host up) scanned in 300.00 seconds
##### A.2: nmap Full Port Scan
Target: 10.10.10.100
Command: nmap -p- -oA fullscan 10.10.10.100
Date: 2026-08-06
Nmap 7.94 scan initiated Mon Aug 6 10:10:00 2026
PORT STATE SERVICE 22/tcp open ssh 80/tcp open http
Nmap done at Mon Aug 6 10:25:00 2026
##### A.3: Directory Enumeration
Target: http://10.10.10.100
Command: gobuster dir -u http://10.10.10.100 -w /usr/share/wordlists/dirb/common.txt
Date: 2026-08-06
/admin (Status: 200) /backup (Status: 200) /showcase (Status: 200) /login (Status: 200)
3. Appendix C: Glossary
Purpose
Provide definitions for technical terms and abbreviations used in the report, especially for non-technical readers.
Glossary Template
#### Appendix C: Glossary
| Term | Definition |
|---|---|
| **CVSS** | Common Vulnerability Scoring System - industry standard for rating vulnerability severity (0.0-10.0) |
| **CVE** | Common Vulnerabilities and Exposures - unique identifier for publicly disclosed security vulnerabilities |
| **CWE** | Common Weakness Enumeration - standardized list of software weakness types |
| **RCE** | Remote Code Execution - ability to execute arbitrary code on a remote system |
| **SQLi** | SQL Injection - injecting malicious SQL code into application queries to manipulate the database |
| **XSS** | Cross-Site Scripting - injecting malicious scripts into web pages viewed by other users |
| **SSRF** | Server-Side Request Forgery - forcing a server to make requests to internal or external resources |
| **XXE** | XML External Entity - exploiting XML parser to access local files or make network requests |
| **IDOR** | Insecure Direct Object Reference - accessing resources by manipulating identifiers (e.g., user IDs) |
| **PoC** | Proof of Concept - demonstration that a vulnerability is real and exploitable |
| **WAF** | Web Application Firewall - security appliance that filters and monitors HTTP traffic |
| **MFA** | Multi-Factor Authentication - requiring multiple forms of verification for authentication |
| **PII** | Personally Identifiable Information - data that can identify an individual |
| **LPE** | Local Privilege Escalation - gaining higher-level access on a system you already have access to |
| **SUID** | Set User ID - Linux permission that allows a file to execute with the permissions of its owner |
| **CVE-XXXX-XXXX** | Specific vulnerability identifier (e.g., CVE-2019-13272 is a Linux kernel privilege escalation vulnerability) |
| **Reverse Shell** | A shell connection where the target connects back to the attacker's machine |
| **Bind Shell** | A shell connection where the attacker connects to a port opened on the target machine |
| **Brute Force** | Systematically trying all possible combinations to guess credentials or passwords |
| **Pass-the-Hash** | Authentication attack using a stolen NTLM hash instead of the actual password |
4. Appendix D: References
Purpose
Provide sources and references for vulnerabilities, exploits, tools, and documentation used during the engagement.
References Template
#### Appendix D: References
##### Vulnerability References
| Reference | URL | Relevance |
|---|---|---|
| CVE-2024-1234 | https://nvd.nist.gov/vuln/detail/CVE-2024-1234 | Apache Struts Content-Type OGNL injection |
| CVE-2019-13272 | https://nvd.nist.gov/vuln/detail/CVE-2019-13272 | Linux kernel OverlayFS privilege escalation |
| CVE-2021-41773 | https://nvd.nist.gov/vuln/detail/CVE-2021-41773 | ProxyLogon Microsoft Exchange vulnerability |
| CVE-2021-44228 | https://nvd.nist.gov/vuln/detail/CVE-2021-44228 | Log4Shell remote code execution |
##### Exploit Sources
| Reference | URL | Relevance |
|---|---|---|
| Exploit-DB | https://www.exploit-db.com/ | Public exploit database |
| Packet Storm | https://packetstormsecurity.com/ | Security tools and exploits |
| GitHub Exploits | https://github.com/ | Community-contributed exploits |
##### Security Frameworks and Standards
| Reference | URL | Relevance |
|---|---|---|
| OWASP Top 10 | https://owasp.org/www-project-top-ten/ | Web application security risks |
| OWASP Testing Guide | https://owasp.org/www-project-web-security-testing-guide/ | Web application testing methodology |
| NIST SP 800-115 | https://nvlpubs.nist.gov/nistpubs/SpecialPublications/800-115.pdf | Security testing technical guide |
| CVSS v3.1 | https://www.first.org/cvss/v3.1/specification-document | Vulnerability scoring standard |
| MITRE ATT&CK | https://attack.mitre.org/ | Adversary tactics and techniques |
| PTES | https://www.pentest-standard.org/ | Penetration testing execution standard |
##### Tool Documentation
| Reference | URL | Relevance |
|---|---|---|
| nmap | https://nmap.org/book/ | Network scanner documentation |
| Metasploit | https://docs.metasploit.com/ | Exploitation framework documentation |
| Burp Suite | https://portswigger.net/burp/documentation | Web testing proxy documentation |
| John the Ripper | https://www.openwall.com/john/ | Password cracker documentation |
##### Remediation References
| Reference | URL | Relevance |
|---|---|---|
| OWASP Cheat Sheets | https://cheatsheetseries.owasp.org/ | Secure coding guidance |
| CIS Controls | https://www.cisecurity.org/controls | Security best practices |
| Ubuntu Security Notices | https://ubuntu.com/security/notices | Ubuntu patch information |
| Microsoft Security Updates | https://msrc.microsoft.com/update-guide | Windows patch information |
5. Appendix E: Additional Evidence
Purpose
Include additional evidence that supports findings but would clutter the main report body.
What to Include
| Evidence Type | Description | When to Include |
|---|---|---|
| Additional Screenshots | Extra screenshots not in the main body | When the main body is already dense |
| Network Captures | PCAP files or Wireshark exports | When network analysis is relevant |
| Log Entries | System/application log excerpts | When log analysis supports a finding |
| File Contents | Sensitive file contents (redacted) | When file contents support a finding |
| HTTP Transactions | Full Burp Suite request/response pairs | When HTTP analysis is relevant |
Additional Evidence Template
#### Appendix E: Additional Evidence
##### E.1: HTTP Request/Response - SQL Injection
**Request:**
```http
POST /login HTTP/1.1
Host: 10.10.10.100
Content-Type: application/x-www-form-urlencoded
User-Agent: Mozilla/5.0
username=admin' OR '1'='1'--&password=test
Response:
HTTP/1.1 302 Found
Location: /dashboard
Set-Cookie: session=abc123def456; HttpOnly
Content-Type: text/html
E.2: Network Capture Summary
Tool: Wireshark Capture Duration: 2026-08-06 10:00:00 to 2026-08-06 10:30:00 Interface: eth0
| Protocol | Count | Percentage |
|---|---|---|
| TCP | 1,234 | 65% |
| HTTP | 567 | 30% |
| DNS | 45 | 2% |
| ICMP | 34 | 1% |
| Other | 54 | 2% |
## 6. Appendix F: Custom Scripts
### Purpose
Include custom exploitation or enumeration scripts used during the engagement.
### What to Include
| Script Type | Description | When to Include |
|---|---|---|
| **Exploitation Scripts** | Custom exploit code | When you wrote or modified an exploit |
| **Enumeration Scripts** | Custom enumeration tools | When you wrote custom enumeration scripts |
| **Automation Scripts** | Scripts for repetitive tasks | When automation was used |
| **Post-Exploitation Scripts** | Custom post-exploitation tools | When custom tools were used |
### Custom Scripts Template
```markdown
#### Appendix F: Custom Scripts
##### F.1: SQL Injection Testing Script
```python
#!/usr/bin/env python3
"""
SQL Injection Testing Script
Target: http://10.10.10.100/login
"""
import requests
TARGET = "http://10.10.10.100/login"
def test_auth_bypass():
data = {
'username': "' OR '1'='1'--",
'password': "anything"
}
response = requests.post(TARGET, data=data, allow_redirects=False)
if response.status_code == 302:
print("[+] Authentication bypass confirmed!")
return True
return False
if __name__ == "__main__":
test_auth_bypass()
## 7. Appendix Organization Best Practices
### Organization Principles
| Principle | Description |
|---|---|
| **Clear labeling** | Use consistent labels (Appendix A, B, C, etc.) |
| **Logical order** | Organize appendices in a logical sequence |
| **Cross-referencing** | Reference appendices from the main body |
| **Conciseness** | Include only relevant supporting material |
| **Accessibility** | Make appendices easy to find and reference |
### Cross-Referencing Examples
| Main Body Reference | Appendix Location |
|---|---|
| "See Appendix A for full nmap output." | Appendix A: Tool Output |
| "The CVSS score was calculated using the First.org calculator (see Appendix D)." | Appendix D: References |
| "Additional HTTP request/response pairs are available in Appendix E." | Appendix E: Additional Evidence |
| "The custom exploitation script is included in Appendix F." | Appendix F: Custom Scripts |
## 8. OSCP-Specific Appendix Guidance
### Required Appendices for OSCP
For the OSCP exam, the following appendices are recommended:
1. **References:** List all sources used (exploits, tools, documentation)
2. **Tools Used:** List all tools with versions and purposes
### Optional Appendices for OSCP
The following appendices are optional but can demonstrate thoroughness:
1. **Tool Output:** Raw nmap and scan output
2. **Glossary:** Technical terms and definitions
3. **Additional Evidence:** Extra screenshots or captures
### What NOT to Include in OSCP Appendices
| Don't Include | Reason |
|---|---|
| **Full exploit code from Exploit-DB** | Could be flagged as plagiarism |
| **Copied tutorial content** | Could be flagged as plagiarism |
| **Unnecessary raw data** | Clutters the report without adding value |
| **Personal notes** | Not professional or relevant |
## 9. Key Takeaways
1. **Appendices support the main report.** They provide evidence and references without cluttering the main body.
2. **Use clear labeling.** Appendix A, B, C, etc. with descriptive titles.
3. **Cross-reference from the main body.** Tell the reader where to find supporting material.
4. **Keep it concise.** Include only relevant supporting material.
5. **For OSCP:** References and tools used are required. Other appendices are optional but recommended.
6. **Avoid plagiarism.** Don't include full exploit code or copied content in appendices.
7. **Organize logically.** Group related material together and use consistent formatting.
## 10. Further Reading
- PTES Appendix Guidelines: https://www.pentest-standard.org/
- NIST SP 800-115 Appendix Section
- OWASP Reporting Guidelines