Threat model a feature before building it

Steps

1. 1Diagram the feature: actors, data flows, trust boundaries, stores
2. 2Walk STRIDE per boundary: spoofing, tampering, repudiation, info-disclosure, DoS, elevation
3. 3Rank findings by likelihood × impact; top items get design changes
4. 4Write mitigations as acceptance criteria in implementation tickets
5. 5Add abuse cases to the test plan alongside functional cases
6. 6Revisit the model when architecture shifts, not just annually

Common Pitfalls

• ▲Threat models as one-time compliance theater
• ▲Trusting internal services implicitly across boundaries

Commands

$ npx skills add aniruddhaadak80/skills --skill application-security-threat-model-feature

$ npx skills add aniruddhaadak80/skills --skill application-security-threat-model-feature -g

Tags