AZ-305 ยท Authorization, secrets and keys
Customer-managed keys: where the key lives and how it rotates
Platform-managed vs customer-managed keys, Key Vault Premium vs Azure Key Vault Managed HSM (single tenant, FIPS level), key rotation policies and certificate auto-renewal.
Key points
- Default: platform-managed keys. A customer-managed key (CMK): you control and revoke the key wrapping the data key.
- Key Vault Premium: HSM-protected keys, multitenant.
- Managed HSM: single-tenant pool, security domain, local RBAC; both FIPS 140-3 Level 3.
- Access: managed identity with get, wrap, unwrap.
- Rotation policy: scheduled new key versions; use a versionless key URI.
- DigiCert, GlobalSign, self-signed certificates can auto-renew.
Source: https://learn.microsoft.com/en-us/azure/storage/common/customer-managed-keys-overview
Practice questions
Which Azure key store is a single-tenant HSM pool in which each customer gets a separate security domain?
- Azure Key Vault Standard
- Azure Key Vault Premium
- Azure Key Vault Managed HSM
- Azure App Configuration
Show answer
Answer: C. Azure Key Vault Managed HSM
Azure Key Vault Managed HSM dedicates an HSM cluster to one customer and isolates it with a customer-specific security domain. Key Vault Standard and Premium are multitenant services, and Azure App Configuration is not a key store.
Which requirements must the key vault and key meet before you configure customer-managed keys for an Azure Storage account?
- Soft delete is enabled on the vault
- Purge protection is enabled on the vault
- The key is an RSA or RSA-HSM key
- The vault is in the same region as the storage account
- A system-assigned identity is used when the account is created
Show answer
Answer: A. Soft delete is enabled on the vault, B. Purge protection is enabled on the vault, C. The key is an RSA or RSA-HSM key
The vault or Managed HSM must have soft delete and purge protection enabled, and the key must be RSA or RSA-HSM (2048, 3072 or 4096 bits). The vault may be in a different region, subscription or even tenant. At account creation you must use a user-assigned managed identity, not a system-assigned one.
When Key Vault rotates a customer-managed key, all data protected by that key is re-encrypted with the new key material.
Show answer
Answer: False
False. Rotation creates a new key version and re-wraps the data encryption keys; the underlying data is not re-encrypted. That is why the old key version must stay enabled until re-wrapping finishes.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
