Skip to main content

📝 Azure Non-RBAC Key Vault stores Keys without expiration date 🟢

  • Contextual name: 📝 Non-RBAC Key Vault stores Keys without expiration date 🟢
  • ID: /ce/ca/azure/key-vault/non-rbac-key-vault-keys-expiration-date
  • Located in: 📁 Azure Key Vault

Flags​

Our Metadata​

  • Policy Type: COMPLIANCE_POLICY
  • Policy Category:
    • SECURITY

Similar Policies​

Similar Internal Rules​

RulePoliciesFlags
✉️ dec-x-0feec7902

Logic​

Description​

Open File

Description​

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

Rationale​

Azure Key Vault enables users to store and use cryptographic keys within the Microsoft Azure environment. The exp (expiration date) attribute identifies the expiration date on or after which the key MUST NOT be used for a cryptographic operation. By default, keys never expire. It is thus recommended that keys be rotated in the key vault and set an explicit expiration date for all keys. This ensures that the keys cannot be used beyond their assigned lifetimes.

Impact​

Keys cannot be used beyond their assigned expiration dates respectively. Keys need to be rotated periodically wherever they are used.

Audit​

From Azure Portal​
  1. Go to Key vaults.
  2. For each Key vault, click on Keys.
  3. In the main pane, ensure that the status of the key is Enabled.
  4. For each enabled key, ensure that an appropriate Expiration date is set.
From Azure CLI​

Get a list of all the key vaults in your Azure environment by running the following command:

... see more

Remediation​

Open File

Remediation​

From Azure Portal​

  1. Go to Key vaults.
  2. For each Key vault, click on Keys.
  3. In the main pane, ensure that the status of the key is Enabled.
  4. For each enabled key, ensure that an appropriate Expiration date is set.

From Azure CLI​

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

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

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

To update the expiration date for the keys:

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

From PowerShell​

Set-AzKeyVaultKeyAttribute -VaultName <Vault Name> -Name <Key Name> -Expires <DateTime>

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlags
💼 APRA CPG 234 → 💼 4 Cryptographic key management refers to the generation, distribution, storage, renewal, revocation, recovery, archiving and destruction of encryption keys. Effective cryptographic key management ensures that controls are in place to reduce the risk of compromise of the security of cryptographic keys. Any compromise of the security of cryptographic keys could, in turn, lead to a compromise of the security of the information assets protected by the cryptographic technique deployed.67
💼 APRA CPG 234 → 💼 44c loss of, or unauthorised access to, encryption keys safeguarding extremely critical or sensitive information assets.810
💼 CIS Azure v2.1.0 → 💼 8.2 Ensure that the Expiration Date is set for all Keys in Non-RBAC Key Vaults. - Level 1 (Automated)1
💼 CIS Azure v3.0.0 → 💼 3.3.2 Ensure that the Expiration Date is set for all Keys in Non-RBAC Key Vaults. (Automated)1
💼 Cloudaware Framework → 💼 Expiration Management12
💼 FedRAMP High Security Controls → 💼 AC-2(1) Automated System Account Management (M)(H)16
💼 FedRAMP High Security Controls → 💼 IA-5 Authenticator Management (L)(M)(H)61420
💼 FedRAMP High Security Controls → 💼 SC-12 Cryptographic Key Establishment and Management (L)(M)(H)1911
💼 FedRAMP Low Security Controls → 💼 IA-5 Authenticator Management (L)(M)(H)120
💼 FedRAMP Low Security Controls → 💼 SC-12 Cryptographic Key Establishment and Management (L)(M)(H)11
💼 FedRAMP Moderate Security Controls → 💼 AC-2(1) Automated System Account Management (M)(H)16
💼 FedRAMP Moderate Security Controls → 💼 IA-5 Authenticator Management (L)(M)(H)420
💼 FedRAMP Moderate Security Controls → 💼 SC-12 Cryptographic Key Establishment and Management (L)(M)(H)11
💼 ISO/IEC 27001:2013 → 💼 A.9.2.4 Management of secret authentication information of users810
💼 ISO/IEC 27001:2013 → 💼 A.10.1.2 Key management911
💼 ISO/IEC 27001:2022 → 💼 5.9 Inventory of information and35
💼 ISO/IEC 27001:2022 → 💼 5.10 Acceptable use of information and other associated assets1114
💼 ISO/IEC 27001:2022 → 💼 5.16 Identity management24
💼 ISO/IEC 27001:2022 → 💼 5.18 Access rights46
💼 ISO/IEC 27001:2022 → 💼 6.5 Responsibilities after termination or change of employment24
💼 ISO/IEC 27001:2022 → 💼 8.1 User end point devices911
💼 NIST CSF v1.1 → 💼 PR.AC-1: Identities and credentials are issued, managed, verified, revoked, and audited for authorized devices, users and processes1922
💼 NIST CSF v1.1 → 💼 PR.AC-7: Users, devices, and other assets are authenticated (e.g., single-factor, multi-factor) commensurate with the risk of the transaction (e.g., individuals' security and privacy risks and other organizational risks)1922
💼 NIST CSF v1.1 → 💼 PR.DS-1: Data-at-rest is protected1519
💼 NIST CSF v1.1 → 💼 PR.DS-2: Data-in-transit is protected1421
💼 NIST CSF v2.0 → 💼 PR.AA-01: Identities and credentials for authorized users, services, and hardware are managed by the organization23
💼 NIST CSF v2.0 → 💼 PR.AA-03: Users, services, and hardware are authenticated22
💼 NIST CSF v2.0 → 💼 PR.AA-05: Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties58
💼 NIST CSF v2.0 → 💼 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected82
💼 NIST CSF v2.0 → 💼 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected69
💼 NIST SP 800-53 Revision 5 → 💼 AC-2(1) Account Management _ Automated System Account Management416