Help Center
Go back to application
Help Center
Go back to application
Platform Terms GlossarySupport and Bug Reporting
Task Management
Task Management explained Creating Tasks Setting up Task NotificationsGiving permissions to team members
Organization
Working together in KertosInviting UsersCreating rolesAssigning System AccessCreating Departments and Assigning Users
Integrations
Discovery
Tasks
Device Management
Human Resource Information Systems
Inventory
Inventorization of vendorsInventorization of systemsInventorization of assetsEU AI Act: Inventorization of AI use cases
Risks
Managing risks
Trust Center
Setting up your trust center
Incidents
Reporting incidents
KAIA
KAIA explainedPrinciples of AI at Kertos
Interacting with KAIA
Compliance
Frameworks explainedManaging & implementing controlsCreating & managing policiesCompleting & assigning trainingsGuidance
Privacy Management
Creating a RoPACreating TOMsCreating DPIAs
Data Subject Requests
API Reference
Ingress API Docs for DSRs Webhook API Docs for DSRs
Auto Checks
Auto Checks explainedAuto Checks: AWS Auto Checks: GCPAuto Checks: AzureEnabling Auto Checks by Reconfiguring the Azure IntegrationEnabling Auto Checks by Reconfiguring the GCP IntegrationEnabling Auto Checks by Reconfiguring the AWS Integration
AWS Auto Checks Detailed Explanations
Azure Auto Checks Detailed Explanations
Verify that Server Parameter 'log_retention_days' is greater than 3 days for PostgreSQL Database ServerVerify that server parameter 'connection_throttling' is set to 'ON' for PostgreSQL Database ServerVerify that server parameter 'log_disconnections' is set to 'ON' for PostgreSQL Database ServerVerify that server parameter 'log_connections' is set to 'ON' for PostgreSQL Database ServerVerify that 'Enforce SSL connection' is set to 'ENABLED' for PostgreSQL Database ServerVerify that Server Parameter 'log_checkpoints' is set to 'ON' for PostgreSQL Database ServerVerify that Activity Log Alert exists for Create Policy AssignmentVerify that Activity Log Alert exists for Create or Update Public IP Address ruleVerify that Activity Log Alert exists for Delete SQL Server Firewall RuleVerify that Activity Log Alert exists for Create or Update SQL Server Firewall RuleVerify that Activity Log Alert exists for Delete Network Security GroupVerify that the storage account containing the container with activity logs is encrypted with Customer Managed KeyVerify that Activity Log Alert exists for Delete Policy AssignmentVerify that Activity Log Alert exists for Create or Update Network Security GroupVerify that Diagnostic Setting captures appropriate categoriesVerify that Activity Log Alert exists for Create or Update Security SolutionVerify that Activity Log Alert exists for Delete Public IP Address ruleVerify that logging for Azure AppService 'HTTP logs' is enabledVerify that logging for Azure Key Vault is 'Enabled'Verify that the Expiration Date is set for all Keys in RBAC Key VaultsEnable Role Based Access Control for Azure Key VaultVerify that Private Endpoints are Used for Azure Key VaultVerify that the Key Vault is RecoverableVerify that HTTP(S) access from the Internet is evaluated and restricted

Enable Role Based Access Control for Azure Key Vault

Framework Reference: A.5.15 Integration: Azure – Key Vault (RBAC Configuration)

Why this matters:
Using Azure Role-Based Access Control (RBAC) for Key Vaults provides centralized, fine-grained access control across all vaults and resources. Unlike vault-level access policies, RBAC integrates with Privileged Identity Management (PIM) and Just-In-Time (JIT) access, improving control over sensitive key, secret, and certificate operations and reducing standing privileges.

What this check does:
This check verifies whether each Azure Key Vault is using the Azure RBAC permission model, rather than the legacy Vault access policy model.

Check Logic:

Key Vault property enableRbacAuthorization must be set to true

Where this is configured:
Azure Key Vault → Access Configuration → Permission Model

How this check is executed:

  • Azure Portal:
  • Go to "Key vaults"
  • Select each vault
  • Click "Access configuration"
  • Confirm that the Permission Model is set to Azure role-based access control

Azure CLI:

az keyvault show --resource-group <resource_group> --name <vault_name>

Confirm output contains:

"properties": {  "enableRbacAuthorization": true } 

PowerShell:

Get-AzKeyVault -VaultName <vault_name> -ResourceGroupName <resource_group>

Ensure the Enabled For RBAC Authorization setting is True.

How to fix it:

Azure Portal:

  1. Go to "Key vaults" → select a vault
  2. Click "Access configuration"
  3. Set the Permission Model to "Azure role-based access control"
  4. Acknowledge the warning message and click "Save"
  5. Navigate to "Access Control (IAM)"
  6. Under the "Role assignments" tab, reassign appropriate roles to users or groups

Azure CLI:

az keyvault update \  --resource-group <resource_group> \  --name <vault_name> \  --enable-rbac-authorization true 

PowerShell:

Update-AzKeyVault `  -ResourceGroupName <resource_group> `  -VaultName <vault_name> `  -EnableRbacAuthorization $True

Exceptions:
None specified.

Further resources:

Was this article helpful?

Powered by Product Fruits