Design Planning (Part 1)

By Ashwin Venugopal -

 



To read part 2, please click here
To read part 3, please click here



Data Residency Requirements

According to the type of business and customer residency, organizations might have compliance restrictions related to the logged data. These compliance regulations may not be defined clearly with respect to logging requirements and subject to change with time. Hence, organizations may choose local region to avoid complications.

The selection of a region also carries implications for Microsoft Sentinel and Log Analytics costs as well as the availability of resources for the specific region. Regions like the U.S. can offer a significant cost advantage in comparison to other regions. The discount can be significant depending upon the volume of log ingestion. Therefore, the project team should obtain organizational requirements related to data residency before deploying.

Number of Azure AD Tenants

An Azure AD tenant offers Identity and Access Management (IAM) capabilities for applications and resources used within an organization. Most of the organizations have single Azure AD tenant, but some might have more than one due to mergers and acquisitions or they might need to segregate environments such as corporate versus production infrastructure. 

Each Azure tenant requires a separate Microsoft Sentinel instance because some of the data connectors may only work within the current Azure tenant. So, solutions based on custom connectors and Azure REST APIs can be developed to aggregate remote tenant logs into a single Microsoft Sentinel instance. However, these solutions might create an unnecessary level of complexity and increased maintenance that should be avoided unless otherwise. Azure Lighthouse can provide cross-tenant management experience for unified platform tooling, management at scale, and increased visibility. 

Number of Azure Subscriptions

A single Microsoft Sentinel instance can integrate data from multiple Azure subscriptions. But some security or operational solutions may have restrictions on their logging capabilities that limits the sending of logging/diagnostics data to different subscriptions. Such solutions requires a custom connector that can be configured with the help of many methods. 

Microsoft Sentinel can be deployed in existing subscriptions or in its own subscription without any implications for its functionality. A dedicated subscription is recommended in following situations:

  • There is a need to clearly identify or segregate any costs associated with Microsoft Sentinel. 

  • Permissions needed to be assigned at the subscription level to allow the creation and management of various resources required for a full Microsoft Sentinel configuration. However, for complex environment this cloud be VMs, function apps, automation accounts, storage accounts, data explorer clusters, key vaults, machine learning, and databases. 
If Microsoft Sentinel is deployed in multiple subscriptions, access can be managed centrally through regular assignment of Azure AD roles. Azure Lighthouse is not required here because it is designed to offer cross-tenant access. 

Conclusion

Here are the key factors that can affect the initial architecture for deployments of new Microsoft Sentinel instances or the migration from existing SIEM platforms. 




To read part 2, please click here
To read part 3, please click here












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