Threat Modeling: uncover vulnerabilities without looking at code
summary
Shows how to pick a small feature, draw a simple data flow diagram with trust boundaries and attack surface, then run STRIDE to find specific flaws like missing authentication, weak encryption, or unaudited admin actions. Demonstrates whiteboard-first exercises and tools (Microsoft Threat Modeling Tool, OWASP Threat Dragon, IriusRisk) and claims a design-level threat model typically finds high-impact issues in hours rather than costly post-release pen tests, then maps each STRIDE finding to concrete mitigations.
AI-written summary · about
chapters (28)
- 0:00Start
- 0:57The Application Security Podcast
- 2:05Why and How of Threat Modeling
- 4:53Threat Modeling
- 5:26Mitigating Vulnerabilities
- 6:35Threat Modeling Nirvana
- 8:48The Attack Surface
- 10:31Spot the Flaw
- 12:34Application Security Approaches
- 15:13Dynamic Application Security Testing
- 17:28Expert in Threat Modeling
- 21:55Threat Modeling Threat Modeling Is Not an Exact Science
- 24:09Attack Surface
- 25:14Data Flow Diagrams
- 25:33Data Stores
- 25:46The Trust Boundary
- 27:04Threats to the External Entity
- 27:32Functional Attributes
- 28:23Example of a Data Flow Diagram
- 29:08Stride
- 29:27Classifications of Threats
- 31:22Documentation
- 34:45Rules of Threat Modeling Club
- 35:10Data Flow Diagram
- 45:24What Threat Modeling Looks like
- 49:00Stride Methodology
- 49:28Tampering
- 51:37Threat of Elevation of Privilege
