STRIDE per Element Analysis
What you'll learn: How to systematically apply each STRIDE threat category to every component in your data flow diagram.
The Core Idea
You've learned the six STRIDE threat types (Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, and Elevation of Privilege). Now it's time to apply them methodically to each element in your data flow diagram: processes, data stores, data flows, and external entities.
Not every threat applies to every element—and that's the power of this approach. You work through each diagram component asking, "Which STRIDE threats are relevant here?"
How It Works in Practice
For Processes
Ask all six STRIDE questions: Can someone spoof this process? Tamper with its execution? Deny it ran? Steal its data? Crash it? Gain higher privileges through it?
For Data Stores
Focus on Tampering (modifying stored data), Information Disclosure (unauthorized reading), Denial of Service (making the store unavailable), and sometimes Repudiation (no logs of who accessed what).
For Data Flows
Consider Tampering (intercepting and modifying data in transit), Information Disclosure (eavesdropping), and Denial of Service (blocking the communication).
For External Entities
Primarily Spoofing (pretending to be that entity) matters most—you typically don't control external entities to prevent other threats.
Why This Matters
Without a systematic approach, you'll miss threats. By checking each element against applicable STRIDE categories, you create a comprehensive threat inventory rather than guessing based on intuition.
Key Takeaway: STRIDE per Element means methodically asking which of the six threat types apply to each specific component in your DFD, creating complete threat coverage without wasting effort on irrelevant combinations.