CIS Microsoft Azure Foundations Benchmark v1.4.0/Logging and Monitoring/74 of 115
5.1.5Ensure that logging for Azure KeyVault is 'Enabled'
Control family: Logging and Monitoring
Control description
Enable AuditEvent logging for key vault instances to ensure interactions with key vaults are logged and available.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
Key Vault resource logs record every request to a vault: who read which secret or used which key, and from where. Without them, a stolen credential used to pull secrets leaves no trace.
Before you start
The same on every cloud, before the steps in the tabs.
- Decide where key vault logs go and how long they are kept, and who reviews access to secrets.
Evidence
- The logging standard section on key vaults
On Azure the tasks add a diagnostic setting to each key vault that sends its audit logs to Log Analytics, then keep it checked with the CIS standard.
Task 1Send key vault audit logs to Log Analytics
- Sign in to the Azure portal at portal.azure.com and open Key vaults, then the vault.
- From the resource menu, select Diagnostic settings, then Add diagnostic setting.
- Under Category groups, select audit and allLogs.
- Select Send to Log Analytics workspace and the security workspace (and optionally Archive to a storage account).
- Select Save.
- Check it: after a secret is read, an entry appears in the workspace (or in the insights-logs-auditevent container).
Task 2Keep it checked with the CIS v1.4.0 standard in Defender for Cloud
- Open Microsoft Defender for Cloud > Regulatory compliance and select Manage compliance policies.
- Select the subscription, select Security policies, find CIS Microsoft Azure Foundations Benchmark v1.4.0 and toggle its status to On (once per subscription).
- Back on Regulatory compliance, open the CIS Microsoft Azure Foundations Benchmark v1.4.0 standard and expand recommendation 5.1.5.
- Open the assessment for Resource logs in Key Vault should be enabled and fix the resources it lists as non-compliant.
- Check it: every resource under recommendation 5.1.5 shows as passing after the next evaluation.
Evidence
- The diagnostic setting of each key vault, with the audit category group
- The CIS v1.4.0 standard, with recommendation 5.1.5 passing
Not applicable. This benchmark covers Azure only.
Not applicable. This benchmark covers Azure only.
Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.