TryHackMe teaches with "rooms": short guided lessons, each with a browser-based machine to practise on and questions to answer. It's the gentlest on-ramp in security. Where Bandit is a puzzle, TryHackMe is a course.
Free vs subscription
Many rooms are free. The subscription unlocks the full learning paths, faster machines and the in-browser attack box for longer sessions. A good approach: start free, and subscribe for the months you're actively doing a path. Prices change, so check the site.
Which paths, in which order
Path names change over time; these are the stable building blocks. Take them roughly in this order:
| Order | Path (or its current equivalent) | What you get from it |
|---|---|---|
| 1 | Pre Security | Networking, the web, Linux and Windows basics. Skim what Bandit and chapter 3 already taught you. |
| 2 | Cyber Security 101 (formerly Introduction to Cyber Security) | A tour of offensive and defensive roles, so you can see which side pulls you. |
| 3a | Jr Penetration Tester | The offensive method: recon, web basics, Burp Suite, exploitation concepts, privilege escalation on Linux and Windows. Prepares you for PNPT/OSCP-style study. |
| 3b | SOC Level 1 | The defensive method: SIEM, log analysis, phishing analysis, threat intelligence, incident response. Prepares you for BTL1. |
| 4 | Web Fundamentals / Web Application Pentesting | Then switch to PortSwigger (chapter 5) for depth. |
As the only architect and security person on your own products, do both 3a and 3b. You need to think like the attacker to design, and like the defender to notice when something is happening.
How to get real value from a guided room
Guided rooms make it easy to "answer the question" without learning anything. Avoid that:
- Read the task text fully before starting the machine.
- Predict before you run. "I expect this to show port 80 and 22." Being wrong is where learning happens.
- Do every command yourself. Don't copy-paste from the task text; type it.
- When you get an answer, ask why it worked. If you can't explain it, re-read the task.
- Write a five-line summary per room in your notes (template below).
- Revisit rooms after a month without the instructions. Can you still do it?
The method you'll practise again and again
Almost every offensive room follows the same loop from chapter 0. Make it a checklist in your notes so it becomes automatic:
[ ] Recon โ what hosts/services exist? versions?
[ ] Enumerate โ for each service: what does it expose? users, pages, shares, versions
[ ] Analyse โ known weaknesses? misconfigurations? default credentials?
[ ] Exploit โ prove impact in the smallest safe way
[ ] Escalate โ from the user I am to the user I need
[ ] Report โ what, impact, evidence, fix
Defensive rooms have their own loop: detect โ triage โ scope โ contain โ eradicate โ recover โ learn (chapter 7).
Room notes template
# Room: <name> (path: <path>) date: <date>
Topic in one line:
Tools used:
Key commands / queries:
The idea I didn't know before:
How I'd DEFEND against what this room taught:
Revisit date:
That "how I'd defend" line is the difference between a CTF player and a security architect. For every attack room, write how you'd prevent or detect it in Pulse, Maeve or TomiWebsites.
Getting stuck
- Re-read the task. The hint is almost always in the text.
- Check the room's discussion or the official write-up after a real attempt.
- Ask Claude: "TryHackMe room X, task Y. I tried A and B, here's the output. Nudge, don't solve."
Milestones
- Week 2โ3: Pre Security done.
- Month 2: Cyber Security 101 done; you know which side you prefer.
- Month 3โ4: halfway through Jr Penetration Tester or SOC Level 1.
- Then: the free Advent of Cyber event every December is a great yearly refresher, and HackTheBox's starting-point machines are the next step up.