Beginner → Master Roadmap¶
The CEH hub sequenced into one ladder — from "never opened a terminal" to "operates confidently on both sides of an attack." CEH sits in the middle (Stages 1–4); Stage 5 is where you keep climbing after the cert. Work the stages in order; don't skip the foundations. (The career ladder across all the certs is the repo-wide roadmap; this page is the skill ladder inside CEH.)
🧭 See also: career/ceh-career-and-adjacent-certs.md and the repo-wide sysadmin → PAM architect roadmap.
flowchart TD
S0["Stage 0 — Foundations<br/>Linux · terminal · networking · lab"] --> S1["Stage 1 — Understand attacks<br/>the 20 modules (theory)"]
S1 --> S2["Stage 2 — Wield the tools<br/>Kali course + cheatsheets"]
S2 --> S3["Stage 3 — Do it hands-on<br/>labs · capstone · drills"]
S3 --> S4["Stage 4 — Pass the exams<br/>mocks · rapid-fire · Practical"]
S4 --> S5["Stage 5 — Beyond CEH → Mastery<br/>HTB/OSCP · specialize · red+blue"]
Each stage ends with a checkpoint: a concrete thing you can do. If you can't do it, you're not done with the stage — go back, don't push forward.
Stage 0 — Foundations (1–3 weeks · absolute beginner)¶
You can't hack what you can't navigate. Build the base first.
- Learn: Kali course chapters 00 Getting started → 01 Linux → 02 Terminal → 03 Networking.
- Do: stand up the lab (cd labs && ./scripts/setup.sh), confirm it's isolated.
- ✅ Checkpoint: from a cold terminal you can move around Linux, edit a file, read your IP, ping a lab host, and explain what a port and an IP subnet are.
Stage 1 — Understand the attacks (4–8 weeks · the CEH theory)¶
Learn what each attack is and why it works — and the control that stops it (your retention hook).
- Learn: the 20 modules in order. For each: read the guide, drill its facts.md, and read the Defender & PAM section. Track the blueprint in BLUEPRINT-COVERAGE.md.
- Cross-cutting: AI-driven hacking (v13) and the defender/PAM knowledge base.
- ✅ Checkpoint: for any attack (Kerberoasting, SQLi, XSS, ARP poisoning…) you can explain it in two sentences and name the control that defeats it.
Stage 2 — Wield the tools (overlaps Stage 1 · 4–6 weeks)¶
Turn "I know the concept" into "I can drive the tool." - Learn: Kali course chapters 04 Recon → 15 Reporting (recon, nmap, enumeration, web, Metasploit, passwords, AD, sniffing, wireless, post-ex). - Reference: keep the cheatsheets open while you work. - ✅ Checkpoint: without notes, you can nmap a host, enumerate SMB, crack a hash, get a shell with Metasploit, and upgrade it to a TTY.
Stage 3 — Do it hands-on (ongoing · where skill actually forms)¶
Reading ≠ doing. Break things in the lab.
- Do: every module's lab-walkthrough.md; then the full capstone chain (recon→Kerberoast→delegation→ADCS→DCSync); then the challenge lab (stego/pcap/crypto/hashes) and the Practical drill packs.
- Master move: attack the lab, then detect your own attack in the logs — understanding both sides is what separates operators from button-pushers.
- ✅ Checkpoint: you can run the capstone end-to-end from a foothold to Domain Admin, and find the same activity in the defender's logs.
Stage 4 — Pass the exams (final 2–4 weeks)¶
- Knowledge exam: the 12-week plan, exam strategy, and drill the 50-Q / 125-Q mocks + the 200-Q rapid-fire bank until you're ≥85%.
- Practical (CEH Master): the
practical/skills checklist, playbooks, and timed drills. - ✅ Checkpoint: ≥85% on a full-length mock, and you clear the Practical drills under time.
Stage 5 — Beyond CEH → Mastery (months–years · never really "done")¶
CEH proves breadth. Mastery is depth + reps + both-sides fluency. Pick a lane and go deep.
Structured hands-on ladder (free/cheap): - TryHackMe — beginner-friendly guided rooms → their "Jr Penetration Tester" / "Offensive Pentesting" paths. - Hack The Box — Starting Point → easy → medium boxes; HTB Academy for structured modules. - VulnHub / PortSwigger Academy / PentesterLab — downloadable targets and web-app depth. - Build your own bigger home lab (add AD forests, cloud accounts, an EDR to evade/tune).
Certification ladder: the order after CEH (CySA+, PenTest+ / PNPT / OSCP, cloud security, CISSP) and the reasoning behind it live in one place, the repo-wide sysadmin → PAM architect roadmap; each cert's hub applies the same preparation method.
Specializations to go deep in: - Active Directory / identity (your repo already leans here — identity attack paths, BloodHound, ADCS). - Web application security (PortSwigger Academy → bug bounty). - Cloud security (AWS/Azure/GCP + Kubernetes — Module 19). - OT / ICS security (critical infrastructure — the beginner→expert ot-security/ curriculum, the OT lab, IEC 62443, ATT&CK for ICS). - Malware analysis / DFIR, red teaming / evasion, or detection engineering / blue team (detection-engineering.md → SIEM/Sigma/Sysmon).
Habits of mastery: - Both sides: for every attack you learn, learn its detection and its fix (the whole repo is built this way). - Reps + notes: keep a methodology and a personal knowledge base (Kali ch.15); write up every box you do. - CTFs + community: play CTFs, read writeups, follow research; teach what you learn (fastest way to master). - Stay legal, stay current: only authorized targets; the field moves — keep reading (deep references).
Where are you? — competency self-assessment¶
Rate yourself per skill: 🟥 Novice (need a guide) · 🟨 Competent (can do with notes) · 🟩 Proficient (cold, under time) · 🟦 Expert (can teach + adapt). Level up the 🟥/🟨 rows.
| Skill | 🟥 → 🟦 |
|---|---|
| Linux / terminal / networking | navigate → script → design a lab network |
| Recon & scanning | run nmap → interpret + choose next step → evade + tune |
| Enumeration | list shares → pull the right data fast → map an unknown env |
| Web & SQLi | follow a payload → exploit by hand → chain to RCE |
| Password / hash cracking | crack MD5 → pick the right mode fast → craft rules/wordlists |
| Exploitation & privesc | use a Metasploit module → manual exploit + privesc → write your own |
| Active Directory | Kerberoast → walk a BloodHound path → full domain compromise + persistence |
| Detection / blue team | read a finding → detect an attack in logs → write Sigma rules |
| Reporting | take notes → write a finding → deliver a full report |
Mastery isn't a cert — it's the day you can attack a target, defend it, and explain both to someone else. Everything in this repo is arranged to get you there. Start at Stage 0.