Attacking & Defending Kubernetes TEE Enclaves in Critical Infrastructure
summary
Explains that hardware TEEs like SGX and TDX can cryptographically attest, seal, and isolate pod-level workloads but are not a silver bullet: side‑channel and supply‑chain attacks remain primary risks. Shows concrete stacks: OpenEnclave → Graphene/Occlum for a middle ground, alternatives via rune/runE and Marble Run or cross‑compile to WASM, maps controls to GDPR/PCI/HIPAA/NIST 800‑53, notes new SGX supports up to ~1TB enclave memory, and reports a prototype built with Graphene/Occlum tradeoffs in performance and TCB size.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 0:40What is a TEE
- 1:44Who is a TEE for
- 2:49Use Cases
- 5:32TEE chip implementations
- 6:40How to establish trust
- 7:58TEE attestation
- 8:59TEE data
- 9:56How to use TEE
- 10:42casa de papel
- 12:00features
- 13:14attack tree
- 13:38trust
- 14:25silver bullet
- 15:10where does Kubernetes fit
- 15:51operating Kubernetes
- 16:35Open Enclave
- 17:35Unikernel
- 19:34RunE
- 20:46MarbleRun
- 21:48Arcs
- 22:52Overview
- 23:46Formal Verification
- 26:19Compliance
- 27:25Government Agencies
- 27:50Whats Next
- 29:28What About the Supply Chain
related talks
37mIt's All About Trust: Why Confidential Computing Matters
05mSponsored Keynote: Bringing Confidential Computing to Kubernetes
40mKubernetes Meets Confidential Computing - The Different Ways of Scaling Sensitive...
41mPanel: A New Root Of Trust: Changing Computing With TEE
38mOne Ring -3 To Secure Them All: Computing with Hardware Enclaves
18m"If It's Shared, It's Vulnerable": Is Kubernetes the Right Platform for Confidential Compute?
30mK8s meets confidential computing - the different ways of scaling sensitive workloads
46mOpen for AI: Secure paths to data collaboration volume and diversity