The B-MAD Approach to Threat Modeling
summary
Argues that the common instruction bring me a diagram creates needless conflict and late-stage fixes by turning a collaborative design step into a blame-driven blueprint review; proposes shifting to the whiteboard stage with lightweight DFDs and STRIDE checklists, using collaborative drawing tools and big wall maps, aligning deliverables to the four-question framework, and giving retrospectives equal weight to analysis. Offers the Jenga model (technical, organizational, interpersonal blocks), sample deliverables, and metrics (expectation rates like “1 of 10 vs 8 of 10” stopping issues) to measure success.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:06Security Teams Conflict
- 3:41Threat Modeling
- 6:48BMAD Approach
- 10:19How BMAD Causes Problems
- 13:03miscommunication
- 14:26contributors
- 19:32Big Wall Maps
- 21:06Organizational fixes
- 23:46Resources
related talks
49mThreat Modeling Panel
22mEmpowering Developers through Threat Modeling Excellence
57mIntroducing Threat Modelling To Established Teams
01h 00mThreat Modeling for Secure Software Design
35mValue Driven Threat Modeling
43mThreat modeling
01h 00mLayered Threat Modeling: An Architectural Approach
01h 00mThe One Where We Threat Model During Development