Account/Authentication - Azure Active Directory - Enable Conditional Access Policies to Block Legacy Authentication

By Ashwin Venugopal -

 









Summary

Use Conditional Access to block legacy authentication protocols in Office 365. 

Reason

Since legacy authentication don't support MFA, they are often used by attackers for malicious purposes. Hence, if we block legacy authentication, it will make it very difficult for attackers to gain access.

What If?

This setting, if enabled, 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 supports modern authentication.  

How to?

To setup a conditional access policy to block legacy authentication, use the following steps:
  1. Login to https://admin.microsoft.com as a Global Administrator.
  2. Go to Admin centers and click on Azure Active Directory.
  3. Select Azure Active Directory and then Security.
  4. Select Conditional Access.
  5. Now, create a new policy by choosing New Policy.
  6. Set the below 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 the best practice.                                

Monitor:

To verify that legacy authentication is blocked, use the Microsoft 365 Admin Center:
  1. Login to https://admin.microsoft.com as a Global Administrator.
  2. Go to Admin centers and click on Azure Active Directory.
  3. Select Azure Active Directory and then Security.
  4. Select Conditional Access.
  5. Now, verify that either the policy Baseline policy: Block legacy authentication is set to On or find another with the following settings enabled-                 

    • 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 the best practice.   























































Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different groups of computers, re
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning of alert rule parameter
Read more

Design Planning (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Complex Organizational Structures SIEM can be an expensive security control, hence, it is common multiple businesses to contribute to the overall expense. Various organizational units may require a level of access to specific dashboards or sets of data. Microsoft Sentinel offers the ability to assign table-level permissions and limit the level of access to the minimum required to perform requisite job functions.  Role-based Access Control (RBAC) Requirements Microsoft Sentinel offers an extensive list of Azure built-in roles that can be used to provide granular access according to the job requirements and permitted level of access. Some of them are various Microsoft Sentinel dedicated roles: Microsoft Sentinel Contributor- Can perform all engineering-related configuration, such as creating alert rules, configuring data connectors, and additional similar tasks.  Microsoft Sentinel Reader- Can query the log data stor
Read more