The privacy aspect of TPM attestation
summary
Explains how TPM2.0 attestation produces signed PCR values via PCR extend and quote and how privacy is preserved by using credential activation to prove an attestation key lives under the manufacturer-backed endorsement hierarchy without revealing the unique endorsement key. Demonstrates using non‑endorsement attestation keys so TPM obfuscates personally identifiable fields (reset/restart counts, firmware) while leaving PCR digests verifiable, shows the credential activation flow works end‑to‑end, and warns that cross‑logging can deanonymize devices.
AI-written summary · about
chapters (15)
- 0:00Introduction to TPM 2.0
- 1:05Remote attestation basics
- 3:30Attestation roles and process
- 6:08TPM measurements and PCRs
- 8:52Secure boot and quoting
- 11:09Roots of trust and privacy
- 14:29Information lifecycles
- 17:14TPM internal architecture
- 21:15TPM identities and keys
- 24:08Signing attestation codes
- 27:34Credential activation
- 30:25Privacy-preserving attestation
- 34:04Privacy responsibilities
- 37:06Platform responsibility summary
- 38:41Demonstration and closing
related talks
42mTPM based attestation - how can we use it for good?
29mRemote Attestation of IoT devices using a discrete TPM 2.0
29mThe Trusted Platform Module
40mUsing TPMs to Cryptographically Verify Devices at Scale
28mThe TPM as an everyday security tool
43mHardware-backed Per-process Secrets
25mTPM 2.0 Attestable Firmware: Recovering Trust After Firmware Flaws
33mSecuring TPM Secrets with TXT and Kernel Signatures