methodEngineering & architecture

Threat Modeling

A structured method for identifying valuable assets, trust boundaries, plausible threats, and proportionate security responses before and during system change.

Download Markdown (.md)

01What it means

Threat modeling examines how a system could be abused or fail under adversarial conditions. Teams describe the system and its trust boundaries, identify threats and affected assets, assess risk, choose mitigations, and verify the resulting requirements. It is a recurring design activity, not a one-time diagram or penetration test.[1][2]

Recurring adversarial design analysis Model the system, identify abuse, reduce risk, and verify the controls
  1. 01FrameScope, assets, objectives, attackers, assumptions
  2. 02MapComponents, flows, privileges, trust boundaries
  3. 03Identify threatsMisuse cases, attack trees, STRIDE
  4. 04Treat riskDesign changes, controls, ownership, residual risk
  5. 05Verify + revisitTests, evidence, implementation changes

Threat modeling is updated as architecture and evidence change; it is not a one-time diagram or penetration test.

02Why it matters

Security testing finds some implemented flaws, while threat modeling can reveal missing controls and unsafe architecture before implementation. It helps teams focus limited effort on plausible, consequential paths rather than generic checklists.

03When to use it

Threat-model new systems, high-risk features, identity and payment flows, major architecture changes, and newly exposed trust boundaries. Scale depth to consequences and uncertainty, then revisit when data, actors, dependencies, or deployment changes.

04How it works

  1. Define scope, assets, security objectives, assumptions, and relevant attackers.
  2. Map components, data flows, entry points, privileges, dependencies, and trust boundaries.
  3. Identify threats systematically using misuse cases, attack trees, or a framework such as STRIDE.
  4. Assess likelihood, impact, existing controls, uncertainty, and risk ownership.
  5. Select design changes, preventive and detective controls, tests, and accepted residual risk.
  6. Track actions and revisit the model as implementation and evidence evolve.

05A practical example

Example

Before adding document sharing, a team maps invitation links, tenant boundaries, storage, previews, and email delivery. It identifies link leakage and cross-tenant access, then adds expiring scoped links, object-level authorization tests, and audit events.

06Where it breaks

A model reflects the participants' knowledge and can miss novel threats, implementation defects, or changing dependencies. Scoring can create false precision, and findings provide no protection unless owned, implemented, tested, and monitored.

Common mistakes

  • Starting from a generic threat list without mapping the actual system.
  • Modeling only external attackers and ignoring compromised accounts, insiders, and dependencies.
  • Treating every theoretical threat as equal instead of prioritizing consequence and plausibility.
  • Producing a diagram and never tracking mitigations or revisiting assumptions.

07Sources

  1. Threat ModelingOWASP Foundation · Security practice guidanceThreat Modeling
  2. Threat Modeling ManifestoThreat Modeling Manifesto · Practitioner principlesThreat Modeling Manifesto
View saved topics

Start typing to search titles, definitions, categories, and frameworks.