Shift Down Security! How Platform Teams Can Help Break the Logjam
summary
Argues that platform teams must implement policy as code and guardrails so developers don’t shoulder every security task, demonstrating concrete wins: swapping a bloated nginx image with Alpine or distroless cuts reported CVEs from ~130 to a few, nightly image builds and base image hardening remove noise for app teams, use of Kyverno/Gatekeeper/Rego patterns enforces PSS and RBAC at CI, deploy and verify SLSA/VEX attestations via OCI images to centralize supply‑chain checks and automate admissions.
AI-written summary · about
chapters (11)
- 0:00Cloud Native Security intro
- 1:04Traditional vs Cloud Native security
- 3:56Shift Left challenges
- 8:36Enterprise roles and duties
- 10:01Why Shift Down now
- 11:07Defining Shift Down Security
- 13:56Vulnerability management with base images
- 16:28Policy as Code for misconfigs
- 23:16Securing software supply chains
- 25:03Platform teams as security enablers
- 28:11Q&A
related talks
29mThe SecDevOpronomicon
41mPanel Discussion: Foundations of Security and Leadership at Scale
27mIncluding security in your engineering culture
35mShift left the right way to build secure software
57mBuilding a Modern Security Engineering Organization
19mPlatform Engineering beyond the Buzzword?
22mThe challenges of Platform teams
25mCommon platform team mistakes and how to avoid them