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

Security defaults should be enabled in Microsoft Entra ID

  • Level 1
  • Identity Services

This check looks at whether the security defaults setting is switched on in the Microsoft Entra tenant that sits behind your Azure subscriptions. The safe setting is for it to be enabled, so MFA is required and legacy sign-in protocols are blocked, unless you replace it with your own Conditional Access policies that cover the same ground.

Why it matters

Security defaults are a bundle of preconfigured identity protections from Microsoft. Once enabled, every user has to register for multifactor authentication, administrators are asked for MFA on every sign-in, legacy authentication protocols are blocked, device code flow is blocked, and access to Azure Resource Manager (the Azure portal, Azure PowerShell and Azure CLI) requires MFA.

Legacy protocols such as IMAP, POP3 and SMTP basic authentication cannot do MFA at all, so an attacker with a guessed or phished password can use them to walk around an MFA policy. Microsoft's own guidance describes security defaults as a baseline for organisations that do not have more advanced Conditional Access in place. If your tenant already enforces equivalent Conditional Access policies, security defaults must be off, and that is a valid state as long as the same protections exist.

Source: Microsoft Learn, Configure Security Defaults for Microsoft Entra ID.

How to check it yourself

In the Microsoft Entra admin center go to Entra ID > Overview > Properties and select Manage security defaults. The toggle shows Enabled or Disabled. You need at least the Conditional Access Administrator role to open it.

A read-only way to see the same value with Microsoft Graph PowerShell (read scope only):

Connect-MgGraph -Scopes "Policy.Read.All"
Get-MgPolicyIdentitySecurityDefaultEnforcementPolicy | Select-Object IsEnabled

If the result is False, check Entra ID > Conditional Access > Policies to confirm that your own policies require MFA for all users and administrators and block legacy authentication. Try this in a test tenant first if you are unsure what the cmdlet returns for your setup.

How to fix it

First, make sure no administrator or service still depends on legacy authentication, because those sign-ins stop working once the setting is on. Then:

  • Sign in to the Microsoft Entra admin center as at least a Conditional Access Administrator.
  • Browse to Entra ID > Overview > Properties and select Manage security defaults.
  • Set Security defaults to Enabled and select Save.

Microsoft also recommends that administrators revoke existing sign-in sessions after enabling it so everyone is prompted to register for MFA. For one account that can be done with Revoke-MgUserSignInSession -UserId <user>, which changes that user's sessions, so run it deliberately and not as part of a check. ConfigCobra itself never changes the tenant: it reports the finding and gives you these steps or a script to run yourself.

What changes when you fix it

Every user is asked to register for the Microsoft Authenticator app the next time they sign in, so expect a short burst of help-desk questions and send a heads-up to staff first. Administrators are prompted for MFA at each sign-in.

Anything that signs in with a legacy protocol stops working: older Office clients, scanners or applications that send mail with basic authentication, and apps that rely on device code flow. Make sure your emergency access accounts are set up before you switch it on, so nobody gets locked out. Security defaults cannot be customised, and they cannot be combined with Conditional Access policies, so organisations that need exceptions should move to Conditional Access instead.

Included in

BenchmarkCIS IDProfile
CIS Microsoft Azure Foundations v6.0.05.1.1Level 1

Check this on your Microsoft Azure

ConfigCobra runs this check with every other control of the CIS Microsoft Azure Benchmarks, 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