Threat Modeling Panel
summary
Panel argues threat modeling succeeds when it’s modular, iterative and owned by the team, not a one-off review. Practical takeaways: use connection flow diagrams and version-control architecture snapshots, start with an attack-tree or checklist for concrete threats, and try the Elevation of Privilege card game to onboard teams. Tools include Visio-based analysis and an early Visio-to-cloud threat extractor that outputs threat lists; emphasis is on doing lightweight, repeatable models that get revisited in agile sprints.
AI-written summary · about
chapters (6)
- 0:00Start
- 17:11Version Control Ideas and Threat Modeling
- 20:38Standardized Threat and Mitigation Libraries for Cloud
- 41:21The Future of Threat Modeling Is Modular
- 44:27Beginning Threat Modeling What Would Be a Good Area To Start
- 45:37The Goals of the Threat Agents
related talks
58mThreat Modeling In And For Your Organization
01h 00mThreat Modeling for Secure Software Design
46mThreat modeling is on the rise
43mThreat modeling
53mThreat Modeling: uncover vulnerabilities without looking at code
22mEmpowering Developers through Threat Modeling Excellence
57mUnlocking Threat Modeling
01h 00mLayered Threat Modeling: An Architectural Approach