Value driven threat modelling - security by design
summary
Claim: lightweight, value-driven threat modeling fits inside two-week sprints and DevOps by putting security into user stories rather than big up-front models. Uses STRIDE, attack trees and PASTA as options, plus threat libraries and Security Stack Exchange for quick fixes. Focuses on why we build this, what must go right, explicit failure states and security unit tests; ranks risk with story points. Notes one security person per 100 developers and says this approach saves time but is not sufficient for aviation/DoD/bank-level systems.
AI-written summary · about
chapters (6)
- 0:00Introduction and motivation
- 1:54What is threat modeling
- 13:38Threat modeling methods
- 16:52Problems with classic threat modeling
- 23:40Value-driven threat modeling
- 37:27Summary and call to action
related talks
35mValue Driven Threat Modeling
29mRedefining Threat Modeling: Security team goes on vacation
38mIterative Threat Modelling: Security in Agile Development
22mEmpowering Developers through Threat Modeling Excellence
53mThreat Modeling: uncover vulnerabilities without looking at code
52mLessons From The Threat Modeling Trenches
11mThreat modeling state of practice in Dutch organizations
57mUnlocking Threat Modeling