Boost your security and resiliency in Kubernetes
summary
Argues for treating security like chaos engineering by continuously injecting repeatable vulnerability tests into CI/CD or Kubernetes cronjobs, running passive scans first and controlled active attacks later in a prod-like environment. Recommends starting with workload hardening, encrypting secrets, metadata-driven labeling, and limiting privileges. Uses concrete tools and patterns: kube-bench, kube-hunter, custom exploit snippets from exploit-db integrated into pipelines, and metric-driven reporting with Prometheus alerts. Gives real examples (Tesla credential leak, recent API proxy bug), emphasizes damage control and automating fixes after detection.
AI-written summary · about
chapters (14)
- 0:00Start
- 1:32Kubernetes Vulnerability
- 3:35Chaos Engineering
- 7:21Cluster Configuration Files
- 12:01Zero Trust Network Security
- 12:58Lack of Metadata Driven Deployments
- 14:26Legacy Integration and Infrastructure of Service Deployments on Cloud
- 15:12Platform Hardening
- 18:05Challenging the the Multi-Tenancy of Kubernetes
- 19:51Example Security Exploit Test
- 20:07Reading Metrics
- 21:35Do Passive and Active Testing
- 22:37Life Policy Violation and Alerting System
- 23:28Kubernetes Benchmark
related talks
19mHow to Secure Your Kubernetes Clusters
22mSecuring Kubernetes
43mKubernetes Security: Attacking and Defending Modern Infrastructure
35mKubernetes Security - Challenge and Opportunity?
26mMulti-layer hardening in Kubernetes
19mKubernetes Security: Navigating the Real-World Challenges
46mContinuous Kubernetes Security
11mSecuring the Kubernetes Ecosystem