Sentinel POC- Architecture and Recommendations For MSSPs (Part 1)

By Ashwin Venugopal -

 



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






MSSP Architecture Goal

The following diagram provides the overview of the typical architecture an MSSP partner should build to evaluate Sentinel's capabilities. Sentinel is configured at the core in the Log Analytics Workspace (LAW), and both of them exists in a resource group within a subscription. MSSPs will deploy these resources associated with the MSSP tenant, to gain access to MSSP's customers' resources via Azure Lighthouse.

Tenants and Subscriptions for the Sentinel POC in the Context of an MSSP

Tenants- A tenant will be required that will work as the MSSP tenant and at least one tenant that can work as the customer's tenant. Although, Microsoft Sentinel and its associated LAW are subscription resources, but, they must be associated with a tenant.

Subscriptions- A subscription within the MSSP tenant and at least one subscription within each of customer tenants is required. It is needed because LAW, used for data ingestions, and Sentinel, which is a service deployed on a LAW, are both resources can only exist within a subscription.

Considerations:

  • Which tenant will be the MSSP tenant? Partners with POC are free to choose their corporate tenant as their MSSP tenant, but, ultimately the MSSP tenant should be isolated using multiple identity model, else new tenant should be created. However, if only Sentinel's features are being tested for a period of time, then, the single identity model or the corporate tenant will be enough to do so.

  • Are there any options or credits to cover the costs of tenants/subscriptions? CDX environments cannot be used because it has some restrictions that does not allow anyone to add payment instruments required to create a new subscription. However, a Visual Studio subscription, offered as a part of the Developer Program, can be attached to one of those tenants. The program provides a Microsoft 365 developer sandbox, which can be the MSSP tenant as well. Hence, partners can combine Visual studio subscription and Microsoft 365 developer sandbox, resulting in a tenant and subscription with the costs covered by the developer program. This is very useful because the partners will get an E5 license with that tenant, allowing them to test scenarios using some of the Defender 365 Security services. 

  • Free trial- New workspaces can ingest up to 10GB/day of log data for the first 31-days at no cost. Both Log Analytics data ingestion and Microsoft Sentinel charges are waived during this trial period. It is subject to a 20 workspace limit per Azure tenant.

  • Which region?- Various elements should be considered while evaluating the region where the Log Analytics Workspace can be created, like egress costs, feature availability, compliance requirements, etc. There is a decision tree available in the documentation that can guide partners when making these decisions. 

  • An isolated subscription- Microsoft recommends the Sentinel workspace be placed on a separate subscription or a separate management group, so that the permissions of the security data can be isolated preventing them from being inherited.



    




To read part 2, please click here
To read part 3, please click here
To read part 4, please click here
To read part 5, 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