Skip to content
StrikeOps

Security Defaults Disabled With No Conditional Access

HighTypical severity Cloud and Microsoft 365CWE-308ATT&CK T1078.004

01Description

Microsoft Entra ID Security Defaults had been turned off, and no Conditional Access policies had been configured to replace them. The tenant therefore had no centrally enforced requirement for multi-factor authentication and no block on legacy authentication protocols.

02Impact

Without Security Defaults or Conditional Access, MFA depends on individual user choices and legacy protocols remain available. A single guessed, sprayed or phished password is often enough to take over an account, including administrator accounts, and attackers actively target tenants in this state.

03Severity

Typically

High

Typically High. High by default, because the tenant is left with no baseline MFA or legacy authentication blocking. Critical where administrator accounts can sign in with a password alone.

04How to verify

  1. 1In the Entra admin center, open Identity > Overview > Properties > Manage security defaults and confirm the setting is Disabled.
  2. 2Review Protection > Conditional Access > Policies and confirm no enabled policies require MFA or block legacy authentication (report-only policies do not enforce anything).
  3. 3Optionally query the setting with Microsoft Graph PowerShell: Get-MgPolicyIdentitySecurityDefaultEnforcementPolicy, and check the IsEnabled value.

Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.

05Remediation

  1. 1If the tenant has no Entra ID P1 licensing, re-enable Security Defaults: Identity > Overview > Properties > Manage security defaults > Enabled.
  2. 2If the tenant has Entra ID P1 or higher (for example through Microsoft 365 Business Premium or E3), build Conditional Access policies that require MFA for all users and block legacy authentication, then confirm they are On rather than Report-only.
  3. 3Exclude only documented emergency access accounts from these policies.
  4. 4Re-check sign-in logs after the change to confirm no sign-ins are completing with single-factor authentication.

06References

Draft findings like this from your own evidence

Book a demo
Book a demo