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

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 6, please click here





Storage Options

The default storage option for Sentinel ingestion is Analytics table whose retention time can be adjusted for all tables within the workspace or individually per table. A different cost efficient plan can also be used which is called Basic which has interactive retention of 8 days. However, it does have some restrictions, like- not able to trigger alerts and limited KQL commands. This tables are meant to be used with noisy logs, such as firewall logs or flow logs, and are normally used for debugging or troubleshooting purposes. 

A total retention can be set for both Analytic and Basic tables by configuring a total retention period, after which the data will be moved to Archive completing the retention period. The total retention is maximum 7 years. Search feature can be useful to query and rehydrate data from Archive as and when needed.

All these options above are readily available in Log Analytics Workspace, but some of the external storage options are- Blob Storage and Azure Data Explorer (ADX). Blob storage can be queried via externaldata operator in KQL, which can also be used within an analytic rule. Besides, ADX and Blob Storage can be combined and an external table can be created in ADX pointing the whole container.

Following is the summary of various storage options available currently:



Update: Workspace Manager

It is new feature introduced recently. It allows MSSPs to configure the MSSP workspace to act as the parent or grandparent of various other workspaces, typically customer workspaces. However, Workspace Manager still depends on Azure Lighthouse, which is essential to be able to configure workspaces managed from a central MSSP workspace. Workspace Manager can help an MSSP in publishing content to the child workspaces. 

This feature allows MSSPs to group customer workspaces depending on their requirements. For example, healthcare customers may have different analytic rule and workbook requirements than education customers; hence, MSSPs can group them and publish different content to each of those workspaces. Since workspaces can be a [art of different groups, contents from different groups to the same workspace can be published. An ideal MSSP solution should include a combination of both Repositories and Workspace Manager.










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 6, 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