2016 IEEE International Symposium on High Performance Computer Architecture (HPCA) 2016
DOI: 10.1109/hpca.2016.7446082
|View full text |Cite
|
Sign up to set email alerts
|

CATalyst: Defeating last-level cache side channel attacks in cloud computing

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

2
149
0

Year Published

2017
2017
2021
2021

Publication Types

Select...
4
3
2

Relationship

0
9

Authors

Journals

citations
Cited by 277 publications
(159 citation statements)
references
References 25 publications
2
149
0
Order By: Relevance
“…However, they only used Admin VM as an agent to conduct security policy. Liu et al [14] proposed CATalyst, a pseudo-locking mechanism that uses CAT to partition the LLC (Last-level Cache) into hybrid hardware-software managed cache. They implemented a proof-of-concept system using Xen and Linux running on a server with Intel processors, and show that LLC side-channel attacks can be defeated.…”
Section: Related Workmentioning
confidence: 99%
“…However, they only used Admin VM as an agent to conduct security policy. Liu et al [14] proposed CATalyst, a pseudo-locking mechanism that uses CAT to partition the LLC (Last-level Cache) into hybrid hardware-software managed cache. They implemented a proof-of-concept system using Xen and Linux running on a server with Intel processors, and show that LLC side-channel attacks can be defeated.…”
Section: Related Workmentioning
confidence: 99%
“…One popular mitigation technique is isolating security sensitive code execution. This is done by allocating private resources to security sensitive applications [6], [16], [24]. In [16], [24] hardware and software mechanisms are used to partition caches into private regions to mitigate cache-based timing side-channel attacks.…”
Section: Why Attenuating Timing Leakage Is Notmentioning
confidence: 99%
“…We expect that vCAT could be applied here as well, while also providing cache isolation among tasks, a property that cannot be achieved by existing CAT-based solutions such as [18].…”
Section: Related Workmentioning
confidence: 99%
“…We reserved cache partitions 0-7 (CBM bitmask 0×000FF) to CPU1 and partitions 8-15 (CBM bitmask 0×0FF00) to CPU2. We flushed the entire cache initially, and mitigated potential interference to CPU1 and CPU2 by moving all system services to the remaining cores and assigning to them the remaining partitions (partitions [16][17][18][19]. We created a periodic task that sequentially accesses a 4MB array.…”
Section: Cache Lookup Controlmentioning
confidence: 99%