Trusted Launch for virtual machines
Trusted Launch is a security feature you can enable when creating Hyper-V Generation 2 VMs. It enables Secure Boot, installs a virtual Trusted Platform Module (vTPM), protects vTPM state at rest, and supports boot integrity verification (aka guest attestation).
We had earlier announced Trusted Launch for Virtual Machines (TVMs) for Windows Server Insiders – you were able to create and manage TVMs using PowerShell. We are excited to share a preview of Trusted launch support for virtual machines in Windows Admin Center Virtualization Mode (vMode). Using Windows Admin Center vMode, you can create and manage TVMs and view their boot integrity status.
Boot integrity verification
With boot integrity verification, boot measurements are verified by Microsoft Azure Attestation service. This helps detect any alterations to boot path or boot components. Such alterations, e.g. implanting malware in the boot path, can be detected by boot integrity verification. Starting with this preview, you can view VM boot integrity status via Windows Admin Center vMode.
Increasingly attackers prefer implanting malware in the boot path for a variety of reasons: the OS layer is usually well protected, while firmware – as highly privileged code – can be used to alter what gets loaded (e.g., boot loader and drivers). Such alterations are not easily detectable by anti-virus software running at the OS layer. Boot integrity verification or guest attestation is an important part of establishing trust by verifying that the VM started in a healthy way.
Boot integrity verification is performed periodically about every 8 hours, and it verifies boot integrity of the most recent VM start. This also protects against attacks that disable reporting from the VM.
What’s supported
TVMs are available for preview starting with Windows Server Insider preview build 29621. This preview supports some Trusted Launch capabilities: Secure boot, vTPM, vTPM state protection (at rest), and boot integrity verification.
Not supported in this release:
- Moving TVMs to another server.
- TVMs in failover clusters or Hyper-V Replica.
Preview instructions
At a high level, the steps involve:
- Install Windows Server Insider preview build on your server
- Setup Windows Admin Center vMode
- Enable Trusted Launch feature on server
- Setup guest attestation on server
- Create Trusted Launch virtual machine
- Enable guest attestation on the VM
- View attestation status
1. Install Windows Server Insider preview build
Trusted Launch for virtual machines is available starting with the Windows Insider preview build number 29621. Install this build or a later build on your server. (Join Windows Server Insiders if you haven’t already!)
2. Setup Windows Admin Center vMode
Download and install the latest Windows Admin Center vMode on a dedicated vMode gateway machine (separate from the server machine you created in step 1 above).
After installation finishes, check the box to Start Windows Admin Center, then select Finish. Then, sign in as an administrator to start using Windows Admin Center.
On top right corner, click on Settings, and then choose Advanced (under Development on the left pane). Add Experiment key “msft.sme.hyperv.tvmGuestAttestation”.
Create a resource group in Windows Admin Center vMode and add your server machine (host) to the resource group. You can now manage your server from vMode.
Download attestation client from here(please sign up for our NDA program https://aka.ms/joinWACNDA for access). Copy the folder “IsolatedVmGuestAttestation” to “C:\Program Files” on the server host (not the WAC gateway machine). This is required before enabling the Trusted launch feature below.
3. Enable Trusted Launch feature
In the Settings for your server, choose “Isolated guest” and click “Enable”. This installs the Trusted Launch feature.
4. Setup guest attestation on server
To verify boot integrity of Trusted Launch virtual machines, you will need to set up the server with an attestation service provider and configure the attestation service provider with an attestation policy.
First construct the attestation policy.
Query the registry on the server to obtain AK root certificate information. Copy the printed value.
Get-ItemPropertyValue -Path 'HKLM:\SOFTWARE\Microsoft\AszIGVmAgent' -Name 'ActiveAkRoot'
In the policy below, substitute the text <AKRoot> with the value obtained from the registry.
version=1.2;
configurationrules
{
=> issueproperty(type = "aik_trusted_root_certs", value ="-----BEGIN CERTIFICATE-----<AKRoot>-----END CERTIFICATE-----");
};
authorizationrules
{
[type=="x-ms-azurevm-default-securebootkeysvalidated", value==false] => deny();
[type=="x-ms-azurevm-debuggersdisabled", value==false] => deny();
=> permit();
};
issuancerules
{
};
After substitution, the policy would look like, for instance:
version=1.2;
configurationrules
{
=> issueproperty(type = "aik_trusted_root_certs", value ="-----BEGIN CERTIFICATE----- ExampleOutputABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVEnd==-----END CERTIFICATE-----");
};
authorizationrules
{
[type=="x-ms-azurevm-default-securebootkeysvalidated", value==false] => deny();
[type=="x-ms-azurevm-debuggersdisabled", value==false] => deny();
=> permit();
};
issuancerules
{
};
We will use the above text as the attestation policy later.
Create an attestation service provider using instructions at Quickstart: Set up Azure Attestation by using the Azure portal | Microsoft Learn. As shown in the example below, you can view the attestation provider resource. Note the Attest URI - you will need it later.
Click on “Attestation policy” to configure an attestation policy for the attestation provider you created. Choose “Attestation type” as “AzureVM”. When configuring the attestation policy, use the attestation policy text you created earlier.
Enable guest attestation on the server as shown below and provide the Attest URI for the attestation service provider you created earlier.
5. Create Trusted Launch virtual machine
Choose “Virtual machines” under Tools on the left pane. Then, click on “Add” to create a new virtual machine. Choose Security Type as Trusted Launch. Choose an available Virtual Switch for network connectivity.
On the server, run “(Get-VM -name <VMName>).GuestStateIsolationType”.
It should return "TrustedLaunch".
6. Enable guest attestation on the VM
Enable guest attestation for the VM as shown below.
Provide the administrator username and password for the virtual machine. This will allow installing the guest attestation client in the virtual machine.
If successful, you will see a toast notification as shown below indicating successful enablement of guest attestation.
Note: Once enabled, it will take a few minutes for the attestation status to appear as shown in the next step below.
7. View attestation status
The attestation status will appear as shown below.
Note: The attestation status will refresh periodically about every 8 hours and will verify boot integrity of the most recent VM start.
Call to action
Trusted Launch brings foundational VM security — Secure Boot, a vTPM, and protected guest state — to Windows Server, helping safeguard your VMs against boot-level and firmware threats. Please try out TVMs and provide your feedback via the Windows Server Insiders Forum.