Threat Modelling for DevSecOpss
Threat modelling is a structured way to find security problems in a design before code exists. You draw how data flows between components and trust boundaries, then ask what can go wrong using methods such as STRIDE, rank the threats and decide on mitigations. It is cheaper than finding the same flaws after release.
Stage: Secure Design and Code · Part of the DevSecOps roadmap · Last reviewed 19 November 2026
What to learn in Threat Modelling
- Draw a data flow diagram with trust boundaries for an application
- Apply STRIDE to each element and list threats
- Rate threats and choose mitigations that match the risk
- Explain attack trees and when they help
- Record threats and decisions in a reviewable document
- Run a short threat modelling session with developers
Threat Modelling interview questions
What does STRIDE stand for?
Spoofing, Tampering, Repudiation, Information disclosure, Denial of service and Elevation of privilege. Each letter is a category of threat, and you check every component and data flow in the diagram against them to find what could go wrong.
When should threat modelling be done?
At design time, and again when the architecture changes significantly, such as adding a new integration or a data store. Doing it early is cheapest, but even a lightweight session on an existing system reveals useful gaps.
Where Threat Modelling fits in the DevSecOps roadmap
Threat Modelling belongs to the Secure Design and Code stage (intermediate level), which takes about 9 hours. Stop problems before they ship.
Other units in this stage
Back to the full DevSecOps roadmap