Skip to content

Authorized use only

For the official OSEP labs/exam, or systems you are written-authorized to test. Do not use against unauthorized systems.

Pre-exam checklist ​

In the 48–72 hours before the exam, actually build and verify each item below once, then tick it off. There is no time in the exam environment to compile and debug on the spot — every asset must be in a “change one IP and it runs” state.

Scenario numbers match the scenario map; the module docs live under docs/.

Shared infrastructure (do these 10 first) ​

Entry stage (scenarios 1–17) ​

Payloads and evasion (scenarios 18–24) ​

Privilege escalation and credentials (scenarios 25–27, 46) ​

Comms and tunneling (scenarios 28–35) ​

Linux (scenarios 36–40, 48) ​

Kiosk, JEA, JIT, and WinRM (scenarios 41–43, 56) ​

MSSQL and AD (scenarios 44–45, 47, 49–55) ​

Three things to do in every session ​

text
1. whoami /priv         → identity and available privileges (decides the privesc route)
2. systeminfo           → bitness, version, patches (decides payload form)
3. egress probe         → direct / proxy / DNS (decides the C2 channel)

Verify credentials the moment you get them:

text
netexec smb TARGET -u USER -p PASS -d DOMAIN        # is the credential valid, which hosts can it reach
netexec winrm TARGET -u USER -p PASS -d DOMAIN      # is WinRM the only way in

When it fails ​

  1. Change one variable at a time, then verify and log it immediately.
  2. Confirm “did the delivery succeed” first, and only then suspect “was the payload flagged”.
  3. Stage 1 and stage 2 must take the same path; a mismatch is the most common silent failure.
  4. User context works but SYSTEM does not = a proxy/authentication context problem, not a network problem.
  5. Do not assume LSASS protection can be bypassed without verifying it — switch credential source instead.

Authorized labs and the official exam environment only.