Ravindra BagaleCourses & study guides मराठी Track your progress

35. Careers, Certifications and Bug Bounty

35.2 Certifications Roadmap

By Last updated:

Certifications help clear HR filters, but only when backed by skill. Prices change often and differ by region, so check the official website of each body before paying.

Level Certification (body) Good for
Foundation CompTIA Security+ Broad security basics; widely recognised for entry roles
Foundation ISC2 Certified in Cybersecurity (CC) Beginner-level concepts
Foundation Google Cybersecurity Certificate (Coursera) Beginner SOC-style foundations
Foundation AWS Certified Cloud Practitioner Cloud basics before cloud security
Hands-on entry eJPT (INE) Practical junior penetration testing
Intermediate CEH (EC-Council) Common in Indian job postings for VAPT roles; theory plus a practical option
Intermediate CompTIA CySA+ SOC and security analyst work
Intermediate PNPT (TCM Security) Practical pentest with a report
Advanced OSCP (OffSec) Highly respected hands-on penetration testing exam
Cloud AWS Certified Security – Specialty Cloud security engineer roles
Management CISSP (ISC2) Senior roles; requires paid professional security experience
Management ISO/IEC 27001 Lead Auditor / Implementer GRC and audit roles

A sensible order for learners of this book: networking and Linux skill, then Security+ or an equivalent foundation, then eJPT or CEH with lots of lab practice, then OSCP or AWS Security Specialty depending on whether you choose offensive or cloud.

Ravindra Bagale's Tip

"Which certificate guarantees a job?" – there is no such certificate. Interviewers ask, "Show me how you did this." A certificate opens the door, but proof of skills and labs gets you the job. And stay away from fake "100% placement" shortcut courses.

Practice task

Choose one target role and write your own 6-month certification and practice plan: which certificate first, which labs every week, and which chapters of this book to revise. Check the current exam objectives on the official website of your first certification.

Extended teaching notes

Why this lesson matters

Hiring managers in India look for labs, clear ethics, and the ability to explain a fix. Certifications help; unauthorised testing destroys careers.

  1. Build a home lab and keep notes.
  2. Publish write-ups only for systems you own or public labs.
  3. Learn Linux, networking, one cloud, OWASP.
  4. Practice platforms: TryHackMe, HTB, PortSwigger Academy — under their rules.

Mini case study

Suppose we are on a purple-team exercise for an Indian mid-size company (sample data). Red notes a technique from this lesson against a lab clone. Blue must show the control that stops it, the log that would have fired, and the ticket that hardens production. That is the standard this course trains you for.

Defender's worksheet (do this today)

  1. Write the lesson title, date and the exact lab target you are allowed to use.
  2. List three owned systems (VMs, apps, or cloud accounts) where this lesson applies.
  3. Run one safe check from the lesson on a lab system only. Paste the command and output.
  4. Write a two-sentence fix you would give a teammate.
  5. Name one related public advisory (CERT-In, CISA, NVD, or a vendor bulletin) with its date.

Indian workplace (sample data)

Suppose we are a junior analyst at Infosys, TCS, Wipro or a fintech SOC in Bengaluru/Pune. Turn this lesson into one checklist item with an owner, a due date and a place to store evidence (ticket + screenshot).

Global practice

Compare your notes with OWASP, CIS Benchmarks, NIST CSF/IR guidance or a cloud Well-Architected security question. Write five lines on what overlaps.

Everyday analogy

Explain the risk and the fix to a family member without jargon. If they can repeat the warning, you understand it well enough to teach juniors.

Key terms

  • Control: a safeguard (patch, config, process, detection).
  • Finding: a weakness backed by evidence.
  • Remediation: the fix plus how you verified it.
  • Scope: systems you have written permission to touch.
  • Least privilege: only the access the task needs.
  • Defence in depth: several layers so one failure does not end the story.

Common mistakes

  • Skipping written permission "just for a quick scan".
  • Practising on hostel, office or public targets without authorisation.
  • Collecting tool output without writing the fix.
  • Copying attack steps onto production to "verify". Defenders verify with versions, configs and patches.
  • Publishing screenshots that contain secrets, cookies or internal hostnames.

Recap

  • Evidence, fix, owner, date.
  • Own lab only.
  • Fix > spectacle.