-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement Disk Encryption and Secure Boot on Bastion VMs #774
Comments
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. |
You may want to list EncryptionAtHost as a pre-requisite Resource Provider (Microsoft.Compute) for subscriptions or the bicep code will fail. |
@sergio-re thanks for the feedback! You are absolutely correct. I will validate our documentation and if that is missing, I will open a bug. |
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: