← All posts
OSCP+ certification badge

How I Passed the OSCP+ with a 100/100 on My First Attempt: Honest Tips

2,619 words11 min read

Also on Medium ↗

On this page
  1. The Short Version
  2. What the Exam Looks Like
  3. Is This Realistic for You?
  4. How I Prepared
  5. The Course Modules
  6. The Challenge Labs
  7. HackTheBox
  8. What I’d Change
  9. Resources & Cheat Sheets
  10. Skills Nobody Talks About
  11. Exam Day
  12. The Report
  13. If I Started Over Tomorrow
  14. Final Thoughts
  15. Want Some Help With Your Prep?

I landed my first foothold 18 minutes into the exam, and for a brief moment I thought this was going to be easy. It was not. A few hours later I was staring at the same login page for what felt like the hundredth time, quietly wondering what I had missed.

I ended up passing the OSCP+ on my first attempt with 100/100 points (rooting all machines and extracting their flags) on 11/9/26. I’m sharing how it went, my mistakes, and some tips in case someone is where I was a few months ago. This post covers what the exam looks like, how I prepared, how my exam day went, and the tips I’d give to anyone planning to take it.

The Short Version

If you only have a minute, here’s some quick notes:

  • Prep time: About 130 hours over two and a half months, roughly 13 hours a week, while working full time (tracked in Toggl)
  • Background: One year as a cybersecurity analyst, plus eJPT and eCPPT (more on that below)
  • What helped most: The PEN-200 challenge labs and HTB machines, plus learning to slow down and make sense of the information I was given
  • What I’d change: More time in the challenge labs and on HTB, and fewer tutorials
  • Biggest trap: Rabbit holes. I lost about 7 hours to a couple of them on exam day
  • Want to skip some modules? Jump to the modules you can skip

What the Exam Looks Like

Note: Offsec is planning to change to a scaled scoring system starting December 1, 2026, with a new scoring scale between 100 and 500. The passing score is 400 out of 500. You can still get raw points from rooting machines, but those points are scaled/adjusted based on the difficulty of the exam set you receive. The format below is what I took, so double-check OffSec’s current exam guide.

You get 23 hours and 45 minutes of proctored hacking time, then another 24 hours afterward to turn in your report. The exam is out of 100 points, and you need 70 to pass. There are no bonus points to bail you out. Sixty of the points come from three standalone machines worth 20 each, split evenly between getting a foothold and escalating privileges. The other 40 come from an Active Directory set of three machines, which you start with an assumed breach and a set of credentials. Metasploit is only allowed on one target, but it would be better to avoid using it entirely because you don’t need it to pass. Treat it as a get-out-of-jail-free card if you’re completely stuck, but don’t over-rely on it.

Is This Realistic for You?

Why did I take this exam? Because, unfortunately, it’s the most recognized certification in the industry. No matter what other pentesting certs you might get, this is undoubtedly a big name that can get your foot in the door. I also wanted an honest check on whether my pentesting knowledge was as sharp as I hoped, and it’s a stepping stone. I’d love to pick up OSEP, OSAI, and maybe CRTP down the road, and this felt like the right place to start.

Everyone has their own background, but here is mine: I’ve been working as a cybersecurity analyst for about a year, and I hold a B.S. in Computer and Information Science and an AA in Cybersecurity. I’m also certified in eJPT and eCPPT (odd, yes, since they’re all pentesting certifications). I wasn’t starting from zero, but I wasn’t a seasoned pentester either, and I think that’s worth knowing before you compare your timeline to mine.

So is it realistic? With that background, about 130 hours over two and a half months was enough for me. If you have less hands-on experience, give yourself more time than I did, and spend it working through TryHackMe or HackTheBox trainings/lessons before you start the OSCP material.

How I Prepared

I decided to take the accelerated path and purchase the 3 month plan because I already had prior pentesting knowledge. So this is just what worked for me, and it should give you a general idea of how much time could be invested for this exam.

Altogether I put in around 130 hours. Here’s how it generally broke down:

  • ~60 hours: Working through the course modules
  • ~15 hours: HTB machines
  • ~25 hours: Challenge labs, where I also practiced by writing reports for some of them
  • ~30 hours: Building my notes, cheat sheets, and scripts, which I’m glad I didn’t skip

The Course Modules

I finished all of the PEN-200 modules except vulnerability scanning, client-side attacks, and AWS. From there I moved on to the challenge labs, which is where a lot of the hands-on work comes from that readily equips you for the OSCP.

What You Can Skip (My Opinion)

If you’re tight on time, there are a few modules you can skip without hurting your chances of passing. They’re still worth learning on your own later, but none of them are needed to pass, in my opinion:

  • Vulnerability scanning
  • Phishing basics
  • Antivirus evasion
  • AWS cloud and the extra-mile material
  • The Metasploit framework: Optional if you already know it and don’t plan to use it
  • Port redirection and SSH tunneling: Understanding the concept is worth it for real-world work, but for this exam, knowing how to pivot with ligolo-ng against the AD network is all you need

The Challenge Labs

Challenge labs are multi-machine environments designed to simulate real-world pentesting engagements and prepare you for the OSCP exam. Note: you do NOT need to complete all the challenge labs to be prepared for the exam. I personally didn’t complete Skylark, Relia, Feast, and Laser:

My progress before I took the exam

For the ones I did finish, here are some notes on them:

Challenge lab Should I complete before OSCP? Notes
Secura Yes Builds muscle memory for pivoting, internal recon, and AD compromise chains
MedTech Yes Easy-rated, with lots of pivoting and enumerating. Most flags came from reusing credentials across hosts
OSCP A, B, C Yes An exact replica of the exam’s scoring, AD sets, and standalone machines. Practice writing reports using Sysreptor or any reporting tool for an easy copy/paste process
Zeus / Poseidon Maybe All Windows and clear about where to pivot, so it was perfect AD practice and a good place to get used to taking notes and screenshots. But I wouldn’t say this is needed unless you want more practice against Windows/AD environments

MedTech deserves a little extra credit because it taught me the most. When you hit a dead end, you have to circle back to what you’ve already found, whether that’s credentials, ports and services, or corners you never fully explored. It also taught me a lesson I needed: log everything you’ve already tried, or you’ll end up running the same exploit twice and wondering why it still doesn’t work. It made me a lot more comfortable with Windows enumeration and exploitation tools such as nxc, psexec, impacket, and evil-winrm.

My overall progress before I took the exam

Stuck in a Challenge Lab?

If you’ve been staring at the same machine for hours, I offer a 1:1 Cert Roadmap Session that covers the challenge labs I’ve completed: Secura, MedTech, OSCP A, B, and C, Zeus, and Poseidon. We’ll go through what you’ve found so far and work out your next step together. I’ll give you nudges and methodology, never full solutions or flags, so you still get the “aha” moment yourself (which is the whole point of the labs).

HackTheBox

These are the machines I’ve pwned while studying for the OSCP:

  • Active
  • Administrator
  • Admirer
  • Bashed
  • Bastard
  • Beep
  • Bounty
  • Builder
  • Cronos
  • Shocker
  • Forest
  • Magic

As you can maybe tell, I was following TJ Null’s OSCP List in alphabetical order in the beginning lol.

I’d also recommend watching IppSec here and there. I don’t mean following along step by step, but watching how he approaches a box helped me understand the pentesting workflow: what to check first, how to decide where to dig, and when to back out of a dead end.

What I’d Change

If I could redo my prep, I’d spend more time in the challenge labs and on HTB machines. I’d also try harder to avoid turning to tutorials so easily. If you do get stuck and need one, read just enough to get unstuck, then close it and keep going on your own. That’s where the learning actually happens.

Resources & Cheat Sheets

For me, PEN-200 and its challenge labs were easily the most valuable thing, followed by the TJ Null list and the HTB and TryHackMe machines for extra practice. I don’t have a roadmap of what courses to take that would align closely with OSCP (there are other posts that talk about that), but as a tip, just search up whatever techniques you think you need more experience in. Whether it’s pivoting, networking, AD enumeration/exploitation, Linux exploitation, or Windows exploitation… you get the point. I never touched Proving Grounds Practice, so I can’t say anything about it. For quick lookups, HackTricks and GTFOBins/LOLBAS are good references. HackTricks especially is great when you run into a service you’ve never seen before and need to learn it fast.

These are the cheat sheets I leaned on during prep and the exam:

Skills Nobody Talks About

Your technical skills can get you far, but it was discipline and the Try Harder mindset that got me through. Here are a few non-technical skills to polish:

  • Time management: Twenty-four hours sounds like forever until you realize half of it went to something that wasn’t worth it. It helps to check in on yourself regularly and ask whether what you’re doing is actually moving you toward points.
  • Knowing when to move on: Rabbit holes will quietly eat your whole attempt. If you’ve been circling the same thing for too long, write down what you tried, step away from that machine, and come back with fresh eyes. It’s not giving up, it’s saving yourself.
  • Note-taking: Your report is only as good as your notes. If you don’t write down a command or a finding when it happens, you’ll be hunting for it at hour 20 when you’re tired and the report is due.
  • Research skills: Finding the right exploit or technique quickly saves a lot of time. Knowing how to search, what to search, and when a result is worth trying comes from practice.
  • Consistency: Studying a little bit regularly kept everything fresh in my head, and it worked much better than cramming everything.
  • Stress management, sleep, and rest: A full day of nonstop hacking will give you a headache. Go touch some grass, eat your favorite food, and talk to your friends and family. Plan your sleep and breaks ahead of time instead of deciding in the moment, when you’re already banging your head on a box.

Exam Day

Here’s how my exam day actually went. The first foothold came in 18 minutes. The standalones took about 12 hours in total. Then, somewhere between the standalones and the AD set, I lost a solid 7 hours to a couple of rabbit holes, which still stings a little to write down. The AD set itself took around 4. By the 23-hour mark, I had user and admin access on every system.

The biggest lesson was that the information you’re handed is there for a reason. Every service, file, credential, and username is placed deliberately, so the way in is usually simpler than it feels. Understanding why things are placed where they are keeps you out of rabbit holes, and on both Windows and Linux it really pays to know your file structures, processes, and common vulnerabilities well enough to tell what belongs and what looks out of place. I got into the habit of writing down what I knew and what I didn’t, then stepping back to look at the whole system instead of spraying passwords at everything in sight, which helped save some time.

A few things to carry into your own attempt:

  • Save the AD set for later. I had heard that it’s relatively gentle compared to the standalones, and that matched my experience. I tackled it in the middle or toward the end, after the standalones, or whenever I was waiting on a scan to finish.
  • Label your machines clearly in your notes. So you don’t mix up which is which during the actual engagement.
  • Take more breaks than you think you need. Stepping away somehow made my head clearer. When you’ve been digging and pivoting nonstop, it’s hard to see the thing right in front of you.
  • Don’t rush. Twenty-four hours is enough time to find a way into every system.

It also helps to set a couple of rules for yourself before the exam, while your head is still clear. For example, set a time slot for when to take breaks or when to move on to the next machine (e.g., “90 minutes without progress and I pivot to another box”). Another is a rest schedule that you treat as non-negotiable, planned around your exam start time.

The Report

I used SysReptor as my template, and I spent about 6 hours writing it. About 90% of that was done during the exam window itself, so I only had a little left to finish afterwards.

What made it manageable was taking ugly notes on Obsidian as I went and turning them into a cleaner report afterward. I also grabbed screenshots along the way with Greenshot, since it’s quick to copy and paste them into place. If you only take one tip from this section, practice writing a report before the real exam, so the process isn’t new when you’re tired.

If I Started Over Tomorrow

  • Spend more time in the challenge labs and on HTB machines. That’s where the hands-on learning happens.
  • Resist the tutorial. Read just enough to get unstuck, then go back to working it on your own.
  • Set your rules before exam day. Decide your time-box and your rest schedule while your head is still clear, and practice writing a report beforehand so none of it is new when you’re tired.

Final Thoughts

These are my thoughts, opinions, and tips that worked for me. I’m not saying this is the one-and-done method of passing the OSCP exam, but I hope it shows you what it’s like, how I prepared, and what I would’ve told my past self if I were to start all over again. Everyone has their own journey, and this is just a testament to mine. I hope this was a good resource for anyone trying to break into red teaming/pentesting or who just wants to learn the nitty-gritty technical concepts that lie in a hacker’s perspective.

Whoever you are, I wish you the best in your journey!

Want Some Help With Your Prep?

If you’d like someone in your corner while you study, I offer 1:1 mentorship for the OSCP+, eJPT, and eCPPT:

  • Cert Roadmap Session: one hour to build a week-by-week study plan around your background and exam date, plus help with any challenge lab you’re stuck on.
  • Monthly mentorship: two calls a month and questions by chat in between, until you pass.

Same rule as above: methodology and nudges, never exam content or lab solutions.

Stay resistant. Josh·jeΩm.dev

Comments

    Comments show up once I've read them. No links, please. Be kind.

    What should I write about next?

    Stuck on something from your OSCP prep? Ask me and I might write about it.

    Get new posts by email

    One email when I publish something new. No spam, unsubscribe anytime.

    Latest: Home Lab Ep. 1: Building a Self-Hosted LLM with Ollama and LibreChat