The One Where We Threat Model During Development
summary
Explains a concrete workflow: create a baseline threat model, then loop per backlog story with a curator ensuring each security-relevant story uses an if-this-then-that checklist; teams adopt a 12-item subject list for fast baseline elicitation and a one‑page checklist to build muscle memory. Presents tooling and outputs: the pytm Python library stores models with attributes, generates DFD/sequence diagrams and reports that flag mismatched data classifications and suggested mitigations. Describes CTM applied at Autodesk and teams that move from ad hoc to continuous, iterative fixes.
AI-written summary · about
chapters (12)
- 0:00Intro
- 3:01Agenda
- 4:17Security & threat model primer
- 14:11Threat Modeling Manifesto
- 18:54Values
- 22:22Principles
- 24:47Patterns
- 27:05Anti-patterns
- 33:35CTM: Continuous threat modeling
- 51:11Pytm: Pythonic way of threat modeling
- 58:35Resources
- 59:25Outro
related talks
58mThreat Modeling In And For Your Organization
49mThreat Modeling Panel
57mIntroducing Threat Modelling To Established Teams
52mLessons From The Threat Modeling Trenches
22mEmpowering Developers through Threat Modeling Excellence
38mIterative Threat Modelling: Security in Agile Development
35mValue Driven Threat Modeling
39mValue driven threat modelling - security by design