The Offensive Security Certified Professional (OSCP) is widely regarded as the most respected entry-level penetration testing certification. Unlike multiple-choice certifications, OSCP requires passing a 24-hour hands-on exam where you must compromise machines and submit proof of access. This guide covers what to study, how to prepare, lab strategy, and what actually works on exam day — based on collective community experience.
What is OSCP?
OSCP is offered by Offensive Security as part of the PEN-200 (PWK) course. The exam consists of three standalone machines (10 points each) and an Active Directory set (40 points, requires domain admin), totaling 100 points. You need 70 points to pass. A 10-point bonus is available for a complete lab report documenting 10 machines and all exercises. The exam is proctored via webcam and screen share.
Prerequisites and Timeline
Recommended before starting PEN-200:
- Networking fundamentals (TCP/IP, subnetting, protocols)
- Linux command line proficiency
- Basic scripting (Python or Bash)
- TryHackMe: Complete path (Jr Penetration Tester + Pre-Security)
- Hack The Box: 10-20 easy/medium machines (retired, with writeups)
Typical prep timelines:
- Complete beginner: 12-18 months
- Some IT background: 6-12 months
- Already working in security: 3-6 months
LabTime recommendation: 90 days minimum, 365 for thorough preparationCourse and Lab Structure (PEN-200)
PEN-200 modules cover:
- Information gathering and enumeration
- Vulnerability scanning and exploitation
- Web application attacks
- Active Directory attacks
- File transfers and antivirus evasion
- Privilege escalation (Windows and Linux)
- Port forwarding and tunneling
- Metasploit Framework (limited use on exam)
- Buffer overflows (Windows/Linux - removed from recent exam)
- Password attacks
- Client-side attacks
Lab machines: ~70 unique machines across 3 lab networks
Challenge labs: 6 simulated OSCP exam scenarios (most valuable exam prep)
Prove It Labs: Specific exercises to reinforce course conceptsRecommended Study Resources
Primary:
- PEN-200 course materials and labs (official)
- Hack The Box OSCP-like machines (TjNull's list)
github.com/tjnull/OSCP-Stuff
Supplementary:
- TCM Security Practical Ethical Hacking (PEH) course
- IppSec YouTube channel (HTB machine walkthroughs)
- 0xdf hacks stuff blog
- S1ren YouTube (OSCP tips)
Linux PrivEsc:
- linpeas.sh (automated enumeration)
- GTFOBins (gtfobins.github.io)
- TryHackMe Linux PrivEsc room
Windows PrivEsc:
- winpeas.exe
- lolbas-project.github.io
- TCM Windows Privilege Escalation course
AD-specific:
- TCM Practical AD course
- HTB Pro Labs: Offshore, RastaLabsLab Strategy: What to Actually Do
Week 1-4: Foundation
- Read course PDF cover to cover
- Complete all exercises for the lab report bonus
- Compromise the first few labs with hints
Week 5-10: Independent Lab Machines
- Attempt each machine with 2 hours of genuine effort first
- Document everything in a note-taking tool (CherryTree/Obsidian)
- Use community hints only after 2+ hours stuck
- Focus on methodology, not memorizing exploits
Week 11+: Challenge Labs
- Complete all 6 OSCP challenge lab sets
- These are the best exam simulation
- Review every machine you struggled with
Final 2 Weeks:
- Revisit weak areas
- Practice note-taking speed
- Do a full mock exam (simulate 24 hours: compromise machines, write report)
- Rest 2 days before actual examExam Methodology
Time allocation (24 hours):
Hour 0-1: Nmap all targets, review scope, plan approach
Hour 1-10: Attack standalone machines (aim for 2 of 3)
Hour 10-20: Attack AD set (most points, most complex)
Hour 20-24: Mop up remaining standalone, document
Report: Due 24 hours AFTER exam ends
Enumeration checklist per machine:
1. nmap -sC -sV -p- -T4 --open TARGET
2. Web: gobuster/feroxbuster + nikto + manual review
3. SMB: enum4linux-ng, smbmap, smbclient
4. FTP: anonymous login, version CVE lookup
5. SSH: version CVE lookup
6. Check all services for version-specific CVEs
7. Run linpeas/winpeas after footholdNotes and Documentation
Documentation on exam day is critical. You cannot pass without proof of compromise:
Required screenshots for each machine:
- ipconfig/ifconfig output showing machine IP
- hostname output
- whoami showing root/SYSTEM/Administrator
- Proof file: cat /root/proof.txt or type C:\Users\Administrator\Desktop\proof.txt
- Local proof: cat /home/user/local.txt (for partial credit)
Capture for every command:
# Example: screenshot ipconfig + hostname + whoami + proof in one command
echo '---' && hostname && whoami && ipconfig && type C:\Users\Administrator\Desktop\proof.txt
Keep timestamped notes with all commands run and their outputExam Day Tips
Do:
- Read the exam guide 2x before exam day
- Prepare your Kali VM and tools in advance
- Take breaks every 90 minutes (walk, eat)
- Start with machine you feel most confident about
- If stuck 1+ hour, move to another machine, come back later
- Save your VPN config and backup plan
- Submit proof.txt contents via exam control panel immediately
Don't:
- Use Metasploit exploit/multi/handler on more than 1 machine
- Forget local.txt (10 points on its own)
- Underestimate the report (write it night of, not morning after)
- Skip enumeration to try exploits first
- Panic — the exam is designed to be completableAfter OSCP: Where to Go Next
Certifications:
- OSEP (PEN-300) - Evasion and advanced AD attacks
- OSED (EXP-301) - Windows exploit development
- CRTO (Certified Red Team Operator) - Cobalt Strike
- CRTE (Certified Red Team Expert) - Advanced AD
- eWPTX (web app advanced)
Practice platforms:
- Hack The Box Pro Labs (Offshore, Cybernetics)
- VulnHub (free offline VMs)
- PentesterLab (web-focused)Conclusion
OSCP success comes from methodology, not memorization. Build a systematic enumeration process, practice on HTB machines from TjNull’s list, complete all 6 OSCP challenge labs, and document everything. The exam is hard but fair — every machine is rooted through a logical chain you can find with thorough enumeration. Plan your time, take breaks, capture screenshots continuously, and start the report immediately after the exam. The ‘Try Harder’ philosophy means exhaust your own ideas before looking for hints, but also know when a fresh perspective on a different machine is more productive.
Related Articles
- How to Write a Professional Penetration Testing Report
- Nmap: Advanced Scanning Techniques, NSE Scripts & Firewall Evasion
- Linux Privilege Escalation: SUID, Sudo, Cron & Writable Files
- Metasploit Framework: Exploitation, Post-Exploitation & Meterpreter
- Burp Suite Tutorial: Intercepting, Fuzzing & Exploiting Web Apps