6 Strategies to Bring Order to Kubernetes Security Disruptions
summary
Six concrete moves: embed image scanning in CI/CD and admission controllers to block images before deployment, enforce network policies and IAM/SECcomp for microsegmentation, use runtime detection like Falco plus capture and enrichment with Sysdig and eBPF for forensic context, and plan continuous registry rescans because many containers have <5-minute container lifespan and production fleets can reach 50,000–500,000 containers so prevention, context, and host-level coverage must operate at scale.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:58A New Stack Is Forming
- 5:27Emerging Stack Components
- 6:03The New Stack Creates A Security and Visibility Gap
- 7:30DevOps Must Prioritize Security
- 8:29A Modern Approach to Security
- 12:40Core Principles of an Open Source Security Stack
- 13:47Security Belongs in the Pipeline
- 17:08Verify Workloads Before Deployment
- 18:25Context Is King
- 24:39Prevention: Batteries Included
- 31:01Have a plan for when sh*t hits the fan
related talks
41mKubernetes Security Jumpstart
33mKubernetes Security Jumpstart
28mKubernetes Security Low-Hanging Fruit
11mSecuring the Kubernetes Ecosystem
22mSecuring Kubernetes
19mHow to Secure Your Kubernetes Clusters
35mKubernetes Security - Challenge and Opportunity?
24mA Checklist for Security from the Container to the Kubernetes: An Overview End to End