Produce a STRIDE threat model for a new feature
Когда использовать: Design review for a feature that touches user data, auth, or external networks.
Предварительные требования
- Feature design doc or architecture diagram — Paste into chat or point Claude at the file
- Skill installed — git clone https://github.com/eth0izzle/security-skills ~/.claude/skills/security-skills
Поток
-
Walk the systemUse security-skills. Here's the design for [feature]. Enumerate trust boundaries and data flows.✓ Скопировано→ Named trust boundaries, explicit data flow arrows
-
Apply STRIDEFor each boundary, call out Spoofing, Tampering, Repudiation, Info Disclosure, DoS, Elevation risks.✓ Скопировано→ Table with threats scored, not generic 'consider XSS'
-
Propose mitigationsRank the threats by likelihood * impact and propose concrete mitigations for the top 5.✓ Скопировано→ Specific controls (rate limit, signed requests, audit log)
Итог: A threat model doc ready for a security review meeting.
Подводные камни
- STRIDE becomes checkbox theater — Demand concrete attacker stories — 'attacker with X wants Y, does Z'