Most security problems start as ordinary coding mistakes or design decisions that nobody questioned. Secure coding is the habit of writing software so that those mistakes are harder to make, and threat modeling is the habit of asking what could go wrong before you build it. Together they are the cheapest place to stop a vulnerability, long before a pipeline or a scanner has to catch it.
You'll start with the OWASP Top 10, the standard list of the most critical web application risks, then move on to the everyday secure coding practices that prevent them. After that you'll learn threat modeling with STRIDE, a simple method for finding spoofing, tampering, data leaks, and other threats by looking at how your system is put together.
Once you can spot weaknesses in code and design, you'll be ready for the next module, Security Testing Automation, where you add tools to your pipeline that find these problems automatically.
What changed in the OWASP Top 10 since 2021, the two new additions, and how each risk category affects the applications you build.
The essential secure coding practices every developer should know, and how to apply them as you write code.
An easy introduction to the STRIDE framework and how it helps you identify and address security threats in software systems.
A step-by-step walkthrough of running a quick threat model on a simple web application with STRIDE and the Microsoft Threat Modeling Tool.