Account/Authentication - Azure Active Directory - Ensure that Between Two & Four Global Admins are Designated

By Ashwin Venugopal -

 









Summary

It is recommended to designate more than one global administrators, so that a single admin can be monitored easily and the redundancy can be maintained in case the single admin leave an organization. However, not more than four global admins can be set for any tenant and they ideally have no licenses assigned to them.  

Reason

If there is only one global tenant administrator, he or she can easily perform any kind of malicious activity without any possibility of being discovered by another admin, having more than one global administrators ensures that one of their accounts will be successfully breached by an external attacker.

What If?

If there is only one global administrator in a tenant, then, another global administrator will be required to be identified as well as configured, while, for more than four global administrators, a review of role requirements for current global administrators will be needed to identify which of the users want require global administrator access. Hence, the after effect highly depends upon the current number of global administrators configured in the tenant.

How to?

To correct the number of global tenant administrators, use the Microsoft 365 Admin Center:
  1. Log in to https://admin.microsoft.com as a Global Administrator.
  2. Select Users>Active Users.
  3. Now, add the name of the user to be made a Global Administrator in the Search field.
  4. In order to create a new Global Admin:
               1. Select the user's name.
               2. A window will appear to the right.
               3. Select Manage roles.
               4. Select Admin center access.
               5. Check Global Administrator.
               6. Click Save changes.
       5. To remove Global Admins:
               
               1. Select User.
               2. Under Roles select Manage roles.
               3. De-select the appropriate role.
               4. Click Save changes.

To correct the number of global tenant administrators, you can also use the Office 365 PowerShell MSOL:
  1. Connect to Microsoft 365 using Connect-MSOLService.
  2. Run the following PowerShell command to create a new Global Admin- 
    Add-MsolRoleMember -RoleObjectId 62e90394-69f5-4237-9190-012177145e10 - RoleMemberEmailAddress "AdeleV@Contoso.com."
          
          3. Run the following PowerShell command to remove Global Admins:
                 
    Remove-MsolRoleMember -RoleObjectId 62e90394-69f5-4237-9190-012177145e10 - RoleMemberEmailAddress "AdeleV@Contoso.com."

          

    Monitor:

    To verify the number of global tenant administrators, use the Microsoft 365 Admin Center-
    1. Log in to https://admin.microsoft.com as a Global Administrator.
    2. Select Users>Active users.
    3. Select Filter and then choose Global Admins.
    4. Now, review the list of Global Admins to make sure that there are from two to four such accounts.
    To verify the number of global tenant administrators, you can also use the Office 365 PowerShell MSOL:
    1. Connect to Microsoft 365 via Connect-MSOLService.
    2. Run the following PowerShell commands:

    Get-MsolRoleMember -RoleObjectId 62e90394-69f5-4237-9190-012177145e10 


















    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