Applying STRIDE at Architecture Level
What you'll learn: How to systematically evaluate architectural components, interfaces, and data flows using the STRIDE threat categorization framework.
The Big Picture
Now that you've identified trust boundaries and drawn data flow diagrams (from your previous lessons), it's time to apply STRIDE—a mnemonic for Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, and Elevation of Privilege—to every element in your architecture.
How It Works
Walk through your architecture diagram methodically:
For each component (web server, database, API gateway):
- Spoofing: Can an attacker impersonate this component?
- Tampering: Can data or logic be modified maliciously?
- Repudiation: Can actions be denied without proof?
- Information Disclosure: Can sensitive data leak?
- Denial of Service: Can availability be disrupted?
- Elevation of Privilege: Can limited access become admin access?
For each data flow (arrows between components):
- Apply STRIDE focusing on data in transit: Can messages be intercepted (Information Disclosure)? Modified (Tampering)? Flooded (Denial of Service)?
For each interface (APIs, authentication endpoints):
- Ask STRIDE questions about the interface contract: Can callers spoof identity? Bypass authorization (Elevation of Privilege)?
Think of STRIDE as a security checklist you apply to a blueprint before construction begins—it's far cheaper to redesign a wall on paper than to tear it down later.
Practical Example
Looking at "User → Web Server → Database" flow across a trust boundary:
- Spoofing: User authentication required?
- Tampering: SQL injection possible? Input validation implemented?
- Information Disclosure: Is the database connection encrypted (TLS)?
- Elevation of Privilege: Does web server use least-privilege database credentials?
Key Takeaway: Applying STRIDE systematically to every architectural component, interface, and data flow transforms abstract security principles into concrete threats you can address before writing a single line of code.