Deploy the sensitive workload as a Generation 2 shielded VM on a guarded fabric, because this combines BitLocker-backed disk protection, host authorization, and restrictions on host-level administration rather than relying only on VHDX file permissions.^1^
Controls for each threat
| Threat |
Required protection |
| Copy and mount the VHD/VHDX |
Encrypt the guest OS and data volumes with BitLocker using the VM’s virtual TPM (vTPM). Copying the file then does not expose its encrypted contents without the keys. |
| Copy and register it on another Hyper-V host |
Use a shielded VM with Host Guardian Service (HGS). HGS releases keys only to authorized, attested hosts, so merely copying and registering the VM is insufficient to start it. |
| Open the local VM console with another account |
For ordinary VMs, restrict host membership and per-VM VMConnect permissions. For stronger protection against host/fabric administrators, use shielding and remote access controlled inside the guest. |
A normal VHDX is only a file; anyone who can copy it can potentially attach it or create another VM around it. NTFS permissions protect access while the file remains on that storage system, but do not remain an effective security boundary after an authorized or privileged user copies it.
Recommended deployment
- Use a Generation 2 VM.
Generation 2 supports Secure Boot and vTPM. Secure Boot is enabled by default and prevents untrusted boot components from loading.^2^
- Enable vTPM and encrypt the guest disks with BitLocker.
Encrypt the OS volume and every data volume containing sensitive information. Shielded VMs automatically protect the OS disk, but attached data drives must also be encrypted if their contents require protection.^1^
- For multiple hosts or protection from host administrators, deploy a guarded fabric.
Its principal components are:
- Host Guardian Service, normally deployed as a three-node cluster.
- One or more guarded Hyper-V hosts.
- Generation 2 shielded VMs.
HGS performs host attestation and key protection. Only an approved host receives the keys needed to start or live-migrate the VM. TPM-trusted attestation provides the strongest assurance and requires TPM 2.0, UEFI 2.3.1, and Secure Boot; host-key attestation is available where TPM 2.0 is unavailable.^1^
- Choose
Shielded, not merely Encryption Supported, when host administrators are outside the trust boundary.
Encryption Supported protects data at rest and in transit but leaves management conveniences under fabric-administrator control. Shielded enforces Secure Boot, vTPM, state and migration encryption, and additional management restrictions.^3^
A shielded VM can be configured locally without HGS, but moving it can prevent it from starting until its Key Protector authorizes the destination host. For enterprise or multi-host enforcement, use HGS rather than treating local shielding as equivalent to guarded-fabric attestation.^2^
Restrict console access
For ordinary or encryption-supported VMs:
- Remove unnecessary users from the local Administrators and Hyper-V Administrators groups. Users managing VMs should not automatically receive permissions on the host operating system.^4^
- Review explicit per-VM console grants:
Get-VMConnectAccess -VMName "SensitiveVM"
This lists users granted VMConnect access to that VM.^5^
- Revoke an unnecessary explicit grant:
Revoke-VMConnectAccess `
-VMName "SensitiveVM" `
-UserName "CONTOSO\UnapprovedUser" `
-Confirm
This changes console authorization, so test with the approved administration account before ending the current session.^6^
These permissions do not protect an ordinary VM from a trusted host administrator who can change permissions or access its files. Shielding is the control intended when fabric administrators or compromised host software are part of the threat model. Console behavior also varies by shielded-VM host version, so do not use “console unavailable” as the sole protection; encryption and host attestation remain the security boundaries.^1^
Host and storage hardening
- Store VM configuration, checkpoint, and VHDX files in a secured location.
- Apply restrictive NTFS/share permissions and secure the underlying storage.
- Enable BitLocker on the host storage as an additional defense against physical disk theft.
- Use dedicated secure networks for management, live migration, and storage; use SMB 3 encryption where storage migration crosses an untrusted network.
- Keep the Hyper-V host minimal, patched, and remotely administered.^4^
Host-volume BitLocker protects stolen physical media, while guest BitLocker plus vTPM protects the copied VHDX. They address different theft scenarios and are complementary.
References
- Guarded fabric and shielded VMs overview
- Hyper-V generation 2 virtual machine security features
- Scenario - Deploy guarded hosts and shielded virtual machines in VMM
- Plan for Hyper-V security in Windows Server
- Get-VMConnectAccess-Syntax
- Revoke-VMConnectAccess-Description