Threat Modelling 101
summary
Argues that doing lightweight threat modeling early saves time and money and produces actionable issues rather than vague lists. Builds a password reset model with a data flow diagram into components (web app, auth service, queue/Kafka, mail service, DB) and applies STRIDE/PASTA and a rapid method. Finds roughly 50 concrete problems — weak token generation, nonexpiring links, race conditions, missing ACLs, user enumeration — and proposes fixes like token expiry, mutual TLS, ACLs, password policy enforcement. Uses data flow diagrams, C3/C4 options and mentions Ory Kratos/Oathkeeper and SMTP queues.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:15What is Threat Modelling
- 7:04Thread Modelling
- 9:54Threat Modelling
- 13:27Diagram
- 17:05Brainstorm
- 24:06Conclusion
related talks
43mThreat modeling
45mA door with no locks? Let’s talk about threat modeling
01h 00mThreat Modeling for Secure Software Design
46mThreat modeling is on the rise
43mA door with no locks? Let’s talk about threat modeling
53mThreat Modeling: uncover vulnerabilities without looking at code
57mUnlocking Threat Modeling
49mThreat Modeling Toolkit