Enabling secure multi-party collaboration with confidential computing
summary
Google describes an open source system called Confidential Spaces built on confidential VMs that claims to release secrets only to authorized workloads and to support mutually distrusting workload author, operator, and resource owner roles. It uses remote attestation, a hardened VM image, and an attestation verifier service integrated with Google IAM to tie attestation results to resource access. Examples show multi‑party compute where data owners keep control while processors pay costs; attack vectors and mitigations are enumerated.
AI-written summary · about
chapters (5)
- 0:00Introduction to secure collaboration
- 2:10Roles and limitations without confidential computing
- 4:56How confidential computing changes roles
- 6:58Multi-party use cases unlocked
- 9:03Confidential Space and its benefits
related talks
28mSealed for All: Multi-Party Confidential Computing, No Trust
11mLightning Talk: Computing Confidentially in the Clouds
45mConfidential Computing: Protecting Customer Data in the Cloud
13mVM Security with Confidential Computing
27mConfidential Tenancy: Towards Digital Sovereignty on Public Clouds
37mIt's All About Trust: Why Confidential Computing Matters
40mDon’t Trust Opaque Clouds, Cryptographically Verify Instead!
30mK8s meets confidential computing - the different ways of scaling sensitive workloads