threat model
A short, structured look at a design that asks what could go wrong and what you will do about it, before the thing is built.
In more detail
It follows the four questions: what are we building, what can go wrong, what are we going to do about it, and did we do a good enough job. The useful output is the list of open questions, each turned into a ticket with an owner or a written decision to accept the risk.
Example
The course treats threat modelling as a habit triggered by each change, such as a new entry point, data store or third party, rather than a yearly workshop.Related terms
- Four Question Framework — Adam Shostack's four threat modelling questions: what are we building, what can go wrong, what are we going to do about it, and did we do a good enough job.
- STRIDE — A threat-modelling checklist of six threat types: Spoofing, Tampering, Repudiation, Information disclosure, Denial of service and Elevation of privilege.
- data flow — A path that data takes from one part of a system to another, described by where it starts, where it ends, what it carries and which network it crosses.
- trust boundary — A line in a system where data passes between parts that trust each other differently, such as from the internet into your service or from your service to a vendor.
- entry point — Any place where something from outside can send input into a system, such as a web route, a message queue or a file upload.
- attack surface — Everything an attacker could try to use against a system: open ports, installed programs, accounts and settings.
Taught in
- Remote Servers And Trust — AI Engineering: LLM Apps, RAG & Agents
- Threat-Model An LLM App — AI Engineering: LLM Apps, RAG & Agents
- The Threat Model Habit — Application Security & Threat Modeling for Engineers
- Container Security: Minimal Bases And Non Root — Application Security & Threat Modeling for Engineers