A door with no locks? Let’s talk about threat modeling
summary
Step-by-step threat modeling workflow that starts with a data flow diagram and a RACI assignment, uses the four-question framework and STRIDE categories to scan a login flow, finds OTP-by-email MFA as a medium-likelihood/high-impact spoofing risk, and documents a concrete decision to mitigate by replacing email OTPs with an authenticator app plus replay and phishing tests. References OWASP insecure design, lists checkpoints for design/test/deploy cycles, and shows how to reuse security patterns.
AI-written summary · about
chapters (22)
- 0:00Introduction to threat modeling
- 1:11Threat modeling as a board game
- 4:23Meet the speaker and jargon
- 6:48What is threat modeling?
- 8:10Why threat modeling matters
- 9:59When to perform threat modeling
- 11:02Who should participate
- 13:28Organizing the threat modeling process
- 15:56Key threat modeling concepts
- 17:45STRIDE methodology explained
- 19:55Approaches to threat modeling
- 22:01Four-question framework
- 22:47Gathering security-relevant information
- 25:18Creating a data flow diagram
- 26:23Analyzing the login module design
- 29:15Scanning for threats with STRIDE
- 30:39Risk analysis and prioritization
- 32:24Risk treatment strategies
- 35:17Validating and iterating the design
- 36:22Testing and deployment phase
- 37:26Final advice and where to start
- 41:45Sharing experiences and communities
related talks
45mA door with no locks? Let’s talk about threat modeling
29mThreat Modelling 101
43mThreat modeling
53mThreat Modeling: uncover vulnerabilities without looking at code
22mEmpowering Developers through Threat Modeling Excellence
01h 00mThreat Modeling for Secure Software Design
57mUnlocking Threat Modeling
46mThreat modeling is on the rise