Auditing - Ensure The User Role Group Changes Are Reviewed At Least Weekly

By Ashwin Venugopal -

 












Summary

Role-based Access Control allows the users to be assigned according to their roles within an organization. It's more manageable form of access control that is less prone to errors. These user roles can be audited inside of Microsoft Purview to provide a security auditor insight into user privilege change.

Reason

By reviewing weekly, one can easily identify the right changes required in an organization and largely maintaining the Least Privilege and preventing Privilege creep. Insider Threats, either intentional or unintentional can occur when a user has higher than needed privileges and if accountability of role membership is maintained, then, it will keep the Insiders and malicious actors limited in the scope of potential damaging activities.

What If?

Enabling this setting will require the Administrators assigning rights to users, to justify the changes to the security auditors. Documentation including detailed policies, procedures, and change requests will need to be considered in order to keep a secure organization functioning within its planned operational level.

How to?

To review user role group changes, perform the following steps using the Microsoft 365 Admin Center:
  1. Under Admin Centers click on Compliance to be redirected to Microsoft Purview.
  2. Click on Audit then select Search.
  3. In Activities find Added member to Role under the Role administration activities section.
  4. Now, set Start date and End date.
  5. Click Search.
  6. Review.

To review user role group changes, perform the following steps using the Exchange Online PowerShell Module:
  1. Connect to Exchange Online using Connect-ExchangeOnline.
  2. Now, run the following Exchange Online PowerShell command: 

    3. $startDate = ((Get-Date) .AddDays (-7)) .ToShortDateString ()
    $endDate = ((Get-Date) .ToShortDateString ()
Search-UnifiedAuditLog -StartDate $startDate -EndDate $endDate | Where-Object
{ $_.Operations -eq "Add member to role." }

      3. Review the output

Monitor:

To verify user role group changes are being reviewed at least weekly, confirm that the necessary procedures are in place and being followed.












































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