Sealed for All: Multi-Party Confidential Computing, No Trust
summary
Claim: multiple parties run a joint confidential workload where data, application, and result are all sealed using hardware TEEs and file encryption. Implementation uses AMD SEV‑SNP for attested launch, a prototype with modified Kata agent then reimplemented upstream with Kata Containers + Confidential Containers, IPtables loopback-only networking, device‑mapper root hash checks, OpenSSL encryption, and a secure key release via attestation. A chained attestation report binds runtime policy and provides post‑run auditability; the prototype and upstream composition work end to end.
AI-written summary · about
chapters (5)
- 0:00Multi-party confidential computing intro
- 4:00Single-tenant limits
- 9:51Multi-party confidential computing
- 12:44Open source challenges & solutions
- 25:19Summary & future
related talks
31mConfidential Containers – Sensitive Data and Privacy in Cloud Native Environments
38mConfidential Containers Explained
27mTrust No One: Bringing Confidential Computing to Containers
29mConfidential Containers: The Next Era of Cloud Data Security
40mDon’t Trust Opaque Clouds, Cryptographically Verify Instead!
37mIt's All About Trust: Why Confidential Computing Matters
36mEverybody is talking about Confidential Computing - the minimum Devs should know
42mSponsored Session: Confidential Computing - New Capabilities for New Workloads