6 Myths of Threat Modeling
summary
Claims six myths are false and shows that threat modeling finds design flaws pen tests and code review miss like an HVAC vendor access path, missing audit controls, or using encryption where a MAC is needed; uses STRIDE and TASM alongside static analysis and pen testing as complementary tools; reports 6 myths debunked, mentions STRIDE and TASM and running over a thousand threat models, teaches starters in about two hours, and shows that threat modeling surfaces quick wins, scales by apprenticeship, and integrates with CI when architectures are already threat modeled.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:00Overview
- 2:32We already do pen tests
- 6:08I dont want a threat model
- 10:28Its too late
- 14:14We already did the threat model
- 17:23Start with something simple
- 19:40Avoid falling into the classic engineers trap
- 23:27Its a teachable skill
- 25:51We dont have security experts
- 30:03We have never found a flaw
- 30:53No silver bullets
- 35:40Threat modeling vs static analysis
- 39:38Authentication
- 42:20Continuous Integration
related talks
53mThreat Modeling: uncover vulnerabilities without looking at code
47m📙 Your Threat Model Is Lying to You: Why Modeling the Design Isn’t Enough in 2026 🖥️
52mLessons From The Threat Modeling Trenches
43mThreat modeling
01h 00mThreat Modeling for Secure Software Design
22mEmpowering Developers through Threat Modeling Excellence
50mThreat Modeling With Architectural Risk Patterns
58mThreat Modeling In And For Your Organization