PortSwigger's Web Security Academy is free, written by the makers of Burp Suite, and it's the best web security curriculum there is. Each topic has a written explanation followed by labs graded Apprentice, Practitioner and Expert. The labs are deliberately vulnerable sites hosted by PortSwigger, so they're legal to attack.
Setup
- Create a free account (lab progress is saved).
- Install Burp Suite Community Edition (free). It's a proxy that sits between your browser and the site and lets you see, edit and replay every request.
- Use Burp's built-in browser (Proxy โ Open browser). It's preconfigured, so you don't need certificates or proxy settings.
Burp, the five tabs you'll use
| Tab | What it does |
|---|---|
| Proxy โ HTTP history | Every request your browser made. Your starting point for every lab. |
| Repeater | Send a request, edit it, send again. 80% of your time is here. |
| Intruder | Send many variants of a request. Rate-limited in the free edition, which is fine for learning. |
| Decoder | Base64, URL, HTML and hex encode/decode. |
| Comparer | Diff two responses, useful when one small difference matters. |
The core habit: find the request in HTTP history โ send to Repeater โ change one thing โ observe.
A sensible order
The Academy publishes its own learning path. This order works well for a developer:
| Phase | Topics | Why first |
|---|---|---|
| 1. Server-side basics | Path traversal, Access control, Authentication, Information disclosure | Logic bugs you can find with just Repeater, and the most common real-world issues |
| 2. Injection | SQL injection, OS command injection | The classic: untrusted data reaching an interpreter |
| 3. Client-side | Cross-site scripting, CSRF, CORS, Clickjacking | How the browser's trust model fails |
| 4. Server-side requests | SSRF, File upload, XXE | The server doing things on your behalf |
| 5. Modern | JWT, OAuth, API testing, GraphQL, Business logic, Race conditions | Directly relevant to Pulse (NestJS + JWT cookie) and Maeve |
| 6. Advanced | Deserialization, Request smuggling, Web cache poisoning, Prototype pollution | Do these after you're comfortable |
Aim to finish all Apprentice labs across the board first, then go back for Practitioner. Expert labs are optional.
How to study one topic
- Read the topic page fully. It's short and precise.
- Do the Apprentice labs without the solution. If stuck for 20 minutes, read only the first line of the solution.
- After solving, read the official solution anyway. There's often a cleaner way.
- Write the "developer's fix" in your notes, in the language you actually use (C# or TypeScript).
- Hunt for it in your own code (chapter 6 and the Hacking Lab's own-code missions).
Topic notes template
# Topic: <e.g. Access control>
What it is (one sentence):
Where it hides (which kinds of endpoints/inputs):
How I recognise it in Burp:
Labs done: Apprentice x/x, Practitioner x/x
The fix in C#:
The fix in NestJS/TypeScript:
Did I check Pulse / Maeve / TomiWebsites? [ ] yes โ notes:
Topics that map directly to your projects
- Access control: Pulse has role- and partner-scoped data. Most real breaches in apps like it are a user reading or changing data that isn't theirs.
- Authentication and JWT: Pulse issues a JWT in a cookie, Maeve uses cookie auth and guest codes. Read the JWT topic carefully.
- CSRF and CORS: any cookie-authenticated API that accepts requests from another site needs a CSRF defense. Chapter 6 shows how to check yours.
- Business logic: invites, guest links, password resets, imports: anything multi-step.
- API testing: NestJS with Swagger at
/docsis exactly the kind of API the Academy teaches you to map.
The Burp Suite Certified Practitioner (optional)
PortSwigger offers a paid, practical exam: the BSCP. It's well-respected for web specialists, and the Academy is its full syllabus. It's a good target after finishing most Practitioner labs.
Check yourself
- What's the difference between Proxy and Repeater?
- Which phase covers the bug class most likely to affect a multi-tenant analytics API?
- Pick one topic you finished. Can you write its fix in both C# and TypeScript from memory?