Account/Authentication - Azure Active Directory - Ensure Multifactor Authentication is Enabled for All Users in All Roles

By Ashwin Venugopal -

 








Summary

In order to enable multifactor authentication for all users in the Microsoft tenant 365, they will be prompted to authenticate with a second factor, which is generally a text message to a registered mobile number where they type in an authorization code, or with a mobile application like Microsoft Authenticator,  after logging in to the Microsoft 365 services

Reason

MFA generally requires an individual to present at least two separate forms of authentication before granting access, can offer extra assurance about the identity of the individual trying to get access, which further requires for an attacker to compromise minimum two different authentication mechanisms, that not only increases the compromise difficulty level, but also, reduces the risks.

What If?

If MFA is implemented for all users in administrative roles, it will permanently change the users' routine as they will have to enroll in MFA via phone, SMS, or an authentication application. After that MFA will always be needed for all the future access to the environment.

How to?

  1. Log in to https://admin.microsoft.com as a Global Administrator.
  2. Go to Admin Centers and click on Azure Active Directory.
  3. Select Enterprise Applications then, under Security, choose Conditional Access.
  4. Click on New policy.
  5. Go to Assignments>Users and groups>Include> Select All users (do not exclude any user).
  6. Now, got to Cloud apps or actions>Cloud apps>All cloud apps (without excluding any apps).
  7. Under Access control>Grant > select Grant access> to check Require multi-factor authentication (and nothing else).
  8. Leave all the other conditions blank.
  9. Ensure the policy is enabled/On.
  10. Create.

Monitor:

To verify the MFA configuration for all users, use the Microsoft 365 Admin Center-
  1. Log in to https://admin.microsoft.com as a Global Administrator.
  2. Go to Admin Centers and click on Azure Active Directory.
  3. Select Enterprise Applications then, under Security, choose Conditional Access.
  4. Now, review the list of policies and make sure that there is a policy that requires the Grant access control with Require multi-factor authentication for All users under Users and groups.
To verify the MFA configuration for administrators, use the Microsoft 365 SecureScore service:
  1. Log in to the Secure Score portal (https://security.microsoft.com) with the help of admin permission for an Office 365 Enterprise, Microsoft 365 Business, or Office 365 Business Premium subscription. 
  2. Click on Ensure all users can complete multi-factor authentication for secure access recommended action to check MFA for all users.
  3. It will show the number of users who do not have MFA configured.  









































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