So if, for example, you create a Vercrypt standard volume (as a file) and save data within that container, utilizing good solid password and encryption practices, that data will be secure from attacks based upon any data found in the Hypervisor logs and conf files. Hypervisors do not concern themselves with the state of the data itself, only the storage medium as it relates to its hardware state. So Hypervisors track, and log only the data needed to accommodate hardware and software state change. That is certainly not the case as it would be an enormous waste of valuable disk space. If that were the case, the configuration and log files the hypervisor uses would be at least the same size as the guest OS and data files. You can determine the level of security you have with Veracrypt (or any other encryption software) within a Virtual Machine, by using logical deduction, and considering (realistically) what hypervisor data files are modified by the Hypervisor when data is accessed and/or written to and from, when a storage device within a Hypervisor guest is modified.Ĭonsider, that contrary to popular belief, not every user/system action that occurs is recorded by the hypervisor.

What is virtualbox encryption