OSCP study materials
OSCP study resources

OSCP study plan

OSCP · Give each week a clear focus.

8 weeks · About 8 hours per week

Week 1

Active Directory Attacks and Post-Exploitation & Information Gathering and Enumeration

  • Build a small Active Directory lab (domain controller plus two members) and enumerate it end to end using TCP/UDP scans, SMB, LDAP and Kerberos queries

  • Enumerate domain users, groups, computers, SPNs and delegation flags using at least five distinct techniques

  • Convert raw enumeration output into a written attack-path diagram linking misconfigurations to escalation steps

  • Record every command and its output into a reusable evidence file that follows a consistent template

Your checkpoint

A personal enumeration playbook containing at least 25 verified commands plus a one-page attack-path diagram for a five-host AD lab you built yourself

Week 2

Active Directory Attacks and Post-Exploitation & Exploitation and Password Attacks

  • Execute Kerberoasting, AS-REP roasting, password spraying and credential dumping against the lab domain

  • Crack every captured hash type with two wordlists and one rule set, then tabulate crack rates and time-to-crack

  • Move laterally with harvested credentials over at least two distinct protocols and confirm privilege level on each target

  • Document the artifacts each credential attack leaves behind so the technique can be defended as well as performed

Your checkpoint

A credential-attack lab report covering at least four hash or secret types, measured crack times, and two successful lateral-movement chains with proof of access

Week 3

Linux Privilege Escalation

  • Enumerate a Linux target manually (users, sudo rights, SUID/SGID binaries, cron jobs, capabilities, kernel level, writable paths) before reaching for any automation

  • Exploit at least three distinct Linux privilege-escalation misconfigurations across separate hosts

  • Write and run your own lightweight privilege-escalation check script and refine it after each new host

  • Capture each escalation as a reproducible step list another tester could follow blind

Your checkpoint

Root on four lab Linux hosts, each with a short writeup naming the exact escalation vector, the command sequence used, and a one-line remediation

Week 4

Windows Privilege Escalation

  • Enumerate Windows hosts for service permissions, unquoted service paths, weak ACLs, auto-logon secrets and missing patches

  • Abuse at least one token or impersonation privilege to move from a low-privileged shell to SYSTEM or administrator

  • Extract stored credentials from registry, memory and unattended-install files on the hosts you compromise

  • Compare manual enumeration against automated tooling and note where each one missed findings

Your checkpoint

Administrator or SYSTEM access on four lab Windows hosts plus a matrix of ten privilege-escalation techniques marked tested with evidence or not applicable with a reason

Week 5

Web Application Attacks & Vulnerability Scanning and Analysis

  • Test three deliberately vulnerable web applications by hand for injection, file upload, path traversal, local and remote file inclusion, server-side request forgery and insecure deserialization

  • Run an unauthenticated scan and an authenticated scan of the same target and reconcile the differences in findings

  • Chain a web finding into a shell and then into a local privilege escalation on the same host

  • Write each finding with reproduction steps, impact and a concrete fix recommendation

Your checkpoint

A completed web-attack worksheet covering three targets, each with a reproduced exploit chain and a written finding entry

Week 6

Client-Side Attacks & Exploitation and Password Attacks

  • Build two client-side delivery chains (for example a document-based payload and a shortcut or HTML-smuggling lure) and confirm a callback from a victim VM

  • Stand up and tear down listeners reliably, verifying that payload encoding and staged versus stageless choices match the listener

  • Take one publicly available proof-of-concept exploit, adapt it to your target, and explain in writing what you changed and why

  • Trace how a client-side compromise becomes a foothold suitable for the pivoting work in week seven

Your checkpoint

Two working client-side chains with callback evidence plus one modified public exploit accompanied by a diff-style explanation of your changes

Week 7

Port Redirection and Pivoting

  • Set up local, remote and dynamic SSH port forwarding and confirm each path with a service check from the far side

  • Route traffic through a compromised host using a SOCKS proxy and at least one tunnelling tool, then reach a host that has no direct route from your attack machine

  • Configure host-level port forwarding on a Windows pivot and a Linux pivot to compare the two approaches

  • Draw the network from the attacker's perspective, marking every hop and the tunnel type used at each one

Your checkpoint

A network diagram plus a table of six forwarding or tunnelling techniques you verified, each with the exact command and the proof of a third-tier host reachable through the chain

Week 8

Active Directory Attacks and Post-Exploitation & Information Gathering and Enumeration & Linux Privilege Escalation & Windows Privilege Escalation

  • Complete a timed full-scope practice run against the lab, starting from a single exposed host and finishing at domain administrator

  • Re-test the three weakest domains from weeks one through seven and close every gap you can name

  • Write up every objective in report format with screenshot evidence, reproduction steps and remediation advice

  • Produce a personal gap list with a remediation plan for the month after the plan ends

Your checkpoint

A full-length practice-exam report with evidence for every objective attempted, a scored self-assessment, and a dated gap-closing plan

Milestones

Week 2: You can go from unauthenticated to domain user credentials in the lab without notes, and you can name the defensive artifact each credential technique leaves behind

Week 4: You hold local administrator or root on at least eight lab hosts across Linux and Windows, with a written escalation narrative for each

Week 6: You can gain a foothold through a web application and through a client-side lure, and adapt a public exploit rather than running it unmodified

Week 8: You complete a timed end-to-end lab run and submit a report that another tester could follow to reproduce every finding from scratch