Publication | Open Access
Strong and efficient cache side-channel protection using hardware transactional memory
144
Citations
45
References
2017
Year
Unknown Venue
Cache-based Side-channel AttacksEngineeringInformation SecurityComputer ArchitectureConfidential ComputingSide-channel AttackHardware Transactional MemoryMulti-channel Memory ArchitectureHardware SecurityTrusted Execution EnvironmentSecure ComputingHardware Security SolutionComputer EngineeringData PrivacyComputer ScienceMemory ArchitectureData SecurityCryptographyCache Side ChannelsCloud ComputingCache MissesSide-channel AnalysisTransactional Memory
Cache-based side‑channel attacks pose a serious threat in multi‑tenant environments such as modern cloud data centers. The authors propose Cloak, a technique that uses hardware transactional memory to prevent adversarial observation of cache misses on sensitive code and data. Cloak retrofits vulnerable code by employing hardware transactional memory to mask cache‑miss patterns, and the authors experimentally confirm its immunity against state‑of‑the‑art attacks. Cloak provides strong protection against all known cache‑based side‑channel attacks with low performance overhead and effectively blocks leakage from Intel SGX enclaves.
Cache-based side-channel attacks are a serious problem in multi-tenant environments, for example, modern cloud data centers. We address this problem with Cloak, a new technique that uses hardware transactional memory to prevent adversarial observation of cache misses on sensitive code and data. We show that Cloak provides strong protection against all known cache-based side-channel attacks with low performance overhead. We demonstrate the efficacy of our approach by retrofitting vulnerable code with Cloak and experimentally confirming immunity against state-of-the-art attacks. We also show that by applying Cloak to code running inside Intel SGX enclaves we can effectively block information leakage through cache side channels from enclaves, thus addressing one of the main weaknesses of SGX.
| Year | Citations | |
|---|---|---|
Page 1
Page 1