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
Implement an option to use either Azure Disk Encryption or Encryption at Host on the Bastion VMs in the Hub. Also provide an option to use the "Security Type" option of either "Trusted Launch" or "Confidential VM" with vTPM, Secure Boot, and Integrity Monitoring. These two features greatly improve the security of the VMs deployed as part of MLZ.
Server-Side Encryption with Encryption at Host and Trusted Launch have been added to the bicep code. These are the recommended zero trust configurations that we plan to implement for now.
Implement an option to use either Azure Disk Encryption or Encryption at Host on the Bastion VMs in the Hub. Also provide an option to use the "Security Type" option of either "Trusted Launch" or "Confidential VM" with vTPM, Secure Boot, and Integrity Monitoring. These two features greatly improve the security of the VMs deployed as part of MLZ.
https://learn.microsoft.com/en-us/azure/virtual-machines/trusted-launch
https://learn.microsoft.com/en-us/azure/confidential-computing/quick-create-confidential-vm-portal-amd
https://learn.microsoft.com/en-us/azure/virtual-machines/disk-encryption-overview
The text was updated successfully, but these errors were encountered: