Skip to content

Commit 2047c0e

Browse files
author
Ajay Kundnani
committed
Updated findings
1 parent ca77122 commit 2047c0e

10 files changed

+8
-5
lines changed
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.

articles/virtual-machines/trusted-launch-existing-vm.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Azure Virtual Machines supports enabling Trusted Launch on existing [Azure Gener
3434
- Azure Generation 2 VM(s) should be **stopped and deallocated** before enabling Trusted Launch security type.
3535
- Azure Backup if enabled for Generation 2 VM(s) should be configured with [Enhanced Backup Policy](../backup/backup-azure-vms-enhanced-policy.md). Trusted Launch security type cannot be enabled for Generation 2 VM(s) configured with *Standard Policy* backup protection.
3636

37-
## Best Practices
37+
## Best practices
3838

3939
- [Create restore point](create-restore-points.md) for Azure Generation 2 VM(s) before enabling Trusted Launch security type. You can use the Restore Point to re-create the disks and Generation 2 VM with the previous well-known state.
4040
- Enable Trusted launch on a test Generation 2 VM and ensure if any changes are required to meet the prerequisites before enabling Trusted Launch on Generation 2 VMs running production workloads.
@@ -268,7 +268,7 @@ New-AzResourceGroupDeployment `
268268

269269
5. Verify that the deployment is successful. Check for the security type and UEFI settings of the VM using Azure portal. Check the Security type section in the Overview page.
270270

271-
:::image type="content" source="./media/trusted-launch/gen2-tvm-settings.png" alt-text="Screenshot of the Trusted Launch properties of the VM.":::
271+
:::image type="content" source="./media/trusted-launch/generation-2-trusted-launch-settings.png" alt-text="Screenshot of the Trusted Launch properties of the VM.":::
272272

273273
6. Start the upgraded Trusted Launch VM and ensure that it has started successfully and verify that you are able to log in to the VM using either RDP (for Windows VM) or SSH (for Linux VM).
274274

articles/virtual-machines/trusted-launch-faq.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -339,7 +339,7 @@ New-AzVM -Name MyVm -Credential $vmCred -SecurityType Standard
339339

340340
---
341341

342-
## Feature Support
342+
## Feature support
343343

344344
### Does trusted launch support Azure Compute Gallery?
345345

@@ -368,13 +368,14 @@ Backups taken before [upgrading existing Generation 2 VM to Trusted Launch](trus
368368
### Will backup continue to work after enabling Trusted Launch?
369369
Backups configured with [enhanced policy](../backup/backup-azure-vms-enhanced-policy.md) will continue to take backup of VM after enabling Trusted Launch.
370370

371-
## Boot Integrity Monitoring
371+
## Boot integrity monitoring
372372

373373
### What happens when an integrity fault is detected?
374374

375375
Trusted launch for Azure virtual machines is monitored for advanced threats. If such threats are detected, an alert is triggered. Alerts are only available if [Defender for Cloud's enhanced security features](../security-center/enable-enhanced-security.md) are enabled.
376376

377377
Microsoft Defender for Cloud periodically performs attestation. If the attestation fails, a medium severity alert is triggered. Trusted launch attestation can fail for the following reasons:
378+
378379
- The attested information, which includes a log of the Trusted Computing Base (TCB), deviates from a trusted baseline (like when Secure Boot is enabled). This deviation indicates an untrusted module(s) have been loaded and the OS may be compromised.
379380
- The attestation quote could not be verified to originate from the vTPM of the attested VM. This verification failure indicates a malware is present and may be intercepting traffic to the TPM.
380381
- The attestation extension on the VM is not responding. This unresponsive extension indicates a denial-of-service attack by malware or an OS admin.

articles/virtual-machines/trusted-launch-portal.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -165,9 +165,10 @@ You can deploy trusted launch VMs using a quickstart template:
165165
- **Recommended** [Trusted launch VM Supported (`TrustedLaunchSupported`) images](#trusted-launch-vm-supported-images) are images where the source does not have VM Guest state information and can be used to create either [Generation 2 VMs](generation-2.md) or [Trusted Launch VMs](trusted-launch.md).
166166
- [Trusted launch VM (`TrustedLaunch`) images](#trusted-launch-vm-images) are images where the source usually has [VM Guest state information](trusted-launch-faq.md#what-is-vm-guest-state-vmgs) and can be used to create only [Trusted Launch VMs](trusted-launch.md).
167167

168-
### Trusted launch VM Supported Images
168+
### Trusted launch VM supported images
169169

170170
For the following image sources, the security type on the image definition should be set to `TrustedLaunchsupported`:
171+
171172
- Gen2 OS Disk VHD
172173
- Gen2 Managed Image
173174
- Gen2 Gallery Image Version

articles/virtual-machines/trusted-launch.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -66,6 +66,7 @@ Azure offers trusted launch as a seamless way to improve the security of [genera
6666
## Additional information
6767

6868
**Regions**:
69+
6970
- All public regions
7071
- All Azure Government regions
7172

0 commit comments

Comments
 (0)