Threat Modeling
Threat modeling is a structured way to work out what could go wrong with a system, app or process before attackers find out, by mapping how it works, identifying likely threats and deciding which protections to build in.
Also called: threat model, threat modelling, STRIDE
What is threat modeling?
Threat modeling means thinking like an attacker on purpose, early. Instead of waiting for a penetration test or a breach to reveal weaknesses, a team looks at a system's design and asks how it could be abused. OWASP's guidance frames it around four questions:
- What are we working on? Draw how the system works: users, data, components and connections.
- What can go wrong? List threats to each part.
- What are we going to do about it? Choose controls or accept the risk.
- Did we do a good job? Review and update as the system changes.
Common methods
- STRIDE, developed at Microsoft, prompts teams to consider Spoofing, Tampering, Repudiation, Information disclosure, Denial of service and Elevation of privilege.
- Attack trees break an attacker's goal into the steps needed to reach it.
- MITRE ATT&CK helps teams check designs against real attacker tactics and techniques.
Why it matters
Fixing a design flaw on a whiteboard is far cheaper than fixing it in production. CISA's Secure by Design initiative urges software makers to build security in from the start, and threat modeling is a core part of that.
How small businesses can use it
You don't need a formal method. Before launching a new customer portal, payment process or integration, spend an hour asking the four questions with the people who know it best. The same thinking works for business processes, such as how a fraudster might abuse your refund or supplier-onboarding process.
Related terms
Sources
- Threat Modeling Cheat Sheet (OWASP)
- Secure by Design (CISA)
Drafted with AI assistance, then edited and fact-checked by a person. How we use AI.
