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

By Ashwin Venugopal -

 








Summary

Enabling the multifactor authentication for all users who are also the members of administrative roles in the Microsoft 365 tenant includes roles like:
  1. Global Administrator
  2. Billing Administrator
  3. Exchange Administrator
  4. SharePoint Administrator
  5. Password Administrator
  6. Skype for Business Administrator
  7. Service Support Administrator
  8. User Administrator
  9. Dynamics 365 Service Administrator
  10. Power BI Administrator

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, reduce 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 users and groups> and check Directory roles.
  6. At least, select the following roles: Billing admin, Conditional Access admin, Exchange admin, Global admin, Helpdesk admin, Security admin, SharePoint admin, and User admin.
  7. Now, got to Cloud apps or actions>Cloud apps>Include> and choose All cloud apps (without excluding any apps).
  8. Under Access control>Grant > select Grant access> to check Require multi-factor authentication (and nothing else).
  9. Leave all the other conditions blank.
  10. Ensure the policy is enabled.
  11. Create.

Monitor:

To verify the MFA configuration for administrators, 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 the appropriate Directory roles 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 Require MFA for Azure AD privileged roles policy to check MFA for admin users.
  3. It will show the number of Admin 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...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
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...
Read more