Using VirtualBox Virtual Machines
With REVEN, you can build RE projects where analyzed scenarios are recorded from Virtual Machines (VMs) running in Oracle VM VirtualBox.
This section describes how to setup a VirtualBox VM that will be suitable for scenario recording.
IMPORTANT: Replaying scenarios recorded with a VirtualBox VM in REVEN will often lead to partial replays due to replay desynchronization errors. Therefore, using QEMU VMs is highly recommended and must be preferred. However, using VirtualBox VMs may prove successful in some rare cases where using QEMU VMs is not convenient or fails.
IMPORTANT: REVEN currently provides the analysis of scenarios with VirtualBox VMs only on servers equipped with Intel processors. It does not support such analysis on servers equipped with AMD processors.
IMPORTANT: The autorecord features of the Project Manager are not supported with VirtualBox VMs. With REVEN Enterprise edition, the ASM stub autorecord feature is available from the Workflow Python API.
VirtualBox is installed on the REVEN server during the REVEN installation process.
Should you need some advanced system configuration, such as
dedicating a USB device to a VM, you will have to manually add the Linux
user running REVEN to the Linux group
vboxusers. If reven_user is the user
login, this can be done using the command line:
$ sudo adduser reven_user vboxusers
Managing remotely a VirtualBox machine may be done through a SSH connection with X-Forwarding enabled or with solutions such as phpVirtualbox or remotebox. We will not document them here.
Creating a VirtualBox VM for scenario recording
- Create a virtual machine in Oracle VM VirtualBox Manager. Please refer to VirtualBox's online documentation.
- Add an IDE adapter to the VM configuration (or make sure it exists). This can be done through the Storage section of the virtual machine settings:
- Set the IDE adapter name to
- Set it as CD-ROM / primary master device.
- Setup the
Systemsettings as follows:
- In the
Processortab, set the number of processors to 1.
- In the
- Set the
Paravirtualization interfaceto None.
- Check all boxes of
- Set the
- Setup the
Audiosettings either disabled, or enabled with the ICH AC97 audio controler selected. Otherwise, the Virtual Machine may not start.
- Install the Microsoft Windows or Linux guest OS of your choice on the virtual machine.
WARNING: Make sure to remove any software that may communicate with
the VirtualBox hypervisor from the guest. Intrusive software such as
Guest additions (which provides extended features like drag
and drop, clipboard sharing and full resolution display) may lead to unhandled
hypervisor behavior, and the recorded scenario will not be properly handled
What you must know
VirtualBox saves states of a VM in Snapshots. Technically, there are Disk snapshots and Live snapshots.
Disk snapshots are saved while a VM is off, or by taking a snapshot on a running VM and discarding saved state.
Live snapshots are obtained by shutting down a VM and choosing Save state, or when you take a snapshot on a running VM.
For a given VM, REVEN's Project Manager will show you a single list of VirtualBox snapshots to record scenarios from.
Preparing VirtualBox snapshots to use with REVEN
We recommend the following approach to prepare a VirtualBox snapshot that will be used to record a scenario.
In the VirtualBox GUI:
- Create and setup the VirtualBox VM.
- Install software & configuration required by your scenario in the VM.
- Run operations required in the VM before the scenario recording, but that need not be recorded.
- Take a snapshot of the VM.
- Shutdown the VM.
In the REVEN Project Manager:
- If the VM has previously been registered, simply refresh the list of snapshots for the VM.
- If the VM has not been registered yet, simply register it. Its snapshots will be automatically known by the Project Manager.