"I Didn't Peek: and I Can Prove It": Confidential Computing for Audits and Regulators
summary
Confidential computing uses chip-level TEEs in Intel AMD Nvidia and Arm to keep data encrypted in use and to produce remote attestation signatures that auditors accept as cryptographic receipts; regulators can see hashed measurements proving the exact code and inputs ran in an enclave. It enables multi-party workflows (hospitals to pharma, cross-bank credit checks) without full data sharing, exposes availability as a gap, notes attestation crypto needs post-quantum updates, and the consortium lists 13 active projects; fines cited reach about 2.5 billion.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:10Data sovereignty regulations in India
- 8:03Security for auditors
- 12:58Confidential computing
- 17:14Remote attestation proofs
- 22:48Confidential computing benefits
- 29:05Regulators and boards
- 32:16Summary
- 32:59Q&A
related talks
37mIt's All About Trust: Why Confidential Computing Matters- 37mIt's All About Trust: Why Confidential Computing Matters
47mThe Rise of Confidential Computing, What It Is and What it Means to You
42mSponsored Session: Confidential Computing - New Capabilities for New Workloads
11mLightning Talk: Computing Confidentially in the Clouds
45mConfidential Computing: Protecting Customer Data in the Cloud
36mEverybody is talking about Confidential Computing - the minimum Devs should know
36mSecurity for AI and Multi-Party Collaboration with Confidential Computing (Oh, and...