Skip to main content
Five Steps for Cloud Compliance Readiness·A practical playbook for security teamsDownload
CIS Microsoft Azure Foundations v6.0.0 · Section 3

Compute Services

Section 3 of the CIS Microsoft Azure Foundations Benchmark v6.0.0 is Compute Services and holds 1 of the benchmark's 127 controls: 3.1.1, a Level 2 recommendation about multifactor authentication for identities that can reach privileged virtual machines. ConfigCobra assesses it read-only across the Azure subscriptions in scope, and the finding points at the exact Azure resource.

1controls
0Level 1
1Level 2

About this section

In the CIS Microsoft Azure Foundations Benchmark v6.0.0, section 3 is named Compute Services and contains 1 of the benchmark's 127 controls. Most compute topics sit in a separate benchmark, CIS Microsoft Azure Compute Services v2.0.0 (99 controls), which the same ConfigCobra scan also covers; this overview is only about the single Foundations control in section 3.

Virtual machines are where interactive administrative access ends up in Azure: someone signs in over RDP or SSH, runs commands, reads disks and reaches whatever network the machine can see. Access to a VM is shaped by two layers. The Azure control plane decides who may manage the machine, through role assignments on the subscription, resource group or the VM itself. The guest operating system decides who may log on. A privileged virtual machine is one where either layer grants administrative reach, for example a jump host, an identity server or a machine that carries a powerful managed identity.

The one control, 3.1.1 (Level 2), is titled "Ensure only MFA Enabled Identities can Access Privileged Virtual Machine". Its theme is simple: a stolen or guessed password alone should never be enough to land on a machine that holds privilege. It sits at the point where identity (section 5 of the same benchmark) meets compute, so reviewing it usually means looking at who holds privileged access to your VMs and what sign-in requirements apply to them. Level 2 is the stricter, security-focused profile, so expect it to matter most where machines are sensitive.

ConfigCobra assesses it with a read-only connection: a certificate-based Entra app registration with Reader on the target subscriptions and a read-only Microsoft Graph policy permission. It never writes to your Azure. It can scan every subscription the app can read or a selected list, and the finding points at the exact resource. Severity is ConfigCobra's own estimate used to prioritise remediation, because CIS publishes no severity.

For a failing result, ConfigCobra generates a copy-paste remediation script or portal steps that you apply yourself. Before you do, remediation impact analysis lists the affected resources and identities with the likely effect, a confidence level and a prepare step, plus an impact level of High, Medium, Low or None. That matters here, because requiring MFA for privileged access can lock out an administrator or stop a service that signs in. Scheduled scans (daily, weekly or monthly) or an ad hoc scan, drift alerts when a control regresses and email notifications keep the result current, and the Azure resource inventory shows the machines involved.

Check all 1 controls on your Microsoft Azure

ConfigCobra runs this section with the rest of the CIS Microsoft Azure Foundations Benchmark v6.0.0, read-only.

Get in touch

Let's talk.

Whether you're evaluating ConfigCobra, running an audit, or managing a client fleet — we respond within one business day.

Free trial