Demystifying remote attestation
summary
Remote attestation is evaluated by concrete properties: comprehensiveness and interpretability of evidence, hardware-signed measurements, timeliness and a trustworthy attester. Implementations integrated Intel SGX with EPID/DCAP, AMD SEV‑SNP (they ship specific version checks), and AWS Nitro (later abandoned because the hypervisor is trusted), and a Decentriq data clean room runs on those primitives. Practical fixes include embedding expected TCB version numbers and using reproducible builds with Nix and the reproducibility project to bind source to measurements, while physical chip location and root‑of‑trust replacement remain open problems.
AI-written summary · about
chapters (8)
- 0:00Introduction to remote attestation
- 2:30Value of confidential computing
- 5:43Security properties of attestation
- 9:33Measurement and versioning challenges
- 14:30Hardware root of trust concerns
- 16:16Binding measurements to source code
- 20:08Physical security of chips
- 23:19Call for open verification library
related talks
29mA Simple Protocol for Remote Attestation of System Integrity
42mSponsored Session: Confidential Computing - New Capabilities for New Workloads
15mRemote Attestation in AMD SEV-SNP Confidential VMs
29mRemote Attestation of IoT devices using a discrete TPM 2.0
37mIt's All About Trust: Why Confidential Computing Matters
01h 13mTutorial: Complete Platform Attestation: Remotely Verifying the Authenticity and Integrity of your Platform’s Hardware, Firmware, and Software
24mShrinking The Elephant - A Confidential Computing Attestation Sequel
47mAMD SEV-SNP Attestation: Establishing Trust in Guests