Getting Started with Microsoft Sentinel- Access Microsoft Sentinel

By Ashwin Venugopal -

 





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

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