Automating Architectural Risk Analysis with the Open Threat Model format
summary
Claims a reproducible format, Open Threat Model (OTM), that turns Infrastructure as Code into interoperable threat models using infrastructure as code sources (CloudFormation, Terraform) and a python generator that applies JMESPath-style mappings. Schema is YAML/JSON, treats mitigations as first-class objects, and encodes trust and CIA scores on a 0–100 risk scale. Demo generates an OTM file and a Graphviz-style architecture diagram from cloud templates, showing the approach works end to end.
AI-written summary · about
chapters (29)
- 0:00Introduction
- 0:35What is architecture
- 2:13What is architectural risk analysis
- 3:17Insecure design
- 4:04Threat modelling
- 6:13Shifting security left
- 8:32Architecture challenges
- 10:32Software development vs manufacturing
- 10:54Software development is art
- 11:55Continuous iterative revisionist design
- 13:01Canvas framework
- 14:52Warding map
- 17:46Continuous iterative revisionist
- 18:37Infrastructure as code
- 19:49Open threat model format
- 21:10Potential use cases
- 24:12Open specification
- 28:13Object attributes
- 30:57Key differences
- 32:25Unique Identifiers
- 33:26Representations
- 34:00Application Code
- 36:17Trust Zones
- 37:14Components
- 38:52Data Flow
- 39:07Threats
- 40:20Mitigations
- 41:15Component
- 42:21Demo
related talks
01h 00mEvolving Threat Modeling Through the Open Threat Model Format
34mThreat Model-as-Code
50mUsing IAC to Accelerate Threat Modeling
30mAgile Threat Modeling with Open-Source Tools
50mThreat Modeling With Architectural Risk Patterns
58mThreat Modeling In And For Your Organization
57mUnlocking Threat Modeling
01h 14mAutomating Cybersecurity Compliance in DevSecOps with Open Information Model for Security as Code