CIS Microsoft Azure Foundations Benchmark v1.4.0/Other Security Considerations/100 of 115
8.3Ensure that the Expiration Date is set for all Secrets in RBAC Key Vaults
Control family: Other Security Considerations
Control description
Ensure that all Secrets in 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.
Secrets such as passwords and connection strings tend to outlive the people and systems they were made for. An expiration date on every secret in vaults using Azure role-based access control makes sure each one is reviewed and replaced on time.
Before you start
The same on every cloud, before the steps in the tabs.
- Agree the maximum lifetime of secrets (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 secrets don't cause outages.
Evidence
- The key and secret management standard, with lifetimes and owners for secrets
On Azure the tasks set an expiration date on each secret in the vault, and keep it checked with the CIS standard.
Task 1Set an expiration date on each secret
- Sign in to the Azure portal at portal.azure.com and open Key vaults, then a vault that uses the Azure role-based access control permission model (shown under Settings > Access configuration).
- Make sure you hold an Azure role such as Key Vault Crypto Officer or Key Vault Secrets Officer.
- Select Objects > Secrets and open a secret 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 secrets list shows an expiration date for every secret.
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.3.
- Open the assessment for Key Vault secrets should have an expiration date and set an expiration date on each secret it lists.
- Check it: every resource under recommendation 8.3 shows as passing after the next evaluation.
Evidence
- The Secrets list of each vault, showing expiration dates
- The CIS v1.4.0 standard, with recommendation 8.3 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.