📙 Your Threat Model Is Lying to You: Why Modeling the Design Isn’t Enough in 2026 🖥️
summary
Claim: threat models stop at design and miss deployed reality, so production scans must feed them. Gives numbers (94% of cloud infra has manual pieces, 6% fully codified, 80% of exposures from misconfiguration, ~1% from code CVEs) and breach examples (Capital One SSRF + over‑privileged IAM role exfiltrating S3; Log4Shell hiding in transitive deps). Recommends using SAST SCA DAST IaC outputs (Snyk/Dependabot/SBOMs) to map findings to components, ask “was this modeled?”, and run a six-step workflow as a two‑week pilot.
AI-written summary · about
chapters (7)
- 0:00Introduction and context
- 4:05The state of threat modeling
- 10:01Gaps between design and reality
- 18:50Real-world impact of blind spots
- 29:20Evidence-based threat modeling
- 35:32Practical six-step workflow
- 44:57Q&A and concluding thoughts
related talks
01h 00mThreat Modeling for Secure Software Design
52mLessons From The Threat Modeling Trenches
46mThreat modeling is on the rise
43mThreat modeling
55m6 Myths of Threat Modeling
53mThreat Modeling: uncover vulnerabilities without looking at code
57mUnlocking Threat Modeling
58mThreat Modeling In And For Your Organization