- Time
- 30–38 weeks + Ongoing
- Before this
- Foundations of computer science
- Leads to
- SOC analyst, Penetration tester, Security engineer, AI security researcher
Curious people who like taking things apart and want to protect people and systems.
Only test systems you own or have written permission to test. Use the practice labs below; attacking other systems is illegal almost everywhere.
-
Stage 1: Networking and Linux for security , 6–8 weeks
What to learn
Build: Capture your own browsing in Wireshark and write a short explanation of what each part of the traffic is.
Move on when: You can read a packet capture and say what happened, and you have finished most of OverTheWire Bandit.
-
Stage 2: Security fundamentals , 6–8 weeks
What to learn
Build: A one-page threat model for an app you built: what could go wrong, how likely it is, and what you would fix first.
Move on when: You can explain how TLS protects a login and why passwords are hashed, not encrypted.
-
Stage 3: Web application security , 8–10 weeks
What to learn
Free resources
Build: Find and write up at least ten vulnerabilities in OWASP Juice Shop, including how to fix each one.
Move on when: You can explain, exploit in a lab, and fix each class in the OWASP Top 10.
-
Stage 4: Pick a side: defend or attack , 10–12 weeks
What to learn
Build: Defence: a home lab that collects logs and detects three ATT&CK techniques. Attack: solve 20 picoCTF challenges and publish write-ups.
Move on when: You can show your lab or write-ups to an employer and talk through your reasoning.
-
Stage 5: Specialise and keep up , Ongoing
What to learn
Free resources
Build: Publish something others can use: a write-up, a detection rule, or a small tool.
Move on when: This stage never ends. Security changes every month.
Specialise: security roadmaps Certification roadmaps Back to all paths