ATTENTION: The new home of the Digital Forensics Wiki is at https://forensicswiki.xyz/. Yeah, it's a silly name, but it was cheap.
This wiki will be going offline permanently in the near future. An exact date will be announced soon. Thank you for being a part of this community.
If you wish to work on the new forensicswiki, please join the Google Group forensicswiki-reborn
Difference between revisions of "Forensics of Virtualization Products"
m (moved VirtualMachineForensics to Forensics of Virtualization Products: The title can easily refer to using virtualization in your forensics practice.)
Latest revision as of 17:10, 23 March 2012
Dealing with Virtual Machine Images
It is becoming increasingly common to find evidence drives with Virtual Machines (VM) on them. The VMs may contain evidence of their own, but with their unique file structure, care must be taken during examination. Running the virtual machine could destroy artifacts that are important.
There are two methods for creating a way to mount or inspect a Virtual Box VM. Virtual Box disks typically have the extension "vdi" for Virtual Desktop Infrastructure. The mount method requires a Linux system and "qemu". The other method converts a vdi to a raw image format which can then be inspected with traditional forensics tools.
- Install qemu-kvm using your preferred installation tool (apt-get, etc)
- Load the network block device module >sudo modprobe nbd
- Use Qemu to load the VDI file as a loop back device >sudo qemu-nbd -c /dev/nbd0 infile.vdi
- Mount >sudo mount /dev/nbd0p1 /mnt
- Inspect the file system as needed
- >sudo umount /mnt
- >qemu-nbd -d /dev/nbd0
Conversion requires the Virtual Box tool kit, if you don't already have it.
- Install virtualbox-ose using your preferred installation tool (apt-get, download from VirtualBox.org, etc)
- Convert to raw format >VBoxManage internalcommands converttoraw infile.vdi outfile.img
- Inspect the raw image as per usual, either with TSK, EnCase, or mount