Creating STRIDE Threat Tables
What you'll learn: How to organize your STRIDE threat analysis into clear, actionable tables that document threats systematically across your system components.
Why Threat Tables Matter
You've learned how to identify STRIDE threats per element and per interaction. Now you need a way to organize all those threats so your team can actually act on them. A STRIDE threat table is like a structured checklist that captures every identified threat in one place, making nothing slip through the cracks.
What Goes in a STRIDE Threat Table
Think of a threat table as a spreadsheet where each row represents one specific threat. For each threat you document:
- Component/Element: What system part is affected (e.g., "Login API", "User Database", "Payment Gateway")
- STRIDE Category: Which threat type (Spoofing, Tampering, Repudiation, Information Disclosure, DoS, Elevation of Privilege)
- Threat Description: Plain-English explanation of what could go wrong
- Attack Vector: How an attacker could exploit this (e.g., "Attacker intercepts unencrypted traffic")
- Potential Impact: What damage results if successful (e.g., "User credentials stolen, accounts compromised")
- Risk Level: Priority ranking (often High/Medium/Low)
Building Your Table
Start with your Data Flow Diagram. For each element (process, data store, external entity, data flow), go through all six STRIDE categories. Ask: "Does this threat apply here?" If yes, add a new row with complete details.
For example, for a "User Login Process":
- Spoofing: Attacker presents fake credentials → impersonation
- Tampering: Attacker modifies password during transmission → unauthorized access
- Information Disclosure: Credentials sent over HTTP → credential theft
Key Takeaway: STRIDE threat tables transform scattered threat observations into structured documentation, ensuring every component's vulnerabilities are captured, described, and prioritized for remediation.