2015
DOI: 10.1109/tpds.2014.2325564
|View full text |Cite
|
Sign up to set email alerts
|

Swiper: Exploiting Virtual Machine Vulnerability in Third-Party Clouds with Competition for I/O Resources

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
19
0

Year Published

2015
2015
2023
2023

Publication Types

Select...
5
2
1

Relationship

0
8

Authors

Journals

citations
Cited by 26 publications
(19 citation statements)
references
References 21 publications
0
19
0
Order By: Relevance
“…These methods are called NoHype and HyperWall. NoHype architecture is an architecture that eliminates the hypervisor and fragile part in traditional virtualization architecture [5] while HyperWall provides security assurance to the guest user and generate security trust assurance during the VM's lifetime. The NoHype architecture as shown in Figure 3 removes the hypervisor in the computer architecture, rendering the attacks on the system pointless as there is nothing to attack.…”
Section: Previous Workmentioning
confidence: 99%
“…These methods are called NoHype and HyperWall. NoHype architecture is an architecture that eliminates the hypervisor and fragile part in traditional virtualization architecture [5] while HyperWall provides security assurance to the guest user and generate security trust assurance during the VM's lifetime. The NoHype architecture as shown in Figure 3 removes the hypervisor in the computer architecture, rendering the attacks on the system pointless as there is nothing to attack.…”
Section: Previous Workmentioning
confidence: 99%
“…There are mainly four kinds of method for co-residency detection. The first bases on the network information [3], analysis network parameters to determine whether virtual machines are co-resident or not; the second bases on I/O resource competition [8], analysis the mutation of throughput load; the third bases on Co-Residency Watermarking [9], analysis time interval distribution of received network packet which are watermarked or non-watermarked; the fourth is use of L2 Cache Home Alone [10], analysis of the use of Cache.…”
Section: Virtual Machine Co-resident Detectionmentioning
confidence: 99%
“…To decreasing the cost of attack, attackers will also revoke VMs after completion co-residency detection. Through analysis detecting behavior conducted by Xiaolin Gui et al in actual cloud environment, combining articles [3,8,9,10,13], we preliminary got eight possible attributes in coresidency detection threats, as shown in Figure 2. The measurement object is the virtual machine co-residency detection threats, set measurement attribute set S t , and S t = {S t1 , S t2 , S t3 , S t4 , S t5 , S t6 , S t7 , S t8 , }.…”
Section: Evaluation Attributementioning
confidence: 99%
“…Other research focuses on performance interference effects in paravirtualized environments. This includes research on the impact of schedulers on network performance [6], [7], Amazon EC2 performance interference [8], and improving CPU time sharing by accounting for time consumed in the driver domain [12]. Because SR-IOV setups are specifically designed to allow I/O requests bypassing the hypervisor, no privileged component like the hypervisor or driver domain can be used for monitoring.…”
Section: Related Workmentioning
confidence: 99%
“…Previous studies analyzed performance interference effects caused by different types of shared resources, like CPU cores, the CPU's memory subsystem, disk-I/O [5] and network-I/O [6]- [8]. Some studies also address multiple resources [9]- [11].…”
Section: Introductionmentioning
confidence: 99%