Virtual machine introspection
 | This article, Virtual machine introspection, has recently been created via the Articles for creation process. Please check to see if the reviewer has accidentally left this template after accepting the draft and take appropriate action as necessary.
Reviewer tools: Inform author |
Comment: We need a stronger emphasis on the best relevant sources to help enhance the article here. SwisterTwister talk 05:18, 26 October 2017 (UTC)
Template:New unreviewed article
Virtual machine introspection (VMI) is a technique "for monitoring the runtime state of a system-level virtual machine (VM)", which is helpful for debugging or forensic analysis.[1][2]
Term introspection in application to the virtual machines was introduced by Garfinkel and Rosenblum[3]. They invented an approach for "protecting a security application from attack by malicious software" and called it VMI. Now VMI is a common term for a set of forensic and analysis methods. VMI-based approaches are widely used for security applications, software debugging, and systems management[4].
VMI tools may be located inside or outside the virtual machine and act by tracking the events (interrupts, memory writes, and so on) or sending the requests to the virtual machine. Virtual machine monitor usually provides low-level information like raw bytes of the memory. Converting this low-level view into something meaningful for the user is known as the semantic gap problem. Solving this problem requires analysis and understanding of the systems being monitored.
VMI within the virtual machine
Programs running inside VM may provide information about other processes. This information may be sent through network interface or some virtual devices like serial port. The examples of in vivo introspection programs are WinDbg[5] or GDB[6] servers that interact with the remote debugger.
The drawback of this approach is that it requires functioning OS within the VM. If OS hangs or isn't loaded yet, the introspection agent couldn't work.
VMI outside the virtual machine
VMI tools may be implemented within the virtual machine monitor[7] or as a separate programs[8] that capture information (e.g., contents of the memory) from the virtual machine monitor. Then this data has to be interpreted to understand the processes in the system. One of the popular tools for such interpretation is Volatility framework[9]. This framework contains profiles for many popular operating systems and may extract different information like process tree or list of the kernel objects.
References
- ^ https://github.com/libvmi/libvmi
- ^ https://link.springer.com/referenceworkentry/10.1007%2F978-1-4419-5906-5_647 Encyclopedia of Cryptography and Security: Virtual Machine Introspection
- ^ https://suif.stanford.edu/papers/vmi-ndss03.pdf
- ^ https://link.springer.com/referenceworkentry/10.1007%2F978-1-4419-5906-5_647 Encyclopedia of Cryptography and Security: Virtual Machine Introspection
- ^ https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/remode-debugging-using-windbg
- ^ https://sourceware.org/gdb/onlinedocs/gdb/Server.html
- ^ https://wiki.xenproject.org/wiki/Virtual_Machine_Introspection VMI in Xen
- ^ https://github.com/Cisco-Talos/pyrebox
- ^ https://github.com/volatilityfoundation/volatility