About an hour a day on weekdays (30 minutes reading + 30 minutes hands-on) and two hours on weekends. Miss a day? Don't double up; just continue.
Weeks 1–3: the shell and the network
| Night reading | Hands-on |
|---|---|
| Chapters 0, 1, 2 | OverTheWire Bandit: aim for the first third in week 1, the next third in week 2 |
| Chapter 3 | Wireshark on your own traffic; nmap -sV 127.0.0.1 on your Mac; curl -I your own sites |
| Re-read your Bandit notes | Finish Bandit |
Weekend: set up the Hacking Lab (Docker compose) and open Juice Shop.
Weeks 4–6: method and the web
| Night reading | Hands-on |
|---|---|
| Chapter 4 | TryHackMe Pre Security, then Cyber Security 101 |
| Chapter 5 | PortSwigger: Path traversal, Access control, Authentication (Apprentice) |
| Chapter 6, sections 1–2 | PortSwigger: SQL injection, Command injection (Apprentice); DVWA at low then medium |
Weekend: Juice Shop: 1- and 2-star challenges. Own-code mission: access-control review of one Pulse controller.
Weeks 7–9: client-side, auth and defense
| Night reading | Hands-on |
|---|---|
| Chapter 6, sections 3–5 | PortSwigger: XSS, CSRF, CORS, JWT |
| Chapter 6, sections 6–9 | PortSwigger: SSRF, File upload; Juice Shop 3-star |
| Chapter 7 | TryHackMe SOC Level 1 first rooms; write two detection queries for Pulse |
Weekend: own-code missions: CSRF defense and trusted client IP in PulseBE, with tests.
Weeks 10–12: real practice
| Night reading | Hands-on |
|---|---|
| Chapter 8 | picoCTF practice gym: web and forensics categories |
| Your notes (revise) | HackTheBox Starting Point; first easy retired machine with a guided write-up |
| Chapter 9 (this page) | Join one live CTF from CTFtime with a beginner-friendly rating |
Week 12 checkpoint: choose your first cert (chapter 8) and book a date 8–10 weeks out. A date on the calendar turns "studying" into "preparing".
Quick reference: review on tired nights
The method: recon → enumerate → analyse → exploit → escalate → report.
The defender's loop: prepare → detect → triage → contain → eradicate → recover → learn.
Encodings: eyJ = Base64 JSON (likely a JWT) · trailing = = Base64 · only 0–9a–f = hex · %20 = URL encoding.
Status codes: 401 not authenticated · 403 not allowed · 404 not found (also what you return to hide existence) · 429 rate limited.
Cookie flags: HttpOnly (no script access) · Secure (HTTPS only) · SameSite=Lax/Strict/None (cross-site sending).
Top fixes: scope every query to the caller · parameterize every query · let the framework encode output · CSRF defense on cookie-auth mutations · rate-limit on trusted values · fail fast on missing secrets · log sensitive actions.
Useful Linux one-liners:
find / -perm -4000 -type f 2>/dev/null # audit SUID programs
grep -rniE "password|secret|api_?key" . # secrets in a codebase
cut -d' ' -f1 access.log | sort | uniq -c | sort -rn | head # top client IPs
git log -p | grep -iE "password|secret" # secrets in git history
Where to practise (all legal)
- OverTheWire: Bandit, then others
- TryHackMe: guided rooms and paths
- PortSwigger Web Security Academy: web, free
- picoCTF: beginner CTF, free, year-round practice gym
- HackTheBox: machines and challenges; Starting Point for beginners
- CTFtime: calendar of live CTF events
- CyberDefenders and Blue Team Labs Online: defensive challenges
- Your Hacking Lab: Juice Shop, DVWA, Metasploitable and your own code, locally
You've reached the end of the book. Now go to the lab, and come back to any chapter whenever a challenge sends you here.