Control: 8.4 Ensure that the Expiration Date is set for all Secrets in Non-RBAC Key Vaults
Description
Ensure that all Secrets in Non Role Based Access Control (RBAC) Azure Key Vaults have an expiration time 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 time) attribute identifies the expiration time 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 time for all secrets. This ensures that the secrets cannot be used beyond their assigned lifetimes.
Remediation
From Azure Portal
- Go to
Key vaults
- For each Key vault, click on
Secrets
. - Under the
Settings
section, Make sureEnabled
is set toYes
- Set an appropriate
EXPIRATION DATE
on all secrets.
From Azure CLI
Use the below command to set EXPIRATION DATE
on the all secrets
az keyvault secret set-attributes --name <secretName> --vault-name <vaultName> --expires Y-m-d'T'H:M:S'Z'
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.
Usage
Run the control in your terminal:
powerpipe control run azure_compliance.control.cis_v150_8_4
Snapshot and share results via Turbot Pipes:
powerpipe loginpowerpipe control run azure_compliance.control.cis_v150_8_4 --share
SQL
This control uses a named query:
keyvault_with_non_rbac_secret_expiration_set