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
Copy file name to clipboardExpand all lines: articles/virtual-machines/boot-integrity-monitoring-overview.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,16 +13,16 @@ ms.custom: template-concept
13
13
14
14
# Boot integrity monitoring overview
15
15
16
-
To help Trusted launch better prevent malicious rootkit attacks on virtual machines (VMs), guest attestation through an Azure Attestation endpoint is used to monitor the boot sequence integrity. This attestation is critical to provide the validity of a platform's states.
16
+
To help Trusted Launch better prevent malicious rootkit attacks on virtual machines (VMs), guest attestation through an Azure Attestation endpoint is used to monitor the boot sequence integrity. This attestation is critical to provide the validity of a platform's states.
17
17
18
-
Your [Azure trusted VM](trusted-launch.md) needs Secure Boot and virtual Trusted Platform Module (vTPM) enabled and attestation extensions installed. Then Microsoft Defender for Cloud verifies that the status and boot integrity of your VM is set up correctly. To learn more about Microsoft Defender for Cloud integration, see [Trusted launch integration with Microsoft Defender for Cloud](trusted-launch.md#microsoft-defender-for-cloud-integration).
18
+
Your [Azure trusted VM](trusted-launch.md) needs Secure Boot and virtual Trusted Platform Module (vTPM) to be enabled so that the attestation extensions can be installed. Microsoft Defender for Cloud offers reports based on Guest Attestation verifying status and that the boot integrity of your VM is set up correctly. To learn more about Microsoft Defender for Cloud integration, see [Trusted Launch integration with Microsoft Defender for Cloud](trusted-launch.md#microsoft-defender-for-cloud-integration).
19
19
20
20
> [!IMPORTANT]
21
21
> Automatic Extension Upgrade is now available for the Boot Integrity Monitoring - Guest Attestation extension. For more information, see [Automatic Extension Upgrade](automatic-extension-upgrade.md).
22
22
23
23
## Prerequisites
24
24
25
-
You need an active Azure subscription and a Trusted launch VM.
25
+
You need an active Azure subscription and a Trusted Launch VM.
26
26
27
27
## Enable integrity monitoring
28
28
@@ -44,7 +44,7 @@ This action installs the Guest Attestation extension, which you can refer to via
44
44
45
45
### [Template](#tab/template)
46
46
47
-
You can deploy the Guest Attestation extension for Trusted launch VMs by using a quickstart template.
47
+
You can deploy the Guest Attestation extension for Trusted Launch VMs by using a quickstart template.
48
48
49
49
#### Windows
50
50
@@ -119,7 +119,7 @@ You can deploy the Guest Attestation extension for Trusted launch VMs by using a
119
119
120
120
### [CLI](#tab/cli)
121
121
122
-
1. Create a VM with Trusted launch that has Secure Boot and vTPM capabilities through initial deployment of a Trusted launch VM. To deploy the Guest Attestation extension, use `--enable-integrity-monitoring`. As the VM owner, you can customize VM configuration by using `az vm create`.
122
+
1. Create a VM with Trusted Launch that has Secure Boot and vTPM capabilities through initial deployment of a Trusted Launch VM. To deploy the Guest Attestation extension, use `--enable-integrity-monitoring`. As the VM owner, you can customize VM configuration by using `az vm create`.
123
123
1. For existing VMs, you can enable boot integrity monitoring settings by updating to make sure that integrity monitoring is turned on. You can use `--enable-integrity-monitoring`.
124
124
125
125
> [!NOTE]
@@ -129,10 +129,10 @@ You can deploy the Guest Attestation extension for Trusted launch VMs by using a
129
129
130
130
If Secure Boot and vTPM are set to **ON**, then boot integrity is also set to **ON**.
131
131
132
-
1. Create a VM with Trusted launch that has Secure Boot and vTPM capabilities through initial deployment of a Trusted launch VM. As the VM owner, you can customize VM configuration.
132
+
1. Create a VM with Trusted Launch that has Secure Boot and vTPM capabilities through initial deployment of a Trusted Launch VM. As the VM owner, you can customize VM configuration.
133
133
1. For existing VMs, you can enable boot integrity monitoring settings by updating. Make sure that both Secure Boot and vTPM are set to **ON**.
134
134
135
-
For more information on creating or updating a VM to include boot integrity monitoring through the Guest Attestation extension, see [Deploy a VM with Trusted launch enabled (PowerShell)](trusted-launch-portal.md#deploy-a-trusted-launch-vm).
135
+
For more information on creating or updating a VM to include boot integrity monitoring through the Guest Attestation extension, see [Deploy a VM with Trusted Launch enabled (PowerShell)](trusted-launch-portal.md#deploy-a-trusted-launch-vm).
136
136
137
137
---
138
138
@@ -148,7 +148,7 @@ The Azure Attestation extension won't work properly when you set up a network se
148
148
149
149
### Solutions
150
150
151
-
In Azure, NSGs are used to help filter network traffic between Azure resources. NSGs contain security rules that either allow or deny inbound network traffic, or outbound network traffic from several types of Azure resources. The Azure Attestation endpoint should be able to communicate with the Guest Attestation extension. Without this endpoint, Trusted launch can't access guest attestation, which allows Microsoft Defender for Cloud to monitor the integrity of the boot sequence of your VMs.
151
+
In Azure, NSGs are used to help filter network traffic between Azure resources. NSGs contain security rules that either allow or deny inbound network traffic, or outbound network traffic from several types of Azure resources. The Azure Attestation endpoint should be able to communicate with the Guest Attestation extension. Without this endpoint, Trusted Launch can't access guest attestation, which allows Microsoft Defender for Cloud to monitor the integrity of the boot sequence of your VMs.
152
152
153
153
To unblock Azure Attestation traffic in NSGs by using service tags:
154
154
@@ -162,9 +162,9 @@ To unblock Azure Attestation traffic in NSGs by using service tags:
162
162
163
163
:::image type="content" source="media/trusted-launch/unblocking-NSG.png" alt-text="Screenshot that shows how to make the destination a service tag.":::
164
164
165
-
Firewalls protect a virtual network, which contains multiple Trusted launch VMs. To unblock Azure Attestation traffic in a firewall by using an application rule collection:
165
+
Firewalls protect a virtual network, which contains multiple Trusted Launch VMs. To unblock Azure Attestation traffic in a firewall by using an application rule collection:
166
166
167
-
1. Go to the Azure Firewall instance that has traffic blocked from the Trusted launch VM resource.
167
+
1. Go to the Azure Firewall instance that has traffic blocked from the Trusted Launch VM resource.
168
168
1. Under **Settings**, select **Rules (classic)** to begin unblocking guest attestation behind the firewall.
169
169
1. Under **Network rule collection**, select **Add network rule collection**.
170
170
@@ -174,7 +174,7 @@ Firewalls protect a virtual network, which contains multiple Trusted launch VMs.
174
174
175
175
To unblock Azure Attestation traffic in a firewall by using an application rule collection:
176
176
177
-
1. Go to the Azure Firewall instance that has traffic blocked from the Trusted launch VM resource.
177
+
1. Go to the Azure Firewall instance that has traffic blocked from the Trusted Launch VM resource.
178
178
179
179
:::image type="content" source="./media/trusted-launch/firewall-rule.png" lightbox="./media/trusted-launch/firewall-rule.png" alt-text="Screenshot that shows adding traffic for the application rule route.":::
0 commit comments