Course contentsShow
← Security
Lesson 46 of 3,0522. Threat Modeling FundamentalsFree lesson

Documenting Threat Models

Understand what to capture in threat model documentation: diagrams, threats, mitigations, assumptions, and action items.

Documenting Threat Models

What you'll learn: How to capture and organize the essential elements of a threat model so it remains useful, actionable, and understandable to your team.

Why Documentation Matters

You've learned to identify assets, draw data flow diagrams, spot threats, and prioritize them. But if all that work lives only in your head or scattered notes, it's lost the moment you move to another project. Good documentation transforms threat modeling from a one-time exercise into a living security resource.

What to Capture

Your threat model documentation should include five core elements:

1. Diagrams

Your data flow diagrams (DFDs) are the visual foundation. Include the system overview and any decomposed diagrams showing trust boundaries, data flows, and external entities.

2. Identified Threats

List each threat you discovered. For each one, note which component it affects and which security principle (confidentiality, integrity, availability) is at risk.

3. Mitigations

Document how you plan to address each threat—whether through technical controls, process changes, or accepting the risk. Link mitigations back to specific threats.

4. Assumptions

Record what you assumed to be true: "Users authenticate via company SSO," "Database runs inside corporate network," etc. When assumptions change, your threat model needs revisiting.

5. Action Items

Create a clear list of next steps with owners and deadlines. This turns analysis into accountability.

Think of your threat model document as a security blueprint—anyone reviewing it should understand what you built, what could go wrong, how you're protecting it, and what still needs doing.

Key Takeaway: Threat model documentation captures diagrams, threats, mitigations, assumptions, and action items—turning security analysis into a shared, actionable reference that survives beyond the initial modeling session.