Rethinking Isolation Mechanisms for Datacenter Multitenancy
summary
SGX-style enclaves leak via shared microarchitectural state (Foreshadow, hyperthreading fixes that cost up to 50 percent), so the paper proposes IME: a CPU with two physically isolated pipelines where the top-half runs tenant code and the bottom-half runs a mirrored security monitor that reads top-half PCs and registers, enforces CFI-like checks, and can stall or squash top-half retirement. Implementation is in Chisel and the processor exports a machine-readable microarchitectural description for tenant auditing.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:17SGX
- 1:17Peak Isolation
- 2:03Isolation Monitor Execution
- 3:47SGX Overview
- 5:48SGX Design Flaws
- 9:01Sample Security Policy
- 14:35Related Work
- 16:10Open Challenges
related talks
38mOne Ring -3 To Secure Them All: Computing with Hardware Enclaves
28mSanctum: Minimal Hardware Extensions for Strong Software Isolation
36mAttacking & Defending Kubernetes TEE Enclaves in Critical Infrastructure
25mTelling Your Secrets without Page Faults...
50mTrusted Execution Environments Meet the Blockchain
37mIt's All About Trust: Why Confidential Computing Matters
19mCoSMIX: A Compiler-based System for Secure Memory Instrumentation and Execution in Enclaves
20mHyperEnclave: An Open and Cross-platform Trusted Execution Environment