Secure key release
Concept
Secure key release (SKR) is a capability of Azure Key Vault Premium and Managed HSM that releases an HSM-protected key only to a trusted execution environment whose attestation claims satisfy a release policy defined by the customer.
Description
Secure key release (SKR) is a capability of Azure Key Vault Premium and Managed HSM. It releases an HSM-protected key only to a trusted execution environment whose attestation claims satisfy a release policy defined by the customer. In practice it adds an access layer around data encryption and decryption keys, so that only a specific application running in a known, verified configuration can obtain the key material.
The approach targets workloads that run on Azure confidential computing. According to the documentation notes, a key can be released from Azure Key Vault to an attested trusted execution environment such as an SGX enclave, an AMD SEV-SNP confidential VM or a confidential container. Instead of relying only on identity and role-based access, the key owner can require proof about the environment itself: what kind of environment is asking for the key and whether it meets the expected compliance and configuration state.
The mechanism depends on Microsoft Azure Attestation. Release decisions rest only on claims in Microsoft Azure Attestation tokens. The application first performs remote attestation, and Azure Attestation issues a signed token describing the environment. The application presents this token when it requests the key, and Azure Key Vault checks the token's claims against the release policy that was attached to the key when the exportable key was created. If the claims match, the key is released; if not, it is withheld.
The release policy is a JSON document. Its top level is a list of alternatives, and each alternative names an attestation authority and a set of claims that must match. One example given in the documentation is a policy that requires an attestation type of sevsnpvm and a compliance status of azure-compliant-cvm, which ties key release to an AMD SEV-SNP confidential VM that Azure reports as compliant.
The Premium workflow follows a fixed order. First, a vault is created with the premium SKU. Second, the release policy is written. Third, an exportable RSA-HSM key is created with the policy attached. Finally, the target environment attests and requests the release. Because the policy is bound to the key at creation, the conditions for release are defined by the customer before any workload asks for the key.
A distinction worth noting concerns Trusted Launch VMs. These can also produce attestation tokens, so a policy can gate on claims such as secure boot or PCR values. However, the documentation notes that a confidential offering is needed to protect keys from the host in memory. A policy based only on Trusted Launch claims therefore verifies the boot state but does not by itself give the memory protection that confidential VMs, enclaves or confidential containers provide.
Typical decisions around secure key release include which attestation claims to require, whether to allow several alternative environments in one policy, and whether to use Key Vault Premium or Managed HSM as the key store. No M365.FM episodes are currently linked to this topic, so the description here rests on the documentation notes for Azure Key Vault and Azure Confidential Computing.
Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.
| Type | Concept |
|---|
Frequently asked questions
Questions marked with AI were written with AI from the facts on this page.
What does secure key release do? (AI)
It releases an HSM-protected key from Azure Key Vault Premium or Managed HSM only to a trusted execution environment whose attestation claims satisfy the customer's release policy.
Which environments can receive a released key? (AI)
The documentation names SGX enclaves, AMD SEV-SNP confidential VMs and confidential containers as attested trusted execution environments. Trusted Launch VMs can also produce tokens, but a confidential offering is needed to protect keys from the host in memory.
How is the release decision made? (AI)
The application performs remote attestation and receives a signed token from Microsoft Azure Attestation. Azure Key Vault compares the token's claims with the JSON release policy attached when the exportable key was created.
Community wiki
Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.
Experts and companies for this topic
Nobody has listed this topic yet. Add it to your profile.
Maintained by Mirko Peters (Microsoft MVP) · Last updated: