Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Virtualisation security covers the whole virtual estate: the management plane that controls every workload, the virtual machine lifecycle, snapshots and templates, east-west traffic, and backup isolation.

What Is Virtualisation Security?
Virtualisation changed how infrastructure is built and, less visibly, where its security boundaries sit. A single console creates, clones, moves, and deletes workloads. A file on a datastore is an entire server. A snapshot taken for a maintenance window holds the memory contents of a running domain controller. Virtualisation security is the practice of managing that estate as a system, rather than treating each guest as though it were still a separate box in a rack.
This note covers the estate. The isolation layer itself, including escape vulnerabilities and host hardening, is covered separately under hypervisor security.
Whoever controls vCenter, System Center, or the cloud management API controls every workload beneath it. They can clone a server and mount its disk elsewhere, export a virtual machine wholesale, revert a system to an earlier state to undo evidence, or delete the lot. No in-guest control has any bearing on these actions, because they happen at a layer below the guest operating system.
Treat management as a tier zero system, with the same protection as a domain controller: separate administrative accounts that are not used for anything else, multi-factor authentication, access only from privileged access workstations, a management network that is not routable from user subnets, and alerting on role assignment changes, mass clone operations, and snapshot deletion. In 2024, attackers exploited CVE-2024-37085 to gain administrative control of ESXi hosts simply by creating an Active Directory group with a particular name, which is a useful reminder that the dependency between directory and virtual estate deserves scrutiny.
Virtual machine sprawl is a security problem rather than a capacity one. Machines created for a project and never decommissioned stay on the network, drop out of patching, and keep valid credentials. Enforce a lifecycle with ownership, an expiry date, and automated reporting of guests missing from your patch management or EDR coverage.
Templates propagate whatever they contain. A hardened, current template produces hardened, current servers; one with an embedded local administrator password produces several hundred machines sharing it. Rebuild templates on a schedule rather than patching them in place, and scan them for secrets before publication.
Snapshots deserve particular care. A snapshot with memory state contains credentials, keys, and decrypted data, and it can be copied by anyone with datastore access without touching the running guest. Restrict who may create and download them, set retention limits, and encrypt the datastore where regulated data is processed.
Two virtual machines on the same host communicating over the same virtual switch generate traffic that never reaches a physical network device. Traditional network monitoring and firewalls see none of it, which is why so many estates have strong north-south control and nothing between workloads.
Micro-segmentation addresses this by enforcing policy at the virtual network interface, through products such as NSX, through cloud security groups, or through host firewalls managed centrally. Start with the obvious rules, such as preventing application servers from initiating connections to each other and restricting management protocols to administrative sources, and extend from there. Pair it with virtual switch hardening: reject promiscuous mode, MAC address changes, and forged transmits, and keep management, storage, and guest traffic on separate VLANs.
Ransomware groups target virtual estates because the leverage is extraordinary. Encrypting datastores on a handful of hosts takes out hundreds of servers in one action, and in-guest backup agents are useless once the underlying storage is gone. The ESXiArgs campaign of February 2023 compromised thousands of internet-exposed hosts through a vulnerability that had been patched two years earlier.
The defences are specific. Keep an immutable copy of backups outside the virtual estate, so the backup system cannot be deleted by the same credentials that control the hypervisors. Verify restoration of a full host, not just of individual files. Separate the backup system’s identity plane from the production directory. And test the recovery runbook against the scenario where the management console itself is unavailable.
Inventory every host, guest, template, and snapshot, including the ones nobody claims. Isolate management interfaces. Apply a hardening guide, whether the vendor security configuration guide or the relevant CIS Benchmark. Get hypervisor and management logs into your SIEM. Then prove that backups restore without the virtual estate being available.
Our Infrastructure and Architecture Review Services assess virtual estates end to end, from management plane exposure through segmentation to backup isolation, because an attacker who reaches one of those usually reaches all three.
Hypervisor security concerns the isolation layer itself: its attack surface, escape vulnerabilities, and host configuration. Virtualisation security is the wider programme covering the management plane, virtual machine lifecycle, templates, snapshots, east-west network policy, and backup isolation. Most real incidents involve the wider estate rather than a hypervisor escape, which makes the broader view the more urgent one.
A snapshot that includes memory state captures everything the running system held, including credentials, encryption keys, and decrypted data. It is a file on a datastore, so anyone with storage access can copy it without touching the guest or triggering in-guest logging. Restrict who may create and export snapshots, limit retention, and encrypt datastores holding regulated workloads.
Traffic between guests on the same host never leaves the virtual switch, so physical network tooling cannot see it. Options are port mirroring from the virtual switch to a collector, a distributed firewall that enforces and logs policy at each virtual interface, or host-based firewalls managed centrally with their logs forwarded. Most estates get further faster with enforcement than with inspection.
Yes. A guest operating system faces the same threats as a physical one, and compromise of a guest is the usual starting point for reaching the management plane. Use agents designed for virtual environments to avoid scan storms, and make sure template images include the agent so that newly provisioned machines are covered from first boot rather than from the next inventory sweep.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.