The elephants in the confidential room: Attestation and verification
summary
Confidential Containers exposes that attestation is fragmented and vendor‑specific so a workload must implement multiple custom clients to get a decryption key. The project defines a generic KBS protocol over HTTPS and JSON Web tokens, a plugable relying party that forwards evidence to verifiers, and a manufacturer‑agnostic reference value provider that consumes in‑toto/SLSA provenance. Using DICE/TCG x509 evidence extensions aims to let one CVM speak to many attestation services.
AI-written summary · about
chapters (7)
- 0:00Introduction to attestation
- 1:24The attestation gap in confidential computing
- 3:08The relying party and verification flow
- 9:31Fragmentation in attestation services
- 14:02Why standardization is critical
- 18:40Simplifying the attestation stack
- 20:57Q&A: Static vs dynamic attestation
related talks
24mShrinking The Elephant - A Confidential Computing Attestation Sequel
40mDon’t Trust Opaque Clouds, Cryptographically Verify Instead!
24mFrom Trust Assumptions To Trust Evidence: Why PKI and Confidential Computing
17mHow to Build a Confidential Attestation Client
28mSealed for All: Multi-Party Confidential Computing, No Trust
35mChains of trust in Confidential Computing
19mKeynote: Attested, Transparent, Sovereign: The Evolution of Confidential Computing
29mConfidential Containers: The Next Era of Cloud Data Security