Getting Started with Microsoft Sentinel- Access Microsoft Sentinel

 





Overview

Generally, users with an access to Microsoft Sentinel workspace, also have access to all the other data resources. However, there might be some users who require access to selective data only. Hence, it is recommended to configure role-based access control (RBAC), which is also known as setting up resource-context RBAC. 

Scenarios For Resource-Context RBAC

The following are the scenarios in which resource-context RBAC can be of most help:

Requirement Type

SOC Team

Non-SOC Team

Permissions

The entire workspace

Specific resources only

Data Access

All data in the workspace

Only data for resources that the team is authorized to access

Experience

The full Microsoft Sentinel experience, possibly limited by the functional permissions assigned to the user

Log queries and workbooks only

 Resource-context RBAC is a good solution for the similar access requirements to the non-SOC team.


Alternative Methods For Implementing Resource-Context RBAC

Resource-context RBAC might not offer a full solution. Hence, the following table lists the scenarios for other solutions for data access:

Scenario

Solution

A subsidiary has an SOC team that requires a full Microsoft Sentinel experience.

Here, a multi-workspace architecture to separate the data permissions.

Required o provide access to a special type of event.

In this case, table-level RBAC can be used to define permissions for each table.

Limit access to a more granular level, either not based on the resource, or to only a subset of the fields in an event,

Access can be offered to data via built-in integration with Power BI dashboards and reports.

 

Explicitly Configure Resource-Context RBAC

To explicitly configure resource-context RBAC:
  • Resource-context RBAC should be enabled in Azure monitor.
  • A resource group should be created for each users team, who requires access to some resources, not the entire Microsoft Sentinel environment. 
  • Now, resource can be assigned and events can be tagged with relevant resource IDs, to the created resource team groups

When the data is sent to Microsoft Sentinel, the log records are automatically tagged with the resource ID of the data source. 











Comments

Popular posts from this blog

Query, Visualize, & Monitor Data in Azure Sentinel

Planning for Implementing SAP Solutions on Azure (Part 2 of 5)

Work with String Data Using KQL Statements