"If It's Shared, It's Vulnerable": Is Kubernetes the Right Platform for Confidential Compute?
summary
Kubernetes shares kernels, control planes, network stacks and buses, so attacker-capable primitives like eBPF snooping, conntrack hijacks, cache side channels (TDX‑ray), ACPI injection and hypervisor exploits lead to broad leakage; the talk enumerates ~37 published post‑2023 attacks and proposes a production architecture that runs every workload as a TEE‑protected guest, gates secrets and devices on a composite attestation chain, wraps compute/network/storage/control in hardened overlays and recommends one tenant, one node, one control plane for true multi‑tenancy.
AI-written summary · about
chapters (10)
- 0:00Confidential computing challenges
- 1:46Shared substrates in compute
- 3:52Attacks on silicon
- 7:24Hypervisor co-tenancy risks
- 9:34Shared nodes compromise
- 10:38Kubernetes control plane risks
- 12:07Isolation limits
- 13:53Confidential threat model
- 15:18Threat assessment & topology
- 16:29Q&A
related talks
35mKubernetes Security - Challenge and Opportunity?
43mKubernetes Security: Attacking and Defending Modern Infrastructure
53mFlying Above the Clouds: Securing Kubernetes
58mTop Secret Cloud Native Security Lessons
40mKubernetes Meets Confidential Computing - The Different Ways of Scaling Sensitive Workloads
36mAttacking & Defending Kubernetes TEE Enclaves in Critical Infrastructure
30mK8s meets confidential computing - the different ways of scaling sensitive workloads
22mSecuring Kubernetes