Growing Talent From Within: Two OSCP+ Journeys at OsmSec

#oscp#oscp+#team

Great cybersecurity teams aren't built overnight. They're built through curiosity, continuous learning, real-world challenges, and opportunities to grow.

Behind every strong cybersecurity team are people who keep questioning, experimenting, learning, and pushing their limits. At OsmSec, we're proud to create an environment where that curiosity is encouraged and potential is given the opportunity to grow into expertise.

Our commitment to developing talent goes beyond everyday project work. Last year, through OsmSec, our team members Nishanth and Saketh had the opportunity to contribute to OffSec's Exploit-DB project. This gave them an opportunity to engage with vulnerability research and contribute to the wider cybersecurity community.

Their dedication to learning and improving also led them to an important milestone: achieving the OSCP+ certification.

OSCP+ is not simply about passing an examination. It demands practical skills, problem-solving, persistence, and the ability to think like an attacker. Every attempt brings its own challenges, and every success has a story behind it.

I sat down with Nishanth and Saketh for an interactive conversation about their journeys, preparation strategies, setbacks, lessons, and what comes next.

Here's a closer look at the people and their determination behind these achievements.

What sparked your interest in OSCP+, and what did that first step into the journey look like for you?

Nishanth:

I've been curious about hacking since childhood. Later, I discovered that cybersecurity was an actual industry with certifications, standards, and professional opportunities.

Back then, OSCP was everywhere. People who held it were incredibly proud of it. I remember OffSec giving out the OSCP card with its distinctive silhouette, and I admired it a lot.

That was the day I decided I wanted to earn one!

For me, there isn't really a single first step. Every day brings something new: a task, an attack, a technique, or something different to explore. That's what keeps me excited about cybersecurity, hacking, and exploitation.

Saketh:

I became interested in cybersecurity in 2024, initially driven by the idea of becoming an ethical hacker.

I started with YouTube tutorials, CTFs, and Hack The Box machines. Eventually, I was introduced to the team at OsmSec, joined as a Content Engineer, and began developing my practical skills.

OSCP naturally became the next milestone in my journey.

What went wrong in the first attempt?

Nishanth:

My biggest challenge was the examination environment itself.

I had never experienced a 24-hour proctored examination, where someone is watching you even though you cannot see them.

The time constraint, my mental health, and a terrible sleep schedule before the exam all affected me.

OSCP was a dream I had wanted to achieve for a long time, so I put too much pressure on myself. As the clock kept ticking throughout those 24 hours, the pressure continued building.

I had a clear picture of the attack path and knew what I needed to do, but I couldn't execute everything successfully.

Saketh:

My biggest weakness was Active Directory.

I had learned individual commands but hadn't developed a proper enumeration and exploitation methodology.

I also underestimated API-based web applications, struggled with Windows privilege escalation, and didn't manage my breaks properly.

I finished my first attempt with 40 points.

What did you do differently the second time around, and which changes made the biggest difference?

Nishanth:

The second time, I was confident that I could achieve it.

I made sure I got enough rest before the examination. I already knew what the 24-hour experience would look like, so I prepared myself mentally.

Instead of treating the exam as a huge burden, I approached it like a game. I kept things simple and tackled each challenge step by step.

I also developed my own strategy.

There's a quote I strongly believe in: "Nosce Te Ipsum"  Know Thyself.

Trust yourself, understand your capabilities, and recognise your limits.

Saketh:

I focused specifically on the areas where I had struggled.

I followed Hexdump's Active Directory course, built a local AD lab, and practised understanding attack paths.

I also completed Tib3rius's Windows Privilege Escalation course and PortSwigger's API Testing learning path.

By my second attempt, I had completed over 120 practice machines.

The biggest difference was moving away from blindly running commands and towards understanding the reasoning behind every enumeration and exploitation step.

Which technical skills grew the most during your preparation, and what's your go-to methodology now when you approach a new target?

Nishanth:

I wouldn't say I followed a strict preparation plan. I went through the course content and videos and spent time working on OSCP style machines in the Challenge Labs.

My regular role also involves penetration testing, which gave me practical experience and helped me continue practising.

My approach depends on the type of target I'm assessing. But the first and most important step is always reconnaissance and enumeration.

Everything starts there. Once you understand the information gathered during enumeration, you can develop your own methodology based on the target.

Saketh:

My biggest improvements were in Active Directory enumeration and exploitation, Windows privilege escalation, and API-based web application testing.

My approach now is to enumerate methodically, understand the attack surface, identify relationships and potential attack paths, and validate hypotheses rather than blindly following command checklists.

How did you plan your 24-hour exam, from the order you tackled machines to how you managed sleep and breaks, and what worked best for you?

Nishanth:

I went with the flow rather than following a fixed order.

I took plenty of breaks and tried not to put unnecessary pressure on myself by constantly thinking about being in an examination.

Whenever I captured a flag, I took a break, came back, and moved on to the next challenge.

I also took naps whenever I felt sleepy.

Keeping myself relaxed and focused helped me throughout the examination.

Saketh:

I started with the Active Directory chain while simultaneously running preliminary Nmap scans against all three standalone machines.

I completed the AD chain in approximately four hours and then tackled the standalone machines in stages, taking planned two-hour breaks between sessions.

Once I reached 70 points, I continued towards 80, secured my evidence, and thoroughly reviewed my notes.

I wrapped up after approximately 22 hours.

Taking proper breaks and trusting my preparation made a significant difference.

What advice would you give a teammate just beginning their own OSCP+ journey?

Nishanth:

Start with the basics and build your knowledge step by step.

Work on challenges, CTFs, and machines. Platforms like TryHackMe, PortSwigger, and especially Hack The Box are great places to begin.

Try building your own lab. Develop vulnerable websites and machines, then practise exploiting them. Understanding both the attacker's and defender's perspectives will give you a much clearer picture.

Also, learn to write your own exploit code and PoCs for vulnerabilities. Don't become someone who simply runs publicly available scripts without understanding them.

OSCP teaches you that public exploits don't always work in every environment. Sometimes, you need to develop your own approach and adapt to the situation.

Saketh:

Don't treat OSCP as a race to collect commands or complete machines.

Focus on understanding why something works, develop a dependable methodology, maintain good notes, and practise consistently.

Complete PEN-200 and spend substantial time on Proving Grounds.

Most importantly, identify your weaknesses early and work on them deliberately.

What are your top three must-have tools, and which resource would you recommend?

Nishanth:

I don't believe there's a fixed set of must-have tools for every penetration test. The tools we choose depend on the attack scenario and the environment.

However, Kali Linux is my go-to operating system. It comes with most of the tools needed for penetration testing, and additional tools can easily be installed when required.

Saketh:

My three must-have tools are:

  1. Nmap: Essential for systematic network and service enumeration.

  2. Kali Linux: My primary environment for enumeration and exploitation.

  3. Notion: For maintaining structured, searchable notes, commands, and learnings from every machine.

As an additional resource, I'd strongly recommend S1REN's blog series and her Zero to Navy Seal of Crackin' guide.

What resources would you recommend to someone preparing for OSCP+?

Nishanth:

Here are some of the resources I recommend:

  • Hack The Box

  • HackTricks

  • IRed Team

  • LOLBins, LOLBAS, and GTFOBins

  • Exploit-DB

  • GitHub repositories such as PayloadsAllTheThings

  • PortSwigger Web Security Academy

  • YouTube

There are many more resources available, but these are some of the ones I find useful.

Saketh:

My recommendations would be:

  • OffSec PEN-200: The foundation for OSCP preparation.

  • OffSec Proving Grounds Practice: Essential hands-on practice.

  • Lainkusanagi and TJNull's OSCP machine lists: Useful for selecting practice machines.

  • S1REN's blogs and YouTube livestream playlist: Excellent for learning methodology and practical techniques.

  • Hexdump's Active Directory Exploitation course: Particularly useful for Active Directory.

  • Tib3rius's Windows Privilege Escalation course.

  • PortSwigger's API Testing learning path.

If you had to capture this whole experience in three words, what would they be?

Nishanth:

Exploit. Pivot. Evade.

Saketh:

Humble. Conscious. Persistent.

What was the first thing you did after that pass email landed?

Nishanth:

When I saw the pass email landed in my inbox, I couldn't contain my happiness.

I had finally done it! 😄

A dream I had been working towards for years was suddenly right in front of my eyes. I was filled with joy and an overwhelming sense of relief.

All the hard work, late nights, and preparation had finally paid off.

I immediately started sharing the news with my loved ones. I remembered where it all began and realised how far I had come.

Saketh:

I stared at the result on my screen, and honestly, I broke down in tears. 🥹

After everything that had happened during my first attempt and all the preparation that followed, it was an incredibly overwhelming moment.

What's the next milestone you're eyeing?

Nishanth:

I'm looking forward to exploring multiple areas, including AI security, product security, threat research, and, of course, red teaming.

But everything is uncertain right now, so let's just go with the flow!

Saketh:

I want to continue deepening my practical penetration testing skills, take on more challenging engagements, and expand my expertise across different areas of cybersecurity.

What Their Journeys Mean for You

Nishanth and Saketh's stories aren't just about passing an exam. They reflect how we work at OsmSec: we don't stop at running tools, we build methodologies, we learn from setbacks, and we understand why an attack path works, not just that it does.

That same discipline is what we bring to every client engagement. When you work with OsmSec, you're not hiring a team that runs automated scans. You're hiring people who approaches a target methodically, curiously, and with a commitment to understanding the real risk, not just the surface vulnerability.

If you want a penetration testing partner whose team is built on the kind of growth you've just read about, we'd love to talk.

Share