What is Threat Modeling?
Threat modeling, told as a story about a guard who puts on a thief's mask and studies the drawing before a single brick is laid.
The builder brought the drawing for a new tower.One front door, one vault, one delivery hatch. The king wants to build right away. The guard asks for one more look.
Realizing after it is built that the hatch was a door too — that is too late.The guard watched the front door. The thief came through the hatch. Fixing it now means tearing the wall down again.
Threat modeling is looking at the drawing through a thief's eyes before building.The guard tries on the thief's mask. Draw what is being built, find where a thief would enter, ask what could go wrong, and write the fix onto the drawing.
Ask about each of the six thief habits, one by one.Six questions at every door. "What if a thief disguised himself here? Tampered? Denied it? Peeked? Blocked it? Got more keys?" So no habit is forgotten.
The fixes go onto the drawing before building.A gatekeeper and a log at the hatch, a separate key for the vault. Then check every brick, and once built, a hired thief tests it for real.
Threat modeling = before laying a brick, look at the drawing through a thief's eyes, find the ways in and what could go wrong, and draw the fixes in first.
Threat Modeling. Diagram the system's assets and data flows, mark trust boundaries and entry points, enumerate threats with a framework like STRIDE, and fold mitigations into the design. It is the cheapest point to build security in.
When grown-ups say it
- Threat modeling
- The drawing through a thief's eyes. Rob the tower on paper before building it. Four questions: what are we building, where would a thief go, what can go wrong, how do we stop it.
- Data flow diagram
- The rooms-and-paths picture. The vault, the hatch, and the arrows between them. Without this picture you do not even know what to guard.
- Trust boundary
- The dashed line around the trusted inside. Inside the line are our people; outside are strangers. Every arrow that crosses the line gets a question.
- Entry point
- Where a thief could get in. Not just the front door — the hatch, the windows, the chimney. → counting our doors from outside
- STRIDE
- The six thief habits. Spoofing, Tampering, Repudiation, Information disclosure, Denial of service, Elevation of privilege. The first letters spell STRIDE.
- Attack tree
- The thief's plan, drawn as a tree. Under 'open the vault' hang branches: steal the key, use the hatch… Block the easiest branch first.
- Mitigation
- The fix drawn into the plan. The gatekeeper at the hatch, the separate vault key, the log. → the castle that asks at every door
- DevSecOps
- Where this drawing gets looked at. The way the guard sits beside the builder from the start. Reading the drawing is the first job. → the builder and the guard, side by side