Course contentsShow
← Security
Lesson 2637 of 3,05250. Secure Architecture and DesignFree lesson

Creating Architecture Data Flow Diagrams

Techniques for documenting system components, data flows, and trust boundaries in architectural diagrams for threat analysis.

Creating Architecture Data Flow Diagrams

What you'll learn: How to map system components, data flows, and trust boundaries to expose attack surfaces during threat modeling.

The Core Idea

A Data Flow Diagram (DFD) in security architecture is your system's blueprint for threat analysis. It visualizes what components exist, how data moves between them, and where trust changes—crucial for spotting vulnerabilities before attackers do.

Think of it like mapping water pipes in a building: you need to know where the clean water enters, where it flows, which valves control it, and where contamination might seep in. Similarly, DFDs show you where sensitive data originates, travels, and where security controls (or gaps) exist.

Essential DFD Elements

Components to Document

  • External entities (users, third-party services): rectangle symbols
  • Processes (applications, services): circles/rounded boxes
  • Data stores (databases, file systems): parallel lines
  • Data flows (arrows): show direction and label with data type

Trust Boundaries

Draw dotted/dashed lines around security perimeters where privilege levels change:

  • Internet → DMZ → internal network
  • User space → admin panel
  • Your infrastructure → cloud provider

These boundaries are where validation, authentication, and encryption must happen.

The Practical Approach

  1. Start broad: Identify all external actors and entry points
  2. Follow the data: Trace sensitive information (credentials, PII, financial data) through every hop
  3. Mark privilege changes: Every trust boundary crossing is a potential attack vector
  4. Number flows: DF1, DF2 helps reference specific paths in threat analysis
  5. Keep it layered: Create high-level context diagrams, then detailed component views

The goal isn't artistic perfection—it's creating a shared visual language for security discussions. When you later apply STRIDE threats, you'll examine each flow and each boundary systematically.

Key Takeaway: Architecture DFDs expose your system's attack surface by mapping components, data flows, and trust boundaries—the foundation for systematic threat identification and security control placement.