Detections
Analytics
1.1.11 Enable Conditional Access policies to block legacy authentication
Warning! Audit Deprecated
This audit has been deprecated and will be removed in a future update.
View Next Audit VersionInformation
Azure AD supports the most widely used authentication and authorization protocols including legacy authentication. This authentication pattern includes basic authentication, a widely used industry-standard method for collecting user name and password information.The following messaging protocols support legacy authentication:
Authenticated SMTP - Used to send authenticated email messages.
Autodiscover - Used by Outlook and EAS clients to find and connect to mailboxes in Exchange Online.
Exchange ActiveSync (EAS) - Used to connect to mailboxes in Exchange Online.
Exchange Online PowerShell - Used to connect to Exchange Online with remote PowerShell. If you block Basic authentication for Exchange Online PowerShell, you need to use the Exchange Online PowerShell Module to connect. For instructions, see Connect to Exchange Online PowerShell using multifactor authentication.
Exchange Web Services (EWS) - A programming interface that's used by Outlook, Outlook for Mac, and third-party apps.
IMAP4 - Used by IMAP email clients.
MAPI over HTTP (MAPI/HTTP) - Primary mailbox access protocol used by Outlook 2010 SP2 and later.
Offline Address Book (OAB) - A copy of address list collections that are downloaded and used by Outlook.
Outlook Anywhere (RPC over HTTP) - Legacy mailbox access protocol supported by all current Outlook versions.
POP3 - Used by POP email clients.
Reporting Web Services - Used to retrieve report data in Exchange Online.
Universal Outlook - Used by the Mail and Calendar app for Windows 10.
Other clients - Other protocols identified as utilizing legacy authentication.
Rationale:
Legacy authentication protocols do not support multi-factor authentication. These protocols are often used by attackers because of this deficiency. Blocking legacy authentication makes it harder for attackers to gain access.
NOTE: As of October 2022 Microsoft began disabling basic authentication in all tenants, except for those who requested special exceptions it should no longer be available in most tenants beyond Dec 31, 2022. Despite this CIS recommends the CA policy to remain in place to act as a defense in depth measure.
Impact:
Enabling this setting will prevent users from connecting with older versions of Office, ActiveSync or using protocols like IMAP, POP or SMTP and may require upgrades to older versions of Office, and use of mobile mail clients that support modern authentication.
This will also cause multifunction devices such as printers from using scan to e-mail function if they are using a legacy authentication method. Microsoft has mail flow best practices in the link below which can be used to configure a MFP to work with modern authentication:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-microsoft-365-or-office-365
Solution
To setup a conditional access policy to block legacy authentication, use the following steps:Navigate to Microsoft Entra admin center https://entra.microsoft.com/.
Click to expand Azure Active Directory > Protect & secure select Conditional Access.
Create a new policy by selecting New policy.
Set the following conditions within the policy.
Select Conditions then Client apps enable the settings for and Exchange ActiveSync clients and other clients.
Under Access controls set the Grant section to Block access
Under Assignments enable All users
Under Assignments and Users and groups set the Exclude to be at least one low risk account or directory role. This is required as a best practice.
Default Value:
Basic authentication is disabled by default as of January 2023.
See Also
Item Details
Audit Name: CIS Microsoft 365 Foundations E3 L1 v2.0.0
References: CSCv7|9.2
Plugin: microsoft_azure
Control ID: 39b37d533ed70d35b5881b1d90fdb70644056e92def799000639a667750dd486