Premium Content

Access "Ensuring virtual machine security"

Danielle Ruest and Nelson Ruest, Contributors Published: 15 Oct 2012
Keeping virtual machines secure

This article is part of the August 2011, Vol. 34 issue of Keeping virtual machines secure

When preparing a server for production, you usually run the server through a series of processes and procedures that are designed to keep it secure. So how should you proceed when it’s time to secure virtual machines (VMs) as opposed to physical servers? This tip covers a few caveats for virtual machine security. The first set of caveats applies to the host server environment, and the second applies to the VMs themselves. Protecting host servers A virtual machine environment always consists of at least two environments: the host server environment, often referred to as the resource pool, and a production environment, which is maintained by VMs. There may be other environments—training, development, testing and more—but the first two are the most common. As a rule, you should always segregate the host environment from any VM environment (see Figure 1). This provides an initial layer of protection for all VMs. Figure 1. Segregating the resource pool from VM environments The resource pool should be linked to a resource directory service—one that is apart from ... Access >>>

Access TechTarget
Premium Content for Free.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Already a member? Login to access this content.

What's Inside

Features

More Premium Content Accessible For Free

Back to top