Management and Governance Services
Section 6 of the CIS Microsoft Azure Foundations Benchmark v6.0.0 holds 24 controls on Azure's logging, alerting and governance plumbing: diagnostic settings, activity log alerts, flow logs, monitoring coverage and resource locks. ConfigCobra assesses it read-only across your subscriptions and points each finding at the exact Azure resource.
About this section
Section 6, Management and Governance Services, is where the CIS Microsoft Azure Foundations Benchmark v6.0.0 deals with how an Azure environment records what happens and how it is protected from accidental change. It contains 24 of the benchmark's 127 controls. Almost all of them sit under one subsection, 6.1, which is about Azure Monitor; the single remaining control, 6.2, is about resource locks.
Reading the control titles, the section falls into a few themes. The first is diagnostic settings: a subscription-level setting for activity logs that captures appropriate categories, logging for Azure Key Vault, and diagnostic settings that send Microsoft Entra and Microsoft Graph activity logs to a suitable destination. A related control covers Intune logs. The second theme is network visibility, with controls for capturing network security group flow logs and virtual network flow logs in Log Analytics. A third is protection of the log store itself, where one control asks that the storage account holding activity logs is encrypted with a customer-managed key.
The largest group, eleven controls under 6.1.2, is a family of activity log alerts. They ask for an alert when someone creates or deletes a policy assignment, creates, updates or deletes a network security group, changes a security solution, changes a SQL server firewall rule, creates or deletes a public IP address, and for an alert covering service health. The idea is that risky configuration changes in a subscription should not go unnoticed. The remaining controls ask for resource logging on every service that supports it, Application Insights configuration, avoiding Basic, Free and Consumption SKUs on production artifacts that need monitoring and an SLA, and resource locks on mission-critical resources.
For an administrator this section is mostly about the Azure portal's Monitor blade, diagnostic settings on subscriptions and individual resources, Log Analytics workspaces and alert rules. Gaps here rarely cause an outage, but they decide whether you can reconstruct an incident afterwards.
ConfigCobra assesses this section as part of the Azure scan that covers all four Azure benchmarks. The scan is read-only: it uses a certificate-based app registration with Reader on the target subscriptions plus a read-only Microsoft Graph policy permission, and it never writes to your Azure. It can cover every subscription the app can read or a selected list, run on a daily, weekly or monthly schedule or ad hoc. Every finding points at the exact Azure resource, carries a ConfigCobra severity estimate used to prioritise remediation (CIS itself publishes no severity), and comes with copy-paste remediation steps. Before you apply a fix, remediation impact analysis shows the affected resources and identities, and drift detection alerts you when a control that passed starts failing again. Results go into the PDF report and the dashboard.
The control numbering and counts above follow the CIS Microsoft Azure Foundations Benchmark v6.0.0; the description of the themes is ConfigCobra's own reading of the control titles.
The 24 controls
| CIS ID | Check | Profile |
|---|---|---|
| 6.2 | Ensure that Resource Locks are set for Mission-Critical Azure Resources | Level 2 |
| 6.1.4 | Ensure that Azure Monitor Resource Logging is Enabled for All Services that Support it | Level 1 |
| 6.1.5 | Ensure Basic, Free, and Consumption SKUs are not used on Production artifacts requiring monitoring and SLA | Level 2 |
| 6.1.1.1 | Ensure that a 'Diagnostic Setting' Exists for Subscription Activity Logs | Level 1 |
| 6.1.1.2 | Ensure Diagnostic Setting Captures Appropriate Categories | Level 1 |
| 6.1.1.3 | Ensure the Storage Account Containing the Container with Activity Logs is Encrypted with Customer-managed Key (CMK) | Level 2 |
| 6.1.1.4 | Ensure that Logging for Azure Key Vault is 'Enabled' | Level 1 |
| 6.1.1.5 | Ensure that Network Security Group Flow Logs are Captured and Sent to Log Analytics | Level 2 |
| 6.1.1.6 | Ensure that Virtual Network Flow Logs are Captured and Sent to Log Analytics | Level 2 |
| 6.1.1.7 | Ensure that a Microsoft Entra Diagnostic Setting Exists to Send Microsoft Graph Activity Logs to an Appropriate Destination | Level 2 |
| 6.1.1.8 | Ensure that a Microsoft Entra Diagnostic Setting Exists to Send Microsoft Entra Activity Logs to an Appropriate Destination | Level 2 |
| 6.1.1.9 | Ensure that Intune Logs are Captured and Sent to Log Analytics | Level 2 |
| 6.1.2.1 | Ensure that Activity Log Alert Exists for Create Policy Assignment | Level 1 |
| 6.1.2.2 | Ensure that Activity Log Alert exists for Delete Policy Assignment | Level 1 |
| 6.1.2.3 | Ensure that Activity Log Alert Exists for Create or Update Network Security Group | Level 1 |
| 6.1.2.4 | Ensure that Activity Log Alert Exists for Delete Network Security Group | Level 1 |
| 6.1.2.5 | Ensure that Activity Log Alert Exists for Create or Update Security Solution | Level 1 |
| 6.1.2.6 | Ensure that Activity Log Alert Exists for Delete Security Solution | Level 1 |
| 6.1.2.7 | Ensure that Activity Log Alert Exists for Create or Update SQL Server Firewall Rule | Level 1 |
| 6.1.2.8 | Ensure that Activity Log Alert Exists for Delete SQL Server Firewall Rule | Level 1 |
| 6.1.2.9 | Ensure that Activity Log Alert Exists for Create or Update Public IP Address rule | Level 1 |
| 6.1.2.10 | Ensure that Activity Log Alert Exists for Delete Public IP Address rule | Level 1 |
| 6.1.2.11 | Ensure that an Activity Log Alert Exists for Service Health | Level 1 |
| 6.1.3.1 | Ensure Application Insights are Configured | Level 2 |
Check all 24 controls on your Microsoft Azure
ConfigCobra runs this section with the rest of the CIS Microsoft Azure Foundations Benchmark v6.0.0, read-only.