A door with no locks? Let’s talk about threat modeling
summary
Gives a concrete threat-modeling workflow: use Adam Shostack’s four-question framework, draw data flow diagrams, categorize threats with STRIDE, map to MITRE/CAPEC and OWASP Top10 2025, then rate likelihood/impact and run risk treatment (avoid, accept, transfer, mitigate). Demonstrates a real failure mode—email OTP vulnerable to phishing—and recommends switching to time-based TOTP (Google Authenticator, Duo, Authy), adding audits, RACI assignments and periodic health checks (6–12 months) with SBOM and compliance checks.
AI-written summary · about
chapters (16)
- 0:00Money Pit analogy
- 3:59What is threat modeling
- 9:00Who should participate
- 13:17Threats vulnerabilities risks
- 15:04STRIDE methodology
- 18:38Four-question framework step one
- 22:32Data flow diagrams
- 24:21Secure digital front door
- 26:27Security controls implementation
- 27:55Threat enumeration and analysis
- 30:04Risk management strategies
- 33:37Validating threat models
- 35:03Testing security controls
- 36:49Starting small habits
- 39:37Sharing knowledge community
- 40:00Q&A
related talks
43mA door with no locks? Let’s talk about threat modeling
29mThreat Modelling 101
43mThreat modeling
01h 00mThreat Modeling for Secure Software Design
57mUnlocking Threat Modeling
46mThreat modeling is on the rise
53mThreat Modeling: uncover vulnerabilities without looking at code
26mYou Too Can Do Threat Modeling