Control: 8.1 Ensure that the Expiration Date is set for all Keys in RBAC Key Vaults
Description
Ensure that all Keys in Role Based Access Control (RBAC) Azure Key Vaults have an expiration time set.
Azure Key Vault enables users to store and use cryptographic keys within the Microsoft Azure environment. The exp (expiration time) attribute identifies the expiration time on or after which the key MUST NOT be used for encryption of new data, wrapping of new keys, and signing. By default, keys never expire. It is thus recommended that keys be rotated in the key vault and set an explicit expiration time for all keys to help enforce the key rotation. This ensures that the keys cannot be used beyond their assigned lifetimes.
Remediation
From Azure Portal
- Go to
Key vaults
- For each Key vault, click on
Keys
. - Under the
Settings
section, Make sureEnabled
is set to Yes - Set an appropriate
EXPIRATION DATE
on all keys.
From Azure CLI
Update the EXPIRATION DATE
for the key using below command.
az keyvault key set-attributes --name <keyName> --vault-name <vaultName> -- expires Y-m-d'T'H:M:S'Z'
Note: In order to access expiration time on all keys in Azure Key Vault using Microsoft API requires "List" Key permission.
To provide required access follow below steps,
For Key Vaults using "Key Vault Access Policy"
- Go to
Key vaults
- For each Key vault, click on
Access Policy
. - Add access policy with
Key permission
asList
For Key Vaults using "Role Based Access Control"
Assign the role of "Key Vault Secrets Officer" to the appropriate user From Powershell
Set-AzKeyVaultKeyAttribute -VaultName <Vault Name> -Name <Key Name> -Expires <DateTime>
Default Value
By default, keys do not expire.
Usage
Run the control in your terminal:
powerpipe control run azure_compliance.control.cis_v150_8_1
Snapshot and share results via Turbot Pipes:
powerpipe loginpowerpipe control run azure_compliance.control.cis_v150_8_1 --share
SQL
This control uses a named query:
keyvault_with_rbac_key_expiration_set