Confidential Containers: The Next Era of Cloud Data Security
summary
Confidential Containers put hardware TEEs into Kubernetes so encrypted memory and attested execution can protect data in use; implementation uses Coco, Trusty, Kata to abstract AMD/Intel/ARM/AWS Nitro differences, with an attestation flow that only releases decryption keys to verified enclaves. A demonstrated AI fraud model runs on encrypted S3 data via an init-container/key-broker pattern (now replaceable by Trusty), and sealed secrets keep keys hidden while pods operate inside TEEs.
AI-written summary · about
chapters (14)
- 0:00Confidential containers intro
- 1:30Confidential computing basics
- 3:37TEEs and hardware security
- 8:14Data protection in use
- 11:03Attestation and verification
- 14:59Key broker services
- 16:02Containers vs VMs vs clusters
- 18:08Trusty project implementation
- 19:12Responsibilities in confidential computing
- 21:40Kata and Coco projects
- 22:45AI fraud detection with encryption
- 25:54Sealed secrets for workloads
- 27:19Workshop and resources
- 27:41Q&A
related talks
31mConfidential Containers – Sensitive Data and Privacy in Cloud Native Environments
38mConfidential Containers Explained
50mConfidential Containers: Why, How, and Where Are We?
27mTrust No One: Bringing Confidential Computing to Containers
38mCloud native Confidential: Isolating Kubernetes Pods with Confidential Computing
30mTrust No One: Secure Storage With Confidential Containers
46mConfidential Cloud: Safeguarding Sensitive Data in K8s
49mCloud Native Confidential: Isolating Kubernetes Pods with Confidential Computing
