Loading controls...

Control: 8.4 Ensure that the Expiration Date is set for all Secrets in Non- RBAC Key Vaults


Ensure that all Secrets in Non Role Based Access Control (RBAC) Azure Key Vaults have an expiration date set.

The Azure Key Vault enables users to store and keep secrets within the Microsoft Azure environment. Secrets in the Azure Key Vault are octet sequences with a maximum size of 25k bytes each. The exp (expiration date) attribute identifies the expiration date on or after which the secret MUST NOT be used. By default, secrets never expire. It is thus recommended to rotate secrets in the key vault and set an explicit expiration date for all secrets. This ensures that the secrets cannot be used beyond their assigned lifetimes.


From Azure Portal

  1. Go to Key vaults.
  2. For each Key vault, click on Secrets.
  3. In the main pane, ensure that the status of the secret is Enabled.
  4. Set an appropriate Expiration date on all secrets.

From Azure CLI

Update the Expiration date for the secret using the below command:

az keyvault secret set-attributes --name <secretName> --vault-name <vaultName> --expires Y-m-d'T'H:M:S'Z'

Note To view the expiration date on all secrets in a Key Vault using Microsoft API, the List Key permission is required.

To update the expiration date for the secrets:

  1. Go to the Key vault, click on Access policies.
  2. Click on Create and add an access policy with the Update permission (in the Secret Permissions - Secret Management Operations section).

From Powershell

For each Key vault with the EnableRbacAuthorization setting set to False or empty, run the following command.

Set-AzKeyVaultSecret -VaultName <Vault Name> -Name <Secret Name> -Expires <DateTime>

Default Value

By default, secrets do not expire.


Run the control in your terminal:

steampipe check azure_compliance.control.cis_v200_8_4

Snapshot and share results via Steampipe Cloud:

steampipe login
steampipe check --share azure_compliance.control.cis_v200_8_4


This control uses a named query: