How to Secure Your Kubernetes Clusters
summary
Argues that Kubernetes security is part of software-defined cloud security and not perimeter defense, recommends shift left by running static, dynamic, dependency and container scans in the CI pipeline on every commit, and cites a pen‑test chain: vulnerable WordPress dependency → remote code execution → pod traversal → API server access → AWS credentials and secrets exfiltration. Claims 90% of prevention is configuration and points to the CIS benchmark for settings, warns that breaking a monolith into 42 services multiplies attack surface and cost unless scanning and policy automation like a single integrated GitLab pipeline are used.
AI-written summary · about
chapters (7)
- 0:00Intro
- 1:37Security trends
- 5:10Cloud requires shared accountability
- 7:16Kubernetes attack demonstration
- 9:40Center for Internet Security
- 10:25Key Principles
- 11:50Breath Before Death
related talks
11mSecuring the Kubernetes Ecosystem
26mBoost your security and resiliency in Kubernetes
22mSecuring Kubernetes
35mKubernetes Security - Challenge and Opportunity?
43mKubernetes Security: Attacking and Defending Modern Infrastructure
19mKubernetes Security: Navigating the Real-World Challenges
20mDefense in Depth: Securing your new Kubernetes cluster from the challenges that lurk within
26mMulti-layer hardening in Kubernetes