Harley Stagner contributes the following article and information to TechTarget's SearchServerVirtualization Web site.  This is part one of a multi-part article, designed to help you with your Microsoft Virtual Server security.  In part one, he describes securing Virtual Server's configuration files, virtual machine configuration files and virtual machine resource files.

Do you need to secure a Microsoft Virtual Server 2005 installation? This article will walk you through securing local access to the Virtual Server 2005 host machine and the virtual machines hosted on it.

Best practices regarding physical servers usually dictate that the servers should be locked in a server room and BIOS-level console access should be restricted to only a few administrators. This concept is not much different when dealing with virtual machines (VMs). The host computer that is running Microsoft Virtual Server 2005 should be locked in the server room. By default, this means that the VMs running on it are locked in the server room. However, BIOS-level console access to VMs can be achieved from anywhere with a network connection to the host machine. This makes securing console access to a VM slightly more involved than locking the physical host machine in the server room. Of course, you could always choose to disconnect the Microsoft Virtual Server 2005 host machine from the network, but then the server could only be used by the systems administrator that is locked in the server room with it. Locking systems administrators in the server room is not considered best practice and we usually want other departments to be able to use our Virtual Server host machine anyway. So, we have no choice but to follow some guidelines in order to secure our virtual machines.

Read the entire part one article, here.