2008
DOI: 10.1109/msp.2008.24
|View full text |Cite
|
Sign up to set email alerts
|

Taming Virtualization

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
15
0
1

Year Published

2010
2010
2017
2017

Publication Types

Select...
5
4

Relationship

0
9

Authors

Journals

citations
Cited by 25 publications
(16 citation statements)
references
References 1 publication
0
15
0
1
Order By: Relevance
“…It is a program running on the host, and hence, susceptible to risk when the volume and complexity of application code increases (Krutz and Vines, 2010). One attack of externally modifying hypervisor is known as VM-based malware/rootkit (VMBR) (Carbone et al, 2008;Le and Wang, 2011), which attempts to execute malicious code instead of system call from hypervisor to the host OS. A Trusted Platform Module (TPM) in the host helps to create a trust relationship with the hypervisor (Krutz and Vines, 2010).…”
Section: Virtual Machinesmentioning
confidence: 99%
“…It is a program running on the host, and hence, susceptible to risk when the volume and complexity of application code increases (Krutz and Vines, 2010). One attack of externally modifying hypervisor is known as VM-based malware/rootkit (VMBR) (Carbone et al, 2008;Le and Wang, 2011), which attempts to execute malicious code instead of system call from hypervisor to the host OS. A Trusted Platform Module (TPM) in the host helps to create a trust relationship with the hypervisor (Krutz and Vines, 2010).…”
Section: Virtual Machinesmentioning
confidence: 99%
“…This is possible when attacker injects an hypervisor beneath the original one, or has direct access to the original hypervisor. Hijacking an Operating System (OS) using a hypervisor is associated to the emergence of VM-based rootkit (VMBR) with Subvirt, Vitriol and Blue Pill as illustrating proof-of-concepts [33]. When the target is the host OS, hyperjacking becomes a serious attack as once the hypervisor is owned, attacker can take full control of the environment, and use any guest OS as a staging ground to attack other guests.…”
Section: From Cloud Providermentioning
confidence: 99%
“…This requires that only the hypervisor is protected from attacks. To this end, several solutions have proposed the protection of the hypervisor from run-time attacks , or a micro-hypervisor architecture [Murray et al 2008] [Steinberg and Kauer 2010], or the introduction of a further nested layer of virtualization [Carbone et al 2008] [Zhang et al 2011a]. All these approaches will be categorized and detailed in the following.…”
Section: Solutionsmentioning
confidence: 99%
“…Other solutions insert another layer below the hypervisor to check the integrity of the hypervisor. GuardHype [Carbone et al 2008] is a hypervisor with a focus on VMBR prevention that allows the execution of legitimate third-party hypervisors but disallow VMBRs. GuardHype mediates the access of third-party hypervisors to the hardware virtualization extensions, effectively acting as a hypervisor for hypervisors.…”
Section: 34mentioning
confidence: 99%