Control: 8.6 Enable Role Based Access Control for Azure Key Vault
Description
WARNING: Role assignments disappear when a Key Vault has been deleted (soft- delete) and recovered. Afterwards it will be required to recreate all role assignments. This is a limitation of the soft-delete feature across all Azure services.
The new RBAC permissions model for Key Vaults enables a much finer grained access control for key vault secrets, keys, certificates, etc., than the vault access policy. This in turn will permit the use of privileged identity management over these roles, thus securing the key vaults with JIT Access management.
Remediation
From Azure Portal
Key Vaults on creation can be set to use Azure role-based control
. For already create Key Vaults :
- From Azure Home open the Portal Menu in the top left corner.
- Select Key Vaults
- View the Key Vaults within your subscription.
- Open every Key Vault you wish to audit.
- Select Access Policies
- Set the Permission Model radio button should be set to
Azure role-based control
. - In the screen note the warning message, then click save if you have determined the impact.
- Select
Access Control(IAM)
. - Select the
Role Assignments
in the horizontal row. - Reapply permissions as needed to groups or users.
Default Value
The default value for Access control in Key Vaults is Vault Policy.
Usage
Run the control in your terminal:
powerpipe control run azure_compliance.control.cis_v150_8_6
Snapshot and share results via Turbot Pipes:
powerpipe loginpowerpipe control run azure_compliance.control.cis_v150_8_6 --share
SQL
This control uses a named query:
keyvault_rbac_enabled