1. The First Attempt: Ambition at 17

At 17, my goal was simple yet audacious: become the youngest OSCP in India. The excitement of being “the youngest” blinded me to the preparation rigor required. I registered for the course, dived into the PWK labs, and immediately faced the reality: OSCP is not just a test of technical skill; it’s a test of patience, methodology, and mental endurance.

During my first attempt, I faced three core challenges:

• Time Management: I underestimated the hours needed to methodically map and exploit lab machines. I often rushed through enumeration and missed subtle misconfigurations.
• Lab Depth: I solved about 15-18 machines out of 60+ in the labs. My exposure was insufficient for exam-level complexity.
• Exam Strategy: The 24-hour exam window requires careful pacing. I misallocated time, spending hours on one machine and failing to cover easier points on others.

“Passion is not enough; OSCP demands disciplined execution, step-by-step methodology, and relentless practice.”

2. Lessons Learned from Failure

Failing the first attempt was humbling but invaluable. I realized:

• Enumeration is everything. Without thorough reconnaissance, privilege escalation becomes guesswork.
• Every exploit must be tested in a controlled way. Blind exploitation can waste hours.
• Documentation is critical. I started maintaining a detailed lab journal, mapping IPs, services, vulnerabilities, and exploit techniques.

3. The Comeback: 9 Months of Intense Preparation

During the second attempt, I treated preparation like a full-time bootcamp:

• Dedicated 6–8 hours daily to labs, techniques, and exploit development.
• Focused on all lab machines, ensuring coverage of Linux, Windows, web apps, buffers, privilege escalations, and misconfigurations.
• Practiced time-bound simulations to mimic the 24-hour exam scenario.
• Joined forums and communities to exchange tactics, without spoiling exam confidentiality.

4. The Exam: 24 Hours of Mental Endurance

The OSCP exam consists of 5 machines and sometimes a buffer overflow challenge, all to be completed in 24 hours. Each machine is worth points depending on difficulty, and a minimum score of 70/100 is needed to pass.

My approach in the second attempt:

• Hour 1-6: Enumeration and scanning, mapping every service meticulously.
• Hour 6-15: Exploit and privilege escalation attempts on medium-level machines.
• Hour 15-22: High-difficulty machines and buffer overflow, keeping notes for report generation.
• Hour 22-24: Final review, note verification, and exam report preparation.

“OSCP is a marathon, not a sprint. Methodical execution under pressure determines success.”

5. Report Writing: The Unsung Challenge

Many underestimate the report component of OSCP. A perfect exam score is meaningless without a thorough, clear, and structured report. The report is where you translate raw exploitation into reproducible steps, demonstrating methodology and professionalism.

My approach to OSCP report writing:

• Step-by-Step Exploitation: Each machine documented with IP, enumeration steps, tools used, and exact commands.
• Screenshots: Screenshots of shells, privilege escalations, and final flags are mandatory to validate every claim.
• Time Management: I reserved final 2 hours to polish the report, verify notes, and ensure clarity.
• Professional Formatting: Clear headings, numbered steps, screenshots, and tool references. The goal: anyone reading the report should reproduce your steps exactly.

Without proper report writing, even technically perfect exploits may not earn full points. During my second attempt, meticulous report preparation ensured I achieved the passing threshold without losing marks unnecessarily.

6. Benefits of OSCP

• Mastery of penetration testing fundamentals, hands-on offensive security skills.
• Recognition as a credible, certified cybersecurity professional.
• Improved problem-solving, patience, and mental resilience under stress.
• Open doors to cybersecurity roles in top companies, ethical hacking, bug bounty programs, and advanced security research.

7. Reflections and Takeaways

Cracking OSCP at 18 was not just about a certification—it was about growth. Failure taught me humility, preparation taught me discipline, and success validated relentless effort. If you aim for OSCP:

• Focus on methodology, not shortcuts.
• Document everything: notes, exploits, successes, failures.
• Practice patience; the exam is as much mental endurance as technical skill.
• Embrace failure as a learning tool. My first attempt was the stepping stone to my OSCP success.
• Write your report like your exam depends on it—because it does.

References & Resources

• Offensive Security PWK / OSCP Course
• Hack The Box Labs
• VulnHub Machines for Practice
• Penetration Testing Tutorials