Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Applies to: Hyperconverged deployments of Azure Local
This article provides an overview of confidential virtual machines (CVMs) on Azure Local.
CVMs on Azure Local bring hardware-based memory encryption and attestation to customer-owned edge infrastructure. They extend Azure's confidential computing platform to the edge to provide cryptographic assurance that protects and encrypts data in use, in RAM, and during computation.
CVMs offer stronger security and confidentiality than standard virtual machines (VMs). They provide hardware-based isolation between virtual machines, the hypervisor, and host management code.
Features
Guest memory isolation: Hardware-encrypted memory by using AMD SEV-SNP ensures workload memory is cryptographically isolated from the host environment.
Disk integrity protection: You choose the security of the guest OS image. Microsoft provides a sample script that creates a hardened guest OS image (for example, by turning off emergency shells) and enables integrity protection. This approach also enables guest OS disk integrity protection for CVMs. To protect against host-side tampering of the guest OS disk and boot chain, enable guest OS image integrity.
Hardware-rooted attestation: Platform firmware measurements bound to workload integrity enable remote verification before sensitive data or keys are released to the workload.
Stateless architecture: CVMs are designed for stateless environments with a minimal Trusted Computing Base (TCB). Workloads fetch secrets post-boot through secure key release and process data entirely in encrypted RAM.
Remote attestation with Microsoft Azure Attestation for secure key release: CVMs generate hardware-rooted attestation reports that Microsoft Azure Attestation validates to issue tokens for secure key release through Azure Key Vault.
Technical architecture
The CVM architecture on Azure Local enables secure workload execution through a layered trust model. The process begins when you use the Azure portal or Azure CLI to check whether an Azure Local cluster is CVM-capable and, after confirmation, create a CVM on the host. Within the host, a guest environment runs the customer workload alongside the guest attestation library. This library allows the user to obtain cryptographic evidence bound to the CVM, so the workload can prove via attestation that it's running in a trusted environment. The Azure Attestation service combined endpoint then attests the CVM report. After successful attestation, the Azure Key Vault relying party performs a secure key release based on the attestation evidence. This process ensures that secrets are released only to verified, confidential compute environments that run on trusted hardware and firmware.
The fundamental security model of CVMs on Azure Local involves hardware-based memory encryption, hardware-rooted firmware measurements, binding the vTPM implementation to the Trusted Execution Environment (TEE), and secure key release before accessing sensitive data.
In this approach, you design solutions specifically for stateless environments with a minimal Trusted Computing Base (TCB). Workloads fetch secrets post-boot through secure key release and process data entirely in encrypted RAM. This approach provides the tightest security boundary because it isolates only the data-handling components within the CVM boundary.
Trust boundary
CVMs establish a strong trust boundary by excluding host administrators. This trust boundary ensures that workload data and execution remain protected even from infrastructure operators. However, consider any Azure resources as part of the trust boundary.
CVMs defend against threats such as remote attackers with host-level access, malicious datacenter personnel with console access, compromised host operating systems, and boot disk tampering. Integrity verification mechanisms help protect against these threats.
Physical attack considerations
Trusted Execution Environments (TEEs) such as AMD SEV-SNP don't protect against sophisticated physical side-channel attacks (for example, power, electromagnetic, timing, or logic analysis attacks). However, they significantly strengthen security by isolating workloads and protecting data from unauthorized access. When combined with physical safeguards such as secure facilities, tamper-evident controls, and environmental monitoring, TEEs provide a robust defense-in-depth approach that makes physical attacks substantially more difficult.
Supported operating systems
The current release supports Linux-based guest operating systems only – Ubuntu 24.04 using our integrity protected script.
Windows CVM guest support isn't available in this release.
Supported OEM hardware
CVM deployment on Azure Local is validated on the following OEM server configurations with AMD Gen 4 EPYC processors with SEV-SNP technology.
| OEM | Server model |
|---|---|
| Lenovo | ThinkAgile MX455 V3 Edge PR |
| HPE | ProLiant DL145 Gen11 |
You can find this configuration in the Azure Local catalog.
Limitations
- To maintain the security boundary, guest management isn't supported.
- Sections of the file system are read-only.
- The entire file system is ephemeral.
- You must custom-tailor images to CVM.
- Clean-room image preparation is required. The username and password are fixed during image preparation.
- Cloud connectivity is required for Azure Attestation and secure key release (Azure Key Vault).
- Migration of a running CVM isn't supported. Shut down all CVMs before you migrate them.
- Windows Update isn't a supported update path. Take updates only through the Azure portal. For more information, see Install a solution upgrade on Azure Local.
Next steps
This feature is available only in Azure Local 2607 or later.