Create & Manage Azure Sentinel Workspaces

By Ashwin Venugopal -

 



Plan for the Azure Sentinel Workspace 

You can install the Azure Sentinel solution in Log Analytics Workspace, whose implementation is mostly focused on the Log Analytics Workspace creation. The only important option when creating a new log on the Log Analytics Workspace is the region which specifies the location where the log data will reside. The three implementation options are:   

  • Single-Tenant with a single Azure Sentinel Workspace
  • Single-Tenant with regional Azure Sentinel Workspace
  • Multi-Tenant

Single-tenant single workspace

This workspace can receive logs from resources in other regions within the same tenant. Generally the log data (when collected) always travel across different regions and stored in another region, which creates two possible concerns- first, it can incur a bandwidth cost. Second, if there is a data governance requirement to keep data in a specific region, then the single workspace option would not be an implementation option. Its pros and cons includes:

Pros

Cons

Central Pane of Glass

May not meet Data Governance Requirement.

Consolidates all security logs and information

Can incur bandwidth cost for cross region.

Easier to query all information

 

Azure Log Analytics RBAC to control data access

 

Azure Sentinel RBAC for service RBAC

 

 Single-tenant with regional Azure Sentinel Workspaces

It contains multiple Sentinel workspaces which requires the creation and configuration of multiple Azure Sentinel and Log Analytics Worspaces. Its pros and cons are:

Pros

Cons

No cross-region bandwidth costs

No central pane of glass. You are not looking in one place to see all the data.

Maybe required to meet Data Governance requirements

Analytics, workbooks, etc. must be deployed multiple times.

Granular data access control

 

Granular retention settings

 

Split billing

 


 Multi-tenant workspaces

If you are want to manage an Azure Sentinel workspace, outside your tenant, then using multi-tenant workspaces using Azure Lighthouse is the correct choice whose configuration can grant you access to the tenants. The tenant configuration  within the tenant is the same considerations before.

Azure Sentinel Permissions & Roles

Azure Role-based Access Control (RBAC) is the authorization system that manages access to Azure resources and it is built on Azure Resource Manager, which is capable of providing fine-grained access management of Azure resources. It also allows you to grant appropriate access to Azure Sentinel and different roles to give you specific control over what users of Azure Sentinel can access and do. 

Azure Sentinel-specific roles

The following are the three dedicated, built-in Azure Sentinel roles:
  • Reader- This role can review data, incidents, workbooks, and other Azure Sentinel resources.
  • Responder- This role has all the permissions of the Reader role. Plus, it can manage incidents by assigning or dismissing them.
  • Contributor- This role has all the permissions of the Reader and Responder roles. Also, it can create and edit workbooks, analytics rules, and other Azure Sentinel resources.

 All the built-in Azure Sentinel roles grant read access to the data in your Azure Sentinel Workspace and can apply to all the resources that deploy to support Azure Sentinel, if those resources are in the same resource group. 

Azure Roles & Azure Monitor Log Analytics Roles

These roles includes access to your Azure Sentinel workspace and other resources. Azure roles grants access across all your Azure resources, including Log Analytics workspaces and Azure Sentinel Resources- Owner, Contributor, and Reader. 

Log Analytics roles grants access across all your Log Analytics workspaces- Log Analytics Contributor, and Azure Sentinel Resources. 

Custom Roles & Advanced Azure RBAC

If the built-in Azure roles doesn't meet the specific needs of your organization, your own custom roles can also be created. Similar to the built-in roles, they allow you to assign custom roles to users, groups, and service principles for management-group, subscription, as well as resource-group scopes. 













Comments

Post a Comment

Popular posts from this blog

Query, Visualize, & Monitor Data in Azure Sentinel

By Ashwin Venugopal -
Image
  Azure Sentinel Workbooks Several ready for use templates are provided by the Azure Sentinel that can be used to create your own workbook and then modify them as needed for Contoso. Most of the data connectors it uses to ingest data come with their own workbooks, but better insight can be obtained by simply looking into the data that is being ingested by using tables and visualizations, including bar and pie charts. You can also make your own workbook easily by using this data from the beginning instead of using the predefined templates. Workbook Page You can easily access the workbook page from the Azure Sentinel from the navigation pane which consists of the: Workbook header- You can add a new workbook and review the saved workbooks as well as templates that are available on the workbook page. Templates section- You can access existing workbook templates on the Templates tab. You can save some of the workbooks for quick access and they will appear on the My Workbooks tab.  From the
Read more

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

By Ashwin Venugopal -
Image
  To read part 1 please click  here To read part 3 please click  here To read part 4 please click  here To read part 5 please click  here Load Balancing The load balancer uses probe ports to determine as well as route the traffic to an active DBMS node, but of there's any failover then the most common SAP application architecture can automatically reconnect against the private virtual IP address without the need for the SAP application to reconfigure it, while the load balancer redirect the traffic against the private virtual IP address without any need for the SAP application to reconfigure. The loaf balancer also offers an option of DirectServerReturn which if configured, can help in directing the traffic from the DBMS VM to the SAP application layer directly to the application layer without routing through the load balancer. But, if it isn't configured, then the return traffic to the SAP application layer is routed through the load balancer. You can also use Azure Load Balan
Read more

Work with String Data Using KQL Statements

By Ashwin Venugopal -
Image
  Extract Data from Unstructured String Fields Unstructured string fields often contains the Security log data and requires parsing to extract data. There are multiple ways of pulling information from string fields in KQL and the two primary operators used are extract and parse.  Extract It gets a match for a regular expression from a text string. You can convert the extracted substring to the indicated type.  Arguments regex- A regular expression. captureGroup- A positive int constant indicating the capture group to extract. 0 stands for the entire match, 1 for the value matched by the first '('parenthesis')' in the regular expression, 2 or more for subsequent parenthesis.  text- A string to search. typeLiteral- An optional type literal. If provided, the extracted substring is converted to this type.  Returns If regex finds a match in text- the substring matched against the indicated capture group captureGroup, optionally converted to typeLiteral. If there's no mat
Read more