| name | cis-azure-foundations-8.3.2 |
| description | Ensure that the Expiration Date is set for all Keys in Non-RBAC Key Vaults |
| category | cis-azure-foundations |
| version | 5.0.0 |
| author | cyberstrike-official |
| tags | ["cis","azure","security","key-vault","keys","expiration"] |
| cis_id | 8.3.2 |
| cis_benchmark | CIS Microsoft Azure Foundations Benchmark v5.0.0 |
| tech_stack | ["azure"] |
| cwe_ids | [] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
8.3.2 Ensure that the Expiration Date is set for all Keys in Non-RBAC Key Vaults (Automated)
Description
Ensure that all cryptographic keys stored in Azure Key Vaults using Vault Access Policy authorization (non-RBAC) have an expiration date configured.
Rationale
Cryptographic keys without expiration dates remain valid indefinitely, creating a security risk as the likelihood of key compromise increases over time. Non-RBAC Key Vaults use Vault Access Policies for authorization, but the key management best practices remain the same. Setting an expiration date ensures keys are periodically reviewed and rotated, limiting the impact of potential key compromise. This aligns with cryptographic best practices and compliance requirements.
Impact
When keys expire, applications and services using those keys will fail until the keys are renewed or replaced. Organizations need to implement key rotation procedures and monitoring to ensure keys are renewed before expiration. Automation through Azure Key Vault key rotation policies can help manage this lifecycle.
Audit Procedure
From Azure Portal:
- Go to
Key vaults.
- For each Key Vault with RBAC authorization disabled (using Access Policies), click the vault name.
- Under
Objects, click Keys.
- For each key, verify that the
Expiration date column shows a date (not blank or 'Not set').
From Azure CLI:
az keyvault list --query "[?properties.enableRbacAuthorization!=\`true\`].name" -o tsv
For each non-RBAC Key Vault:
az keyvault key list --vault-name {vaultName} --query "[].{Name:name, Expires:attributes.expires}" -o table
Ensure Expires is set for all keys.
From PowerShell:
$vaults = Get-AzKeyVault | Where-Object { $_.EnableRbacAuthorization -ne $true }
foreach ($vault in $vaults) {
Get-AzKeyVaultKey -VaultName $vault.VaultName | Select-Object Name, Expires
}
Ensure Expires is populated for all keys.
Expected Result
All keys in non-RBAC Key Vaults should have an expiration date set.
Remediation
From Azure Portal:
- Go to
Key vaults.
- Click the name of a Key Vault.
- Under
Objects, click Keys.
- Click the key that needs an expiration date.