Skip to main content

Table 4 Hardware-enhanced security guarantees in enclaves, and the cases when bad software stack may break these guarantees. Enclave Developers (ED) are responsible for the secure development

From: Managing confidentiality leaks through private algorithms on Software Guard eXtensions (SGX) enclaves

Notion Hardware feature May Break
Integrity Memory access checks Runtime vulnerability in TCB
Confidentiality Page-level secrecy Non-oblivious software stack
Fault tolerance Sealed storage Bad software implementation
Enclave availability Refuses to operate open Vulnerabilities in microcode