Twenty-Third Annual Computer Security Applications Conference (ACSAC 2007) 2007
DOI: 10.1109/acsac.2007.10
|View full text |Cite
|
Sign up to set email alerts
|

Secure and Flexible Monitoring of Virtual Machines

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

1
67
0

Year Published

2013
2013
2018
2018

Publication Types

Select...
7
1

Relationship

0
8

Authors

Journals

citations
Cited by 243 publications
(70 citation statements)
references
References 14 publications
1
67
0
Order By: Relevance
“…Hence, many studies exploit virtualization to provide application integrity but assume that the hypervisor is trusted [Keller et al 2010], [Hofmann et al 2011], [Azab et al 2009], [Xiong et al 2011]. This is the case of solutions based upon virtual machine introspection [Garfinkel and Rosenblum 2003] [Bryan D. Payne and Martim Carbone and Wenke Lee 2007] ], which check the memory of a VM for compromise, and rely on the data gathered from a introspection interface exported by the hypervisor itself. However, in these scenarios, should a hypervisor be compromised, either fake data might be returned by the introspection interface or, worst, other VMs resident on the same host might by attacked from the compromised hypervisor.…”
Section: Discussionmentioning
confidence: 99%
See 1 more Smart Citation
“…Hence, many studies exploit virtualization to provide application integrity but assume that the hypervisor is trusted [Keller et al 2010], [Hofmann et al 2011], [Azab et al 2009], [Xiong et al 2011]. This is the case of solutions based upon virtual machine introspection [Garfinkel and Rosenblum 2003] [Bryan D. Payne and Martim Carbone and Wenke Lee 2007] ], which check the memory of a VM for compromise, and rely on the data gathered from a introspection interface exported by the hypervisor itself. However, in these scenarios, should a hypervisor be compromised, either fake data might be returned by the introspection interface or, worst, other VMs resident on the same host might by attacked from the compromised hypervisor.…”
Section: Discussionmentioning
confidence: 99%
“…It is important to realize that such trust assumptions, as well as other security assumptions, are not fixed, but change in time owing to changes in the tech-nology and the discovery of new vulnerabilities amongst others. Threat models for virtualized systems have considerably evolved over the years, and, therefore, research solutions have also become increasingly sophisticated to cope with them [Garfinkel and Rosenblum 2003], [Bryan D. Payne and Martim Carbone and Wenke Lee 2007], ]. For example, early studies assumed the hypervisor of a remote host to be trusted, and used this assumption to build a trusted chain of enforcement [Keller et al 2010], [Hofmann et al 2011], [Azab et al 2009], [Xiong et al 2011].…”
Section: Introductionmentioning
confidence: 99%
“…The introspection of a paravirtualised guest VM is possible using libxc, a blktap driver and the xen store library . Xen_Access [13] is a good demonstration of memory and disk introspection with the Xen hypervisor. The introspection code remains safe, as it resides in a secure VM (Dom 0).…”
Section: Introspection Using Xen Librariesmentioning
confidence: 99%
“…It has already been shown [13,17] that VT microprocessor support features can be used for introspection activities. Useful information related to guest VM implementation can be retrieved by monitoring the VM control structure (VMCS) of the processor.…”
Section: Introspection Using Virtualization Supportmentioning
confidence: 99%
“…VMI is used in many researches to offload security systems to the outside of VMs. XenAccess [26] is a monitoring library for VMI and Lib-VMI [27] is an extended version of XenAccess. These libraries enable IDS applications on a Host OS to introspect the memory and disks of other VMs.…”
Section: Related Workmentioning
confidence: 99%