Empowering Developers through Threat Modeling Excellence
summary
Shows STRIDE applied to data-flow diagrams with a line-by-line checklist (spoofing, tampering, repudiation, info disclosure, DoS, elevation) and a concrete beach-bar example that maps threats to mitigations. Outputs are prioritized, contextualized risks and practical next steps: add audit trails, encryption, SCA and pen test follow-ups. Argues early threat modeling cuts later cost, embeds security in development workflows, and produces actionable artifacts (diagrams, risk justifications, and remediation items).
AI-written summary · about
chapters (9)
- 0:00Threat modeling intro
- 2:22Developer familiarity
- 7:46What is threat modeling
- 11:21STRIDE methodology
- 13:31System diagrams for threats
- 15:58Threat modeling with beach bar
- 18:52Benefits for applications
- 20:18Breaking silos
- 21:25Key takeaways
related talks
53mThreat Modeling: uncover vulnerabilities without looking at code
43mThreat modeling
01h 00mThreat Modeling for Secure Software Design
35mValue Driven Threat Modeling
29mA Threat Modeling Process can Help you Transition from DevOps to DevSecOps
39mValue driven threat modelling - security by design
41mAn Exploratory Tester's lessons on Security Threat Modeling
57mUnlocking Threat Modeling