CVSS 4.0 finally makes sense
Scoring the lab findings and justifying each rating in a sentence was very practical.
Browse
Test a deliberately vulnerable app with ZAP and Burp Community, cover the OWASP Top 10 with a clear method and write findings developers can fix
Created by Jonas Lindqvist
Most web application breaches come from a short list of well understood mistakes. This course teaches you to find those mistakes the way professional application security testers do: with written permission, a clear method and a report that helps developers fix what you found.
You will run OWASP Juice Shop, a deliberately vulnerable online shop built for training, on your own computer. Every exercise targets that local lab. You will map the application with an intercepting proxy, test it against the OWASP Top 10 categories using the OWASP Web Security Testing Guide as a checklist, and then write up each finding with evidence, a severity rating and a concrete fix.
Testing systems you do not own or have written authorisation to test is illegal in most countries. Every technique in this course is practised only on your local lab or on training platforms that grant permission. The course explains what authorisation for real work looks like and how to keep your tools inside the agreed scope. The aim throughout is defensive: find weaknesses so they can be fixed, and help developers stop them from coming back.
Application security engineer helping developers write, review and test secure code
I sit between development and security teams, reviewing code, tuning scanners and teaching developers how common vulnerabilities actually appear in real code bases.
My courses are written for developers first. We read vulnerable code, exploit it in a safe lab, fix it and add a test or rule so it stays fixed. Examples use Python, JavaScript and Java because that is what most teams I meet write.
I focus on the OWASP Top 10, API security, authentication, and tooling such as Semgrep, CodeQL and secret scanners. My aim is that security becomes part of your normal review, not a separate step at the end.
Scoring the lab findings and justifying each rating in a sentence was very practical.
Rewriting weak findings into strong ones was eye opening. Our developers now actually read the reports.
I used to fire up a scanner and hope. The WSTG checklist approach and the finding template changed how I test our own apps at work.
Nice that it works with free tools only. The Repeater lessons made manual testing feel much less chaotic.
Running everything locally against Juice Shop meant I could practise without worrying about where my traffic was going.
The two account approach to horizontal access control was the most useful part. I would have liked one more example on APIs.
Appreciated how often it repeats that you only test your own lab or with written permission. Good habit to build early.
Content is accurate, but I had to pause and read up on JWTs and cookies before the session lessons made sense.