The second revolves around inter-VM communications, and an area where we believe real risk resides. It should be noted that VMs themselves are no less secure than their physical counterparts, but there are several areas of risk with which to be concerned, including:

• VM sprawl – VMs are so simple to create that many virtualized data centers suffer from VM sprawl. If VMs are created from unpatched images, known vulnerabilities can be exploited.
• Inter-VM attacks – Each physical host has a “soft-switch” to enable VMs to communicate with one another. Because inter-VM communications do not always leave the physical host, they are unprotected by firewalls and other hardware-based protection. In the event a VM is compromised, it can attack other VMs on the same host without detection from existing tools.
• Migration of VMs – Some server virtualization packages enable VMs to be migrated while running to different physical hosts. In the event security solutions are not designed to support hot or cold VM migration, policy may cease to protect the VM. Alternatively, the VM may become inaccessible and cause system outages.

Many vendors offer a silo approach to security, offering separate solutions for physical and virtual machines. Security administrators should be cautious of these wares, as they add incremental management tools and can introduce incompatibility.

A more effective option is to leverage cross-platform virtual security solutions. These solutions are designed to support mixed physical/virtual data centers – a reality for many businesses. These software-based solutions offer a centralized management view to simplify policy enforcement. They also ensure policy persistence in the event a physical or virtual machine is migrated to another physical host, or to another location in the builder. Because cross-platform virtual security solutions are based on software, they protect machines regardless of their physical location, directly addressing the threats introduced by VM sprawl, inter-VM communications and migration.


What should an administrator take into consideration before deploying server virtualization in the enterprise?

Administrators should follow two practices to help mitigate the security risks associated with server virtualization. First, administrators should ensure that virtualization projects follow at least the same processes and procedures as are in place for traditional servers and PCs. This will ensure that new servers are not commissioned without reason and without the “correct” software and access controls being set. Second, investigate solutions that offer cross-platform virtual security to ensure that a centrally-managed security mechanism stays persistent as virtual and physical machines move across a mixed data center. By following core security procedures and protecting against inter-VM communications with cross-platform virtual security, administrators will be well covered.

A number of vulnerabilities have been discovered in virtualization software yet there have not been serious attacks to date. In your opinion, can we expect real problems in the near future?

Software is software. To say there will never be any real problems is to be naïve. That being said, hypervisors offer very small attack surface areas because they have far fewer lines of code to attack. At some point you’ll probably have vulnerability, but if you put that in context with the real threats out there, with regard to inter-VM communications, you’re far better off to focus on the latter.