Moving Security Architecture from Art to Engineering
summary
A repeatable method is presented: a set of artifacts and layered diagrams that move security from guesswork to repeatable engineering, including system context/component/deployment diagrams, a shared‑responsibility deployment model, and a simple case study (dirty‑car congestion pricing) used to teach threat modeling and placement of controls. A reference enterprise architecture is built from 20 models, a vulnerability‑scanning proxy is added in deployment, over 1,000 learners train on the method, and an O’Reilly book publishes the full artifacts and an artifact dependency heat map.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:25Move security to engineering
- 5:22Architecture vs design in security
- 10:03Secure By Design limits
- 13:19Four domains for security
- 16:35Enterprise context for security
- 21:19Security solution thinking process
- 24:52System context diagrams
- 28:11Deployment architecture
- 37:06Final thoughts and key takeaways
- 42:04Q&A
related talks
40mTool Time: Building Your Cybersecurity Architecture Planning Toolbox
27mThe Architect's Guide to Fortifying Software Security
32mThe Art of Secure Architecture
45mSecurity Architecture, An Adventure?
10mDiving into a DevSecOps Reference Architecture
01h 00mApplying Security Engineering Principles to Complex Composite Systems
01h 00mLayered Threat Modeling: An Architectural Approach
57mUnlocking Threat Modeling