Nimble: Rollback Protection for Confidential Cloud Services
summary
Nimble implements an append-only ledger using a tiny trusted state machine inside TEEs combined with crash-fault-tolerant cloud storage, and it ships a reconfiguration protocol that lets the provider replace endorsers without losing safety. The core protocol is Dafny-verified, the prototype is written in Rust and C++ and runs on Intel SGX and AMD SNP-SEV. Measured throughput ranges from tens of thousands requests/sec with end-to-end latency under 3.2 ms (in-memory KV) to several thousand requests/sec with ~30 ms on Azure Table, and the TCB stays small.
AI-written summary · about
chapters (8)
- 0:00Introduction to rollback
- 1:48Rollback attack case study
- 3:11Append-only ledger solution
- 4:21Requirements and challenges
- 5:58Core design insights
- 7:51System architecture
- 9:37Fault tolerance
- 11:33Evaluation and conclusion
related talks
40mDon’t Trust Opaque Clouds, Cryptographically Verify Instead!
45mConfidential Computing: Protecting Customer Data in the Cloud
11mLightning Talk: Computing Confidentially in the Clouds
44mAdvancements in Confidential Computing
19mKeynote: Attested, Transparent, Sovereign: The Evolution of Confidential Computing
40mDoing the Safety Dance: Will Trusted Execution Environments Protect Us?
40mConfidential Computing Across Multiple Clouds and Platforms: Project Enarx
42mSponsored Session: Confidential Computing - New Capabilities for New Workloads