Layered Threat Modeling: An Architectural Approach
summary
Argues that threat modeling must be layered: separate architectural from solution-level work, with different scopes and goals, and shows a reproducible method using Archimate models plus an imported Copic mechanisms of attack catalog. Builds an Archimate cloud reference, links threats to components, assigns likelihood and impact, and scripts an auto-generated traceability matrix that outputs threats and matched control profiles. Demonstration works end to end and the claim is that this produces repeatable enterprise deliverables and clearer control ownership across service models.
AI-written summary · about
chapters (11)
- 0:00Layered threat modeling intro
- 1:49Solution vs architectural threat modeling
- 6:27Enterprise architecture goals
- 11:44Cloud service models example
- 14:15Meta model for threat modeling
- 22:22Identifying threats in models
- 31:19MITRE CAPEC threat catalogs
- 34:30Threat modeling demo in ArchiMate
- 42:19Key conclusions summary
- 46:33Pitfalls in threat modeling
- 49:07Q&A
related talks
57mUnlocking Threat Modeling
49mThreat Modeling Panel
40mCloud Threat Modeling - from Architecture Design to Application Development
58mThreat Modeling In And For Your Organization
50mThreat Modeling With Architectural Risk Patterns
51mApplication Threat Modeling Implementation Tips and Tricks
43mThreat modeling
52mLessons From The Threat Modeling Trenches