Securing Kubernetes Multi-Tenancy: Navigating Challenges Through DevSecOps Control and Visibility
Talkat Multi-TenancyCon Europe 2024 · on Tuesday, 2024-03-19· at 11:40· Pavilion 7 | Level 7.3 | Room S02·
summary
Cites a Red Hat stat that 67% of teams delay Kubernetes deployments for security and maps concrete attack paths across identity, supply chain, network, and runtime/storage. Recommends setting automountServiceAccountToken=false, forbidding wildcard/“escalate” RBAC, enforcing default deny network policies with Cilium, using hardened registries and signed images (cosign, provenance, Chainguard Images), auditing global webhooks and PV lifecycle, and applying detections-to-policies via OPA Gatekeeper plus eBPF runtime telemetry; includes demos and implementation notes.
AI-written summary · about
chapters (9)
- 0:00Multi-tenant Kubernetes security
- 1:24Security challenges in deployments
- 4:13Four key risk buckets
- 7:23Identity risk and attack paths
- 13:01Supply chain and container integrity
- 18:43Network risk and lateral movement
- 21:55Runtime and storage risk
- 23:18Security from code to runtime
- 24:00Q&A
related talks
30mSecuring Kubernetes Multi-Tenancy
11mSecuring the Kubernetes Ecosystem
22mSecuring Kubernetes
35mKubernetes Security - Challenge and Opportunity?
22mSecuring Kubernetes: Best Practices for DevSecOps in the Cloud-Native Era
41mKubernetes Security Jumpstart
43mKubernetes Security: Attacking and Defending Modern Infrastructure
53mFlying Above the Clouds: Securing Kubernetes