turbot/azure_compliance

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

Description

Ensure that all Secrets in 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

  1. Go to Key vaults
  2. For each Key vault, click on Secrets.
  3. Under the Settings section, Make sure Enabled is set to Yes
  4. 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

Set-AzKeyVaultSecretAttribute -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_3

Snapshot and share results via Turbot Pipes:

powerpipe login
powerpipe control run azure_compliance.control.cis_v150_8_3 --share

SQL

This control uses a named query:

keyvault_with_rbac_secret_expiration_set

Tags