Paved Roads To Express RBAC In Threat Models
summary
Claims a small, reusable artifact called access maps that teams fill out (principals, entity type, situational flags, runtime dynamics) and bring into threat models. Demonstrates it on a concrete AWS flow — API Gateway → Lambda → Step Function with CloudWatch logging — and shows it surfaces unexpected risks like auditors able to run transaction execute, missing CSRF/secure-cookie checks, and need for MFA for high-value ops. Works as pre‑work to cut meeting time and produce assignable risks; one fifth of the room already rolled out threat modeling.
AI-written summary · about
chapters (11)
- 0:00Threat modeling basics
- 1:05Misconceptions about threat modeling
- 4:21Threat modeling frameworks
- 8:02Threat modeling workflow
- 13:38Application architecture
- 16:10Sample transaction flow
- 20:01Access maps for RBAC
- 27:26Persona and role analysis
- 29:11Q&A: AI-driven threat modeling
- 31:42Q&A: Workshop details
- 34:33Q&A: Actionable properties
related talks
57mUnlocking Threat Modeling
46mThreat modeling is on the rise
21mFrom Moats to Slopes
53mThreat Modeling: uncover vulnerabilities without looking at code
51mSecure Applications, By Design
50mThreat Modeling With Architectural Risk Patterns
29mThreat Modelling 101
53mPractical Threat Modeling for real-world and Cloud Situations in our hybrid and W...