Architectural Threat Modeling Fundamentals
You'll learn how to systematically identify security threats at the architecture level by mapping trust boundaries and data flows.
What Is Architectural Threat Modeling?
Threat modeling at the architecture phase means analyzing your system's design before you build it to identify where attackers might strike. Unlike code-level security reviews, architectural threat modeling examines the big picture: how components interact, where data crosses trust boundaries, and which assets are most vulnerable.
Think of it like reviewing building blueprints for fire safety. You wouldn't wait until construction is complete—you'd identify fire hazards, map escape routes, and place extinguishers during the design phase. Similarly, architectural threat modeling finds security weaknesses while they're cheapest to fix.
Core Elements
Trust Boundaries are invisible lines where data moves from one security context to another—like when a user request crosses from the internet into your internal network, or when your application queries a database. These boundaries are where validation, authentication, and authorization must happen. Every trust boundary is a potential attack surface.
Data Flow Diagrams (DFDs) visualize how information moves through your system. By mapping processes, data stores, external entities, and the connections between them, you can see where sensitive data travels and identify exposure points. For example, if payment card data flows through multiple services, each hop is a potential interception point.
Asset Identification means cataloging what you're protecting: user credentials, financial data, intellectual property, or system availability itself. Different assets require different protection levels.
The process typically follows: draw your architecture, identify trust boundaries, trace data flows, enumerate threats at each boundary (using frameworks like STRIDE), and determine mitigations.
Key Takeaway: Architectural threat modeling uses trust boundaries and data flow analysis to identify security risks during system design, when they're easiest and cheapest to address.