Microsoft Entra (Identity)
Section 5 of the CIS Microsoft 365 Foundations Benchmark v7.0.0 is Microsoft Entra (Identity) and holds 63 of the 160 controls: MFA, password protection, Conditional Access, authentication methods and Privileged Identity Management. ConfigCobra assesses it through read-only Microsoft Graph permissions, with no agents and no admin password sharing.
About this section
Section 5 of the CIS Microsoft 365 Foundations Benchmark v7.0.0 is Microsoft Entra (Identity), assessed through the Microsoft Entra admin center. It is the largest section by far: 63 of the benchmark's 160 controls. Everything else in Microsoft 365 depends on who can sign in and how, so this is where a tenant's identity posture is decided.
The numbering splits the section into three subsections. Subsection 5.1 (26 controls) covers directory-wide settings: whether users may register applications, create tenants or security groups, how devices may join Entra and who becomes a local administrator, whether users may consent to apps, how long application passwords and certificates may live, who can invite guests, and password hash sync for hybrid setups. Subsection 5.2 (32 controls) covers authentication: Conditional Access policies that require MFA, block legacy authentication, block the device code flow and require managed devices; Identity Protection risk policies; authentication methods such as weak SMS and voice methods and MFA fatigue protection; password protection, banned passwords and lockout settings; and self-service password reset. Subsection 5.3 (5 controls) covers Privileged Identity Management and access reviews: privileged roles that are activated rather than permanent, approval for Global Administrator activation, and reviews for guests and privileged roles.
Controls carry a Level 1 or Level 2 profile and an E3 or E5 profile. The risk-based policies, access reviews and Privileged Identity Management controls are mostly tagged E5, so their relevance depends on what your tenant licences. Each control is also marked Automated or Manual in the benchmark; manual ones, such as several of the self-service password reset settings, need verification by hand.
ConfigCobra assesses the section with read-only Microsoft Graph permissions, so there are no agents and no admin password sharing, and the scan returns results in 20 to 25 minutes. Severity per control is a ConfigCobra estimate used to prioritise remediation, since CIS publishes no severity. For each finding you get a copy-paste remediation script (PowerShell) or admin portal steps. Because identity changes are the ones that lock people out, remediation impact analysis uses real tenant data such as sign-in activity and role assignments to list affected users, groups, apps and policies with the effect, for example sign-in blocked or prompted for MFA, before you apply anything.
The inventory adds risk views that line up with this section, among them users with no MFA registered, guests who never signed in, high-privilege app permissions, expired or soon-expiring app credentials and Conditional Access policies not enforced. Scheduled or ad hoc scans, drift alerts when a control regresses and email notifications keep it current, and a read-only auditor seat lets a client or external auditor see the results.
The 63 controls
| CIS ID | Check | Profile | Assessment |
|---|---|---|---|
| 5.1.2.1 | 'Per-user MFA' is disabled | E3 Level 1 | Manual |
| 5.1.2.2 | Users should not be allowed to register third-party applications | E3 Level 1 | Automated |
| 5.1.2.3 | Non-admin users should not be allowed to create tenants | E3 Level 1 | Automated |
| 5.1.2.4 | Access to the Entra admin center is restricted | E3 Level 1 | Manual |
| 5.1.2.5 | The option to remain signed in is hidden | E3 Level 2 | Manual |
| 5.1.2.6 | 'LinkedIn account connections' is disabled | E3 Level 2 | Manual |
| 5.1.3.1 | Users should not be allowed to create security groups | E3 Level 1 | Automated |
| 5.1.3.2 | That 'Restrict user ability to access groups features in My Groups' is set to 'Yes' | E3 Level 2 | Manual |
| 5.1.3.3 | That 'Owners can manage group membership requests in My Groups' is set to 'No' | E3 Level 1 | Manual |
| 5.1.3.4 | Microsoft 365 group creation should be limited to administrators | E3 Level 2 | Automated |
| 5.1.4.1 | The ability to join devices to Entra should be restricted | E3 Level 2 | Automated |
| 5.1.4.2 | Maximum number of devices per user should be limited | E3 Level 1 | Automated |
| 5.1.4.3 | Global Administrators should not be added as local admin during Entra join | E3 Level 1 | Automated |
| 5.1.4.4 | Local admin assignment during Entra join should be restricted | E3 Level 1 | Automated |
| 5.1.4.5 | Local Administrator Password Solution (LAPS) should be enabled | E3 Level 1 | Automated |
| 5.1.4.6 | Users should be restricted from reading BitLocker keys for owned devices | E3 Level 2 | Automated |
| 5.1.5.1 | User consent to apps accessing company data should not be allowed | E3 Level 2 | Automated |
| 5.1.5.2 | The admin consent workflow should be enabled | E3 Level 1 | Automated |
| 5.1.5.3 | Password addition should be blocked for applications | E3 Level 2 | Automated |
| 5.1.5.4 | Password lifetime for applications should not exceed 180 days | E3 Level 1 | Automated |
| 5.1.5.5 | Custom password addition should be blocked for applications | E3 Level 1 | Automated |
| 5.1.5.6 | Certificate lifetime for applications should not exceed 180 days | E3 Level 1 | Automated |
| 5.1.6.1 | Collaboration invitations should be sent to allowed domains only | E3 Level 2 | Automated |
| 5.1.6.2 | Guest user access should be restricted | E3 Level 1 | Automated |
| 5.1.6.3 | Guest invitations should be limited to the Guest Inviter role | E3 Level 2 | Automated |
| 5.1.8.1 | Password hash sync should be enabled for hybrid deployments | E3 Level 1 | Automated |
| 5.2.2.1 | MFA should be required for all users in administrative roles | E3 Level 1 | Automated |
| 5.2.2.2 | MFA should be required for all users | E3 Level 1 | Automated |
| 5.2.2.3 | Legacy authentication should be blocked via Conditional Access | E3 Level 1 | Automated |
| 5.2.2.4 | Sign-in frequency and persistent browser for admins should be enforced | E3 Level 1 | Automated |
| 5.2.2.5 | Phishing-resistant MFA strength should be required for administrators | E3 Level 2 | Automated |
| 5.2.2.6 | Identity Protection user risk policies should be enabled | E5 Level 1 | Automated |
| 5.2.2.7 | Identity Protection sign-in risk policies should be enabled | E5 Level 1 | Automated |
| 5.2.2.8 | Sign-in risk should be blocked for medium and high risk levels | E5 Level 2 | Automated |
| 5.2.2.9 | A managed device should be required for authentication | E3 Level 1 | Automated |
| 5.2.2.10 | A managed device should be required for MFA registration | E3 Level 1 | Automated |
| 5.2.2.11 | Sign-in frequency for Intune enrollment should be set to every time | E3 Level 1 | Automated |
| 5.2.2.12 | The device code sign-in flow should be blocked | E3 Level 1 | Automated |
| 5.2.2.13 | Periodic reauthentication should be required for all users | E3 Level 1 | Automated |
| 5.2.2.14 | Named locations should be defined and trusted | E3 Level 2 | Automated |
| 5.2.2.15 | Exclusionary geographic access controls should be used | E3 Level 2 | Automated |
| 5.2.2.16 | Token protection should be enforced for session tokens | E3 Level 2 | Automated |
| 5.2.2.17 | Authentication transfer should be blocked | E3 Level 1 | Automated |
| 5.2.3.1 | Microsoft Authenticator should be configured to protect against MFA fatigue | E3 Level 1 | Automated |
| 5.2.3.2 | Custom banned passwords should be configured | E3 Level 1 | Automated |
| 5.2.3.3 | Password protection for on-premises AD should be enabled | E3 Level 1 | Automated |
| 5.2.3.4 | All member users should be MFA capable | E3 Level 1 | Automated |
| 5.2.3.5 | Weak authentication methods (SMS, Voice) should be disabled | E3 Level 1 | Automated |
| 5.2.3.6 | System-preferred multifactor authentication should be enabled | E3 Level 1 | Automated |
| 5.2.3.7 | Email OTP authentication method should be disabled | E3 Level 2 | Automated |
| 5.2.3.8 | Account lockout threshold should be 10 or less | E3 Level 1 | Automated |
| 5.2.3.9 | Account lockout duration should be at least 60 seconds | E3 Level 1 | Automated |
| 5.2.3.10 | Microsoft Authenticator on companion applications should be disabled | E3 Level 1 | Automated |
| 5.2.4.1 | 'Self service password reset enabled' is set to 'All' | E3 Level 1 | Manual |
| 5.2.4.2 | That 2 methods are required for password reset | E3 Level 2 | Manual |
| 5.2.4.3 | SSPR registration and authentication re-confirmation are required | E3 Level 1 | Manual |
| 5.2.4.4 | That users are notified on password resets | E3 Level 1 | Manual |
| 5.2.4.5 | All admins are notified when other admins reset their password | E3 Level 1 | Manual |
| 5.3.1 | Privileged role assignments should be activated not permanent | E5 Level 2 | Automated |
| 5.3.2 | Access reviews for guest users should be configured | E5 Level 1 | Automated |
| 5.3.3 | Access reviews for privileged roles should be configured | E5 Level 1 | Automated |
| 5.3.4 | Approval should be required for Global Administrator role activation | E5 Level 1 | Automated |
| 5.3.5 | Approval should be required for Privileged Role Administrator activation | E5 Level 1 | Automated |
Check all 63 controls on your Microsoft 365
ConfigCobra runs this section with the rest of the CIS Microsoft 365 Foundations Benchmark v7.0.0, read-only.