Identity Services
Section 5 of the CIS Microsoft Azure Foundations Benchmark v6.0.0 is Identity Services, with 15 controls on Microsoft Entra sign-in settings and Azure role assignments. ConfigCobra assesses it read-only in an Azure scan and reports each failing control as a finding on the exact resource.
About this section
Section 5, Identity Services, is one of seven sections with controls in the CIS Microsoft Azure Foundations Benchmark v6.0.0, and it holds 15 of the benchmark's 127 controls. It looks at two sides of the same question: how people prove who they are when they sign in to Microsoft Entra ID, and what those identities are allowed to do once they reach your Azure subscriptions.
The controls fall into a few clear themes, going by their titles. The first is sign-in protection: whether security defaults are enabled, whether multifactor authentication is enabled for all users, whether MFA is required to register or join devices, and whether users can remember MFA on devices they trust. The second is privileged-account hygiene: keeping admin accounts out of daily operations, restricting the User Access Administrator role, and reviewing privileged, non-privileged and tenant creator role assignments. The third is subscription governance: no custom subscription administrator roles, a custom role for administering resource locks, subscription transfer into or out of the Entra tenant set to permit no one, and a subscription owner count between 2 and 3. The last is account lifecycle: reviewing guest users regularly and making sure disabled accounts hold no read, write or owner permissions.
Many of these are about habits as much as settings. Several controls ask that assignments or guests are reviewed periodically, so a passing result is a snapshot of the current state and not proof that a review process exists. That is why continuous checking matters here. Role assignments and guest accounts change all the time, and a clean result on the day of an audit says little about the weeks before it.
ConfigCobra covers this section as part of the Foundations benchmark in its Azure scan, which assesses all four Azure benchmarks together. Access is read-only: Reader on the target subscriptions plus a read-only Microsoft Graph policy permission, through a certificate-based app registration, so ConfigCobra never writes to your Azure. You can scan every subscription the app can read or a selected list. Scans run on a schedule you set (daily, weekly or monthly) or ad hoc on demand, and you are alerted by email when a control regresses.
Each finding points at the exact Azure resource it concerns and carries a severity that is ConfigCobra's own estimate for prioritising work, since CIS publishes no severity. Before you change anything, remediation impact analysis shows the affected resources and identities, with the effect, a confidence level and an impact level of High, Medium, Low or None. That matters for identity changes, where a tightened policy can lock people out. Fixes are given as copy-paste scripts or portal steps for you to run yourself. The control titles in the table above are ConfigCobra's own wording with CIS numbering. The full text is in the official CIS Microsoft Azure Foundations Benchmark, which is the reference to read before you decide on a change.
The 15 controls
Check all 15 controls on your Microsoft Azure
ConfigCobra runs this section with the rest of the CIS Microsoft Azure Foundations Benchmark v6.0.0, read-only.