Use cases for confidential virtual machine

Before confidential virtual machine (CVM) and trusted execution environment (TEE), a cloud service provider (CSP) or anyone with administrative access could read or modify the memory of a virtual machine (VM). CVM and TEE eliminated this vulnerability.

Hardware memory encryption
  • You can run workloads that handle sensitive data in memory, such as data transactions, on a RHEL CVM image on Azure. Hardware memory encryption protects the data residing in physical RAM.
  • You can deploy customer records, health data, or payment information on Azure if your policy allows that the hypervisor and host administrators cannot read VM memory including memory dumps.
  • You can protect data in-use by running the same application stack on a standard RHEL Azure image without changing the application code.
Cryptographic attestation
  • CVM provides a guarantee that your VM runs on genuine hardware with an expected boot state before you release secrets, keys, or access to protected resources.
  • You can use either a self hosted or CSP attestation server to unlock encrypted disks or release decryption keys from a key management service. This is only after an attestation report confirms an untampered RHEL CVM with the expected firmware, boot loader, and kernel measurements.
  • You can enforce access policies so that only attested RHEL CVM instances connect to corporate networks, identity services, or secret stores such as Azure Key Vault.
  • Before processing regulated data on Azure, make sure that you meet compliance requirements by producing verifiable proof that a workload runs in a confidential environment.
CPU-enforced state protection
  • You can confidently run security-sensitive workloads where data might leak through CPU registers, caches, or memory management structures when the processor switches between your VM and Azure management tasks.
  • You can add another layer of protection beyond memory encryption for high-value workloads on RHEL CVM, such as key handling services or security gateways, without changing standard RHEL applications deployment methods on Azure.