How I Learned to Stop Worrying and Trust the Cloud
summary
Argues concrete mechanisms that make clouds measurable and fixable: end-to-end proofs of storage (SafeStore) issues signed certificates and cheap random audits across multiple clouds so missing blocks trigger reconstruction and contractual penalties; metadata+proofs of misbehavior (Depot) lets every node validate history and evict forks, eliminating trust for many correctness properties; replicated tablet servers and co‑located storage (Salus) add small IO and ~10–20% write overhead but double throughput in network‑limited setups; privacy‑preserving aggregation and per‑app vaults (PiBox) use differential‑privacy declassifiers for bounded leaks.
AI-written summary · about
chapters (35)
- 0:00Intro
- 0:44The Opportunity
- 3:25Cloud Concerns
- 4:12New Concerns
- 5:33How to Stop Worrying
- 7:35Technical Principles
- 8:04End-to-End Checks
- 9:10Safestore
- 13:45Safestore Summary
- 18:22Metadata
- 19:19Local Checks
- 20:23Faulty Nodes
- 21:43Join Forks for Consistency
- 22:55Robustness
- 23:47Redundancy
- 24:30Salis
- 26:44How Salis Works
- 31:17Colocating Salis
- 32:44Salis vs Hbase
- 33:40How rights work
- 35:28Initial goal
- 38:15PiBox
- 41:03Trust
- 42:26Build a per user per app sandbox
- 43:20Your sandbox goes up into the cloud
- 44:05Content storage channel
- 44:35Privacy-preserving aggregation channel
- 45:35Sharing channel
- 46:04Demo
- 47:23Summary
- 48:20Restricted Programming Model
- 48:51Conclusion
- 49:41Stop Worrying
- 51:26Trust the Platform
- 54:35Safe Store
related talks
25mImproving Safety with Privacy: An Exploration of Privacy...
40mDon’t Trust Opaque Clouds, Cryptographically Verify Instead!
39mPerils of the cloud
24mCracking the Code of Cloud Security
40mSecurity today and tomorrow : Adapting the rules to suit technological advances
39mManaging Trust Between Multiple Clouds and Non-human Identities Without Passwords
49mCloud Security Made for the EU: Securing Data & Applications
48mControlling Clouds: Beyond Safety