CIS Microsoft Azure Foundations Benchmark v1.4.0/Other Security Considerations/99 of 115
8.2Ensure that the Expiration Date is set for all Keys in Non-RBAC Key Vaults.
Control family: Other Security Considerations
Control description
Ensure that all Keys in Non Role Based Access Control (RBAC) Azure Key Vaults have an expiration time set.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
The same applies to vaults that still use the older vault access policy model: every key gets an expiration date. The difference is only in permissions, which come from the vault's access policies rather than Azure roles.
Before you start
The same on every cloud, before the steps in the tabs.
- Agree the maximum lifetime of keys (for example one year, shorter for high-risk ones) and who renews them before they expire.
- Decide how applications learn about a new version, so expiring keys don't cause outages.
Evidence
- The key and secret management standard, with lifetimes and owners for keys
On Azure the tasks set an expiration date on each key in the vault, and keep it checked with the CIS standard.
Task 1Set an expiration date on each key
- Sign in to the Azure portal at portal.azure.com and open Key vaults, then a vault that uses the vault access policy permission model (shown under Settings > Access configuration).
- Make sure you hold an access policy granting Get and Update on keys.
- Select Objects > Keys and open a key without an expiration date.
- Select the current version, select Set expiration date, and choose a date in line with your rotation policy.
- Select Save.
- Check it: the keys list shows an expiration date for every key. For keys, also set a Rotation policy so new versions are created before expiry.
Task 2Keep it checked with the CIS v1.4.0 standard in Defender for Cloud
- Open Microsoft Defender for Cloud > Regulatory compliance and select Manage compliance policies.
- Select the subscription, select Security policies, find CIS Microsoft Azure Foundations Benchmark v1.4.0 and toggle its status to On (once per subscription).
- Back on Regulatory compliance, open the CIS Microsoft Azure Foundations Benchmark v1.4.0 standard and expand recommendation 8.2.
- Open the assessment for Key Vault keys should have an expiration date and set an expiration date on each key it lists.
- Check it: every resource under recommendation 8.2 shows as passing after the next evaluation.
Evidence
- The Keys list of each vault, showing expiration dates
- The CIS v1.4.0 standard, with recommendation 8.2 passing
Not applicable. This benchmark covers Azure only.
Not applicable. This benchmark covers Azure only.
Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.