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

By Ashwin Venugopal -

 





To read part 1, please click here
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




Cross-Workspace

Since, artifacts can exist on both MSSP and customer workspaces, it is easier to keep the ones having intellectual property within MSSP workspace only. The following options shows how can they be used to access customers' data:
  • Multiple workspace incident view- This view is available as soon as the customers delegate access using Azure Lighthouse or if there are multiple workspaces within the tenant.

  • Cross workspace querying- Multiple workspaces can be queried through the Logs blade using the workspace() expression and the union operator.

  • Cross workspace analytic rules- Partners can create analytic rules that include up to 20 workspaces in the query. Most analytic rules run on the customer's workspace, but this option is for cases where a cross workspace analytic rule is needed. 

  • Cross workspace workbooks- There are various Content hub solutions that include workbooks that can query data across workspaces and partners can also create their own. For example, the Incident Overview workbook and the Microsoft Sentinel Cost workbook that allow partners to view this data across their customers' workspaces, as long as they have access. 

  • Cross workspace hunting- It is same as querying through the Logs blade, partners can also save those queries to hunt later.

Other Resources

A list of links is included to help partners that are ramping up with Microsoft Sentinel, which is -  https://aka.ms/SentinelLinks. However, this list is constantly updated and include all sorts of information including training links to the various Ninja trainings, and other additional links on more advanced subjects, such as UEBA, Fusion, SOAR automation, etc.







To read part 1, please click here
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