Account/Authentication - Azure Active Directory - Ensure that Only Organizationally Managed/Approved Public Groups Exist

By Ashwin Venugopal -

 






Summary

Microsoft 365 Groups is the foundational membership service that drives all teamwork across Microsoft 365 and can provide a group of people access to a collection of shared resources. Although, there are various types of group types, this recommendation is concerned with Microsoft 365 Groups.

In the Administration panel, when a group is created, the default privacy value is "Public".

Reason

As the heading suggests, this one will make sure that only organizationally managed and approved public groups exist and when a group has "Public" privacy, users may easily access data related to this group (like SharePoint), via 3 methods:
  1. By using the Azure portal, and adding themselves into the public group.
  2. By requesting access to the group from the Group application of the Access Panel.
  3. By accessing the SharePoint URL.

Administrators are generally notified whenever a user uses Azure portal. Requesting access to the group, forces the users to send a message to group owner, so that they have immediate access to the group. The SharePoint URL is usually guessable, and can be found from the Group application of the Access Panel. If group privacy is not controlled, any user may access sensitive information, according to the group they try to access.

NOTE- Public in this case means public to the identities within the organization.

What If?

After applying the recommendation, the group owners could receive more access requests than usual, especially regarding groups originally meant to be public.

How to?

In the Microsoft 365 Administration portal, go to:
  1. Teams and groups
  2. Active teams and groups
  3. Select a Public group
  4. Go to 'Settings'
  5. Set Privacy to 'Private'

Monitor:

Using the Microsoft 365 Administration portal:
In the Microsoft 365 Administration portal, go to:
  1. Teams and groups
  2. Active teams and groups
  3. Check that no groups have the status  'Public' in the privacy column.

Using the Microsoft.Graph powerShell module:

To get the list of public groups, run the following:

Connect-Graph -Scopes "Group.Read.All"
Get-MgGroup | where ($_.Visibility -eq "Public") | select
DisplayName, Visibility
































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