Threat modeling
summary
Security issues split roughly 50% design flaws versus bugs and threat modeling targets those design flaws early using data flow diagrams and the STRIDE checklist to find spoofing, tampering, disclosure, DoS, repudiation and elevation problems. Practical steps include scoping, drawing DFDs with numbered data flows, rating trust boundaries, documenting threats and linking mitigations to issue-tracker tickets. Tools mentioned that generate threats or drawings are Microsoft Threat Modeling Tool and OWASP Threat Dragon; real examples show mobile APIs and CDN upload sequences exposing lost access control and URL-tampering risks.
AI-written summary · about
chapters (33)
- 0:00Introduction
- 0:53What do you do
- 1:16How do we know
- 1:57There is no free lunch
- 3:03Flaws and bugs
- 4:10Benefits of threat modeling
- 5:25A quote from a participant
- 6:00Threat modeling
- 8:04When to do threat modeling
- 9:02How to do threat modeling
- 9:19S scoping
- 10:07Models are wrong
- 10:25Generic documentation
- 11:14granularity
- 12:34data flow diagrams
- 18:41data movement
- 19:47identifying threats
- 20:00rating threat boundaries
- 20:42focusing on flaws
- 21:16finding threats
- 21:40spoofing
- 22:45tampering
- 23:26integrity
- 24:17information disclosure
- 25:20denial of service
- 26:29elevation of privilege
- 27:11external entities
- 27:55resources
- 28:42threat modeling tool
- 35:35rating threats
- 37:06mitigations
- 40:42Summary
- 42:12Recommendation
related talks
01h 00mThreat Modeling for Secure Software Design
53mThreat Modeling: uncover vulnerabilities without looking at code
22mEmpowering Developers through Threat Modeling Excellence
57mUnlocking Threat Modeling
46mThreat modeling is on the rise
29mThreat Modelling 101
49mThreat Modeling Toolkit
49mThreat Modeling Panel