Skip to content
StrikeOps

Legacy Authentication Enabled in Microsoft 365

HighTypical severity Cloud and Microsoft 365CWE-287ATT&CK T1110.003

01Description

Legacy authentication protocols, such as IMAP, POP3, SMTP AUTH and older Exchange ActiveSync clients, were not blocked for the Microsoft 365 tenant.

02Impact

Legacy protocols do not support modern authentication and so cannot enforce MFA. Attackers use them for password spraying because a correct password grants access even where MFA is configured for browser sign-ins.

03Severity

Typically

High

Typically High. High, as legacy protocols bypass MFA. Lower only where all legacy protocols are already disabled at the tenant and mailbox level.

04How to verify

  1. 1Review Conditional Access policies for a rule blocking legacy authentication clients.
  2. 2Review Entra ID sign-in logs for legacy authentication usage.
  3. 3Check SMTP AUTH and protocol settings at tenant and mailbox level.

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. 1Create a Conditional Access policy that blocks legacy authentication for all users.
  2. 2Disable SMTP AUTH, IMAP and POP3 where they are not required, at tenant and mailbox level.
  3. 3Migrate any remaining applications to modern authentication.

06References

Draft findings like this from your own evidence

Book a demo
Book a demo