Adapting First Order Security Principles to Newer Architectural Trends
summary
Argues that old CIA models fail at scale and shows concrete checks: map cloud touchpoints, dig ASNs and routes to find unexpected peering paths, and annotate residual risks in SLAs; adopt a data‑centric lifecycle with integrity checks and cross‑region log management; harden ML pipelines with MLSecOps, periodic random verification of model outputs, and adversarial‑perturbation tests; design for the four Rs: robustness, redundancy, rapidity, resourcefulness so segmented services can run degraded and recover.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 1:01First order security problems
- 3:09McCumber model flaws
- 5:57Software security gaps
- 7:06Hardware security principles
- 8:53NIST framework concepts
- 11:44Simple network limits
- 12:45Modern architecture trends
- 14:16Cloud shared responsibility
- 15:40Architectural touch points
- 18:11Cloud security best practices
- 21:05Artificial intelligence in security architectures
- 24:56Zero Trust challenges
- 27:50Zero Trust trade-offs
- 30:37Emerging trends implications
- 32:06Residual risks tolerance
- 33:31Q&A
- 36:35Cloud provider controls
- 38:59Banking cloud risk
- 40:43Simplifying architectures
- 43:12Balancing security
- 46:03Zero Trust benefits
- 48:08Risk prioritization
related talks
45mSecurity Architecture, An Adventure?
43mSecurity By Design
35mAppSec Security: The SDLC in the age of agentic
49mArchitecting Security for Regulated Workloads in Hybrid Cloud
57mHow Do I Secure My Micro-Services?
27mA Gentle Introduction to MLSecOps
01h 04mShifting Security Everywhere
15mApplying DevSecOps Lessons To MLSecOps