Principle of Least Privilege: How to Secure Kubernetes Without Making Users Hate You
summary
Kubernetes insecure workload configs top OWASP’s list, and this talk shows a concrete path: adopt least privilege across users and service accounts, remove privileged containers, and enforce network policies; use ArgoCD projects to limit namespaces and allowlisted resource types, and use Crossplane composite resources plus multiple smaller AWS IAM roles so provider configs don’t grant cluster-wide power. A Terraform-created root app deletion once wiped CI for ~30 minutes and pushed the team to act. Reports find >90% of namespaces lack network policies and scanners find clusters in ~22 minutes.
AI-written summary · about
chapters (20)
- 0:00Kubernetes security challenges
- 3:11Embarrassing security incident
- 5:38Principle of least privilege
- 7:05Least privilege in Kubernetes
- 8:09Zero trust principles
- 9:14Securing beyond users
- 13:08Role-based access control in Kubernetes
- 14:34RBAC implementation challenges
- 16:21Tools for least privilege
- 17:48Argo CD for Git deployments
- 18:52Securing Git repositories
- 20:18Project boundaries with Argo CD
- 21:01Preventing privileged workloads
- 22:02Secure development environments
- 22:43Lost least privilege mindset
- 24:27Crossplane and least privilege
- 26:33Handling emergencies
- 27:35Least privilege as ongoing process
- 27:56Next steps in security
- 33:26Q&A
related talks
28mKubernetes Security Low-Hanging Fruit
28mClosing the Loop: Applying Least Privilege and Ensuring We Did It Well
53mFlying Above the Clouds: Securing Kubernetes
22mSecuring Kubernetes
58mTop Secret Cloud Native Security Lessons
19mHow to Secure Your Kubernetes Clusters
30mFortifying Kubernetes
49mCluster Wrangling: How to make Kubernetes clusters secure and usable