You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Learn how to configure Virtual Machines - Virtual Trusted Platform Module (vTPM).
4
4
ms.topic: how-to
5
5
ms.service: azure-vmware
6
-
ms.date: 12/05/2024
6
+
ms.date: 12/06/2024
7
7
ms.custom: engagement-fy25
8
8
---
9
9
@@ -13,22 +13,15 @@ This article demonstrates how to enable the virtual Trusted Platform Module (vTP
13
13
14
14
A virtual Trusted Platform Module (vTPM) in VMware vSphere is a virtual counterpart of a physical TPM 2.0 chip, utilizing VM Encryption. It provides the same functionalities as a physical TPM but operates within VMs. Each VM can have its own unique and isolated vTPM, which helps secure sensitive information and maintain system integrity. This setting enables VMs to apply security features like BitLocker disk encryption and authenticate virtual hardware devices, creating a more secure virtual environment.
15
15
16
-
## Prerequisites
17
-
18
-
Before configuring vTPM on a VM in Azure VMware Solution, ensure the following prerequisites are met:
19
-
20
-
- The virtual machine must use EFI firmware.
21
-
- The virtual machine must be at hardware version 14 or later.
22
-
- Guest OS support: Linux, Windows Server 2008 and later, Windows 7 and later.
23
-
24
-
>[!IMPORTANT]
25
-
>Customers do not need to configure a key provider to use vTPM with Azure VMware Solution. Azure VMware Solution already provides and manages key providers for each environment.
16
+
## Background
26
17
27
-
## Trusted Launch for Azure VMware Solution
18
+
###Trusted Launch for Azure VMware Solution
28
19
29
20
Trusted Launch is a comprehensive security solution that encompasses three key components: Secure Boot, Virtual Trusted Platform Module (vTPM), and Virtualization-based security (VBS). Each of these components plays a vital role in fortifying the security posture of VMs.
30
21
31
-
## Benefits
22
+
:::image type="content" source="./media/trusted-launch.png" alt-text="Diagram showing the three pillars of trusted launch, Secure Boot, Virtual Trusted Platform Module, and Virtualization-based Security." border="false" lightbox="./media/trusted-launch.png":::
23
+
24
+
### Benefits
32
25
33
26
• Securely deploy VMs with verified boot loaders, operating system (OS) kernels, and drivers.
34
27
@@ -42,13 +35,24 @@ Trusted Launch is a comprehensive security solution that encompasses three key c
42
35
43
36
Secure Boot is the first line of defense in Trusted Launch. It establishes a "root of trust" for VMs by ensuring that only signed operating systems and drivers are allowed to boot. This prevents the installation of malware-based rootkits and bootkits, which can compromise the security of the entire system. With Secure Boot enabled, every aspect of the boot process, from the boot loader to the kernel and kernel drivers, must be digitally signed by trusted publishers. This creates a robust shield against unauthorized modifications and ensures that the VM starts in a secure and trusted state.
44
37
45
-
## Virtual Trusted Platform Module (vTPM)
38
+
###Virtual Trusted Platform Module (vTPM)
46
39
47
40
The vTPM is a virtualized version of a hardware Trusted Platform Module (TPM) 2.0 device. It serves as a dedicated secure vault for storing keys, certificates, and secrets. What sets vTPM apart is its ability to operate in a secure environment outside the reach of any VM, making it tamper-resistant and highly secure. One of the key functions of vTPM is attestation. It measures the entire boot chain of a VM, including UEFI, OS, system components, and drivers, to certify that the VM booted securely. This attestation mechanism is invaluable for verifying the integrity of VMs and ensuring that they haven't been compromised.
48
41
49
-
## Virtualization-based Security (VBS)
42
+
###Virtualization-based Security (VBS)
50
43
51
-
VBS is the final piece of the Trusted Launch puzzle. It leverages the hypervisor to create isolated, secure memory regions within the VM. VBS uses virtualization to enhance system security by creating an isolated, hypervisor-restricted, specialized subsystem. It provides protection against unauthorized access of credential, prevents malware from running on windows system and ensures only trusted code runs from bootloader onwards.
44
+
Virtualization-based Security (VBS) is the final piece of the Trusted Launch puzzle. It leverages the hypervisor to create isolated, secure memory regions within the VM. VBS uses virtualization to enhance system security by creating an isolated, hypervisor-restricted, specialized subsystem. It provides protection against unauthorized access of credential, prevents malware from running on windows system and ensures only trusted code runs from bootloader onwards.
45
+
46
+
## Prerequisites
47
+
48
+
Before configuring vTPM on a VM in Azure VMware Solution, ensure the following prerequisites are met:
49
+
50
+
- The virtual machine must use EFI firmware.
51
+
- The virtual machine must be at hardware version 14 or later.
52
+
- Guest OS support: Linux, Windows Server 2008 and later, Windows 7 and later.
53
+
54
+
>[!IMPORTANT]
55
+
>Customers do not need to configure a key provider to use vTPM with Azure VMware Solution. Azure VMware Solution already provides and manages key providers for each environment.
52
56
53
57
## How to Configure vTPM
54
58
@@ -72,6 +76,7 @@ To configure vTPM on a VM in Azure VMware Solution, follow these steps:
72
76
Migration of VMs with vTPM might not be supported by some tools. Check the documentation of the migration tool. If it isn't supported, you can follow VMware documentation to safely disable vTPM and re-enable it post-migration.
73
77
74
78
## More information
79
+
75
80
[Securing Virtual Machines with Virtual Trusted Platform Module](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-A43B6914-E5F9-4CB1-9277-448AC9C467FB.html)
76
81
77
82
[What Is a Virtual Trusted Platform Module](https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-security/GUID-6F811A7A-D58B-47B4-84B4-73391D55C268.html)
0 commit comments