Kubernetes Security: Tackling Attacks & Best Practices
summary
Claims that vanilla Kubernetes is not secure out of the box, that attacks begin within 22 minutes of exposure, and that a managed path (EKS + Fargate) reduces surface are backed by specifics: manages ~1,000 Kubernetes clusters, demos show a dangerous manifest (default serviceAccount + clusterRoleBinding + privileged true) and an admin access grant via EKS access entries, and concrete tools and checks are recommended: kube-bench, GuardDuty, Amazon Inspector, ECR, Prometheus+Grafana.
AI-written summary · about
chapters (11)
- 0:00Kubernetes security challenges
- 6:55Shared responsibility in AWS EKS
- 10:06Least privilege user access
- 16:31Secure AWS access for apps
- 19:00Securing containers and hosts
- 22:09Scanning images for vulnerabilities
- 24:39Logging monitoring incident detection
- 30:17Encrypting secrets and credentials
- 33:07Network policies best practices
- 35:54Learning resources workshop
- 45:19Q&A
related talks
34mKubernetes Security 101: Best Practices to Secure Your Cluster
43mKubernetes Security: Attacking and Defending Modern Infrastructure
35mKubernetes Security - Challenge and Opportunity?
33mSecuring Kubernetes in the Cloud
33mKubernetes Security: Horror Stories to Help Secure Your Cluster
37mKubernetes to Cloud Attack Vectors: Demos Inside
22mSecuring Kubernetes: Best Practices for DevSecOps in the Cloud-Native Era
29mKubernetes Security Best Practices