Evolving Threat Modeling Through the Open Threat Model Format
summary
Proposes a concrete, machine-readable specification called Open Threat Model (OTM) — a minimal YAML/JSON schema (inspired by OpenAPI) that encodes project metadata, assets, components, trust zones, data flows, threats and mitigations and supports multiple representations (diagram, code, infra). Demonstrates tooling plans: StartLeft generates OTM from CloudFormation, Terraform and Visio; OTM files plug into CI/CD, policy engines and CSPM/vuln tooling to block deployments (example: assert WAF mitigates SQLi). Spec is early, CC‑licensed and seeks community contribution.
AI-written summary · about
chapters (7)
- 0:00Introduction and context
- 1:33Evolution of technology
- 10:47Wardley mapping and design
- 21:48Human-centric threat modeling
- 29:14Full stack threat modeling
- 43:32Open threat model format
- 52:38Q&A session
related talks
47mAutomating Architectural Risk Analysis with the Open Threat Model format
34mThreat Model-as-Code
49mThreat Modeling Toolkit
30mAgile Threat Modeling with Open-Source Tools
58mThreat Modeling In And For Your Organization
32mIntro to Threat Modeling in the Cloud
40mCloud Threat Modeling - from Architecture Design to Application Development
01h 01mImprove your threat modelling through the science of simplicity