|
|
|
|
LEADER |
01801 am a22001693u 4500 |
001 |
137536 |
042 |
|
|
|a dc
|
100 |
1 |
0 |
|a Costan, Victor
|e author
|
100 |
1 |
0 |
|a Massachusetts Institute of Technology. Computer Science and Artificial Intelligence Laboratory
|e contributor
|
700 |
1 |
0 |
|a Lebedev, Ilia
|e author
|
700 |
1 |
0 |
|a Devadas, Srinivas
|e author
|
245 |
0 |
0 |
|a Sanctum: Minimal Hardware Extensions for Strong Software Isolation
|
260 |
|
|
|c 2021-11-05T16:22:34Z.
|
856 |
|
|
|z Get fulltext
|u https://hdl.handle.net/1721.1/137536
|
520 |
|
|
|a Sanctum offers the same promise as Intel's Software Guard Extensions (SGX), namely strong provable isolation of software modules running concurrently and sharing resources, but protects against an important class of additional software attacks that infer private information from a program's memory access patterns. Sanctum shuns unnecessary complexity, leading to a simpler security analysis. We follow a principled approach to eliminating entire attack surfaces through isolation, rather than plugging attack-specific privacy leaks. Most of Sanctum's logic is implemented in trusted software, which does not perform cryptographic operations using keys, and is easier to analyze than SGX's opaque microcode, which does. Our prototype targets a Rocket RISC-V core, an open implementation that allows any researcher to reason about its security properties. Sanctum's extensions can be adapted to other processor cores, because we do not change any major CPU building block. Instead, we add hardware at the interfaces between generic building blocks, without impacting cycle time. Sanctum demonstrates that strong software isolation is achievable with a surprisingly small set of minimally invasive hardware changes, and a very reasonable overhead.
|
546 |
|
|
|a en
|
655 |
7 |
|
|a Article
|