Skip to main content
Five Steps for Cloud Compliance Readiness·A practical playbook for security teamsDownload
CIS Microsoft 365 Foundations v7.0.0 · Section 5

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.

63controls
45Level 1
18Level 2
52automated

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 IDCheckProfileAssessment
5.1.2.1'Per-user MFA' is disabledE3 Level 1Manual
5.1.2.2Users should not be allowed to register third-party applicationsE3 Level 1Automated
5.1.2.3Non-admin users should not be allowed to create tenantsE3 Level 1Automated
5.1.2.4Access to the Entra admin center is restrictedE3 Level 1Manual
5.1.2.5The option to remain signed in is hiddenE3 Level 2Manual
5.1.2.6'LinkedIn account connections' is disabledE3 Level 2Manual
5.1.3.1Users should not be allowed to create security groupsE3 Level 1Automated
5.1.3.2That 'Restrict user ability to access groups features in My Groups' is set to 'Yes'E3 Level 2Manual
5.1.3.3That 'Owners can manage group membership requests in My Groups' is set to 'No'E3 Level 1Manual
5.1.3.4Microsoft 365 group creation should be limited to administratorsE3 Level 2Automated
5.1.4.1The ability to join devices to Entra should be restrictedE3 Level 2Automated
5.1.4.2Maximum number of devices per user should be limitedE3 Level 1Automated
5.1.4.3Global Administrators should not be added as local admin during Entra joinE3 Level 1Automated
5.1.4.4Local admin assignment during Entra join should be restrictedE3 Level 1Automated
5.1.4.5Local Administrator Password Solution (LAPS) should be enabledE3 Level 1Automated
5.1.4.6Users should be restricted from reading BitLocker keys for owned devicesE3 Level 2Automated
5.1.5.1User consent to apps accessing company data should not be allowedE3 Level 2Automated
5.1.5.2The admin consent workflow should be enabledE3 Level 1Automated
5.1.5.3Password addition should be blocked for applicationsE3 Level 2Automated
5.1.5.4Password lifetime for applications should not exceed 180 daysE3 Level 1Automated
5.1.5.5Custom password addition should be blocked for applicationsE3 Level 1Automated
5.1.5.6Certificate lifetime for applications should not exceed 180 daysE3 Level 1Automated
5.1.6.1Collaboration invitations should be sent to allowed domains onlyE3 Level 2Automated
5.1.6.2Guest user access should be restrictedE3 Level 1Automated
5.1.6.3Guest invitations should be limited to the Guest Inviter roleE3 Level 2Automated
5.1.8.1Password hash sync should be enabled for hybrid deploymentsE3 Level 1Automated
5.2.2.1MFA should be required for all users in administrative rolesE3 Level 1Automated
5.2.2.2MFA should be required for all usersE3 Level 1Automated
5.2.2.3Legacy authentication should be blocked via Conditional AccessE3 Level 1Automated
5.2.2.4Sign-in frequency and persistent browser for admins should be enforcedE3 Level 1Automated
5.2.2.5Phishing-resistant MFA strength should be required for administratorsE3 Level 2Automated
5.2.2.6Identity Protection user risk policies should be enabledE5 Level 1Automated
5.2.2.7Identity Protection sign-in risk policies should be enabledE5 Level 1Automated
5.2.2.8Sign-in risk should be blocked for medium and high risk levelsE5 Level 2Automated
5.2.2.9A managed device should be required for authenticationE3 Level 1Automated
5.2.2.10A managed device should be required for MFA registrationE3 Level 1Automated
5.2.2.11Sign-in frequency for Intune enrollment should be set to every timeE3 Level 1Automated
5.2.2.12The device code sign-in flow should be blockedE3 Level 1Automated
5.2.2.13Periodic reauthentication should be required for all usersE3 Level 1Automated
5.2.2.14Named locations should be defined and trustedE3 Level 2Automated
5.2.2.15Exclusionary geographic access controls should be usedE3 Level 2Automated
5.2.2.16Token protection should be enforced for session tokensE3 Level 2Automated
5.2.2.17Authentication transfer should be blockedE3 Level 1Automated
5.2.3.1Microsoft Authenticator should be configured to protect against MFA fatigueE3 Level 1Automated
5.2.3.2Custom banned passwords should be configuredE3 Level 1Automated
5.2.3.3Password protection for on-premises AD should be enabledE3 Level 1Automated
5.2.3.4All member users should be MFA capableE3 Level 1Automated
5.2.3.5Weak authentication methods (SMS, Voice) should be disabledE3 Level 1Automated
5.2.3.6System-preferred multifactor authentication should be enabledE3 Level 1Automated
5.2.3.7Email OTP authentication method should be disabledE3 Level 2Automated
5.2.3.8Account lockout threshold should be 10 or lessE3 Level 1Automated
5.2.3.9Account lockout duration should be at least 60 secondsE3 Level 1Automated
5.2.3.10Microsoft Authenticator on companion applications should be disabledE3 Level 1Automated
5.2.4.1'Self service password reset enabled' is set to 'All'E3 Level 1Manual
5.2.4.2That 2 methods are required for password resetE3 Level 2Manual
5.2.4.3SSPR registration and authentication re-confirmation are requiredE3 Level 1Manual
5.2.4.4That users are notified on password resetsE3 Level 1Manual
5.2.4.5All admins are notified when other admins reset their passwordE3 Level 1Manual
5.3.1Privileged role assignments should be activated not permanentE5 Level 2Automated
5.3.2Access reviews for guest users should be configuredE5 Level 1Automated
5.3.3Access reviews for privileged roles should be configuredE5 Level 1Automated
5.3.4Approval should be required for Global Administrator role activationE5 Level 1Automated
5.3.5Approval should be required for Privileged Role Administrator activationE5 Level 1Automated

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.

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