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

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




Agents and Forwarders

Since, the Log Analytics Agent will be retired till August 2024, the new Azure Monitor Agent (AMA), which is a consolidation of all agents, will replace it along with the Telegraf agent and the Diagnostics extension. AMA actively supports Data Collection Rules (DCRs) that not only supports filtering of data during ingestion time not only for agents but also for other types of ingested data.

The AMA and DCRs helps in sending different types of data to different Log Analytic Workspaces, hence, if their is data that is not useful then it is not required to send it to the workspace associated with Sentinel. XPath queries can be used to filter out the events.

AMA agent can be easily installed via VM extensions, Azure Policy, or the Windows installer. However, the most preferable option is Azure Policy via Defender for Cloud (MDC) as it can work for any server on any cloud or on-prem and if any new servers are added then they will automatically get agent.

Partners can also configure a forwarder for CEF via AMA connector while forwarding syslog data to the Sentinel workspace using AMA. A Content hub solution including an AMA migration tracker workbook is also present. 

If migration is done from the Log Analytics agent to the AMA, then there is a script that can remove the previous agent on all Azure VMs. 

Sample Data

Sample data can be generated with the help of various options acting as customer workspaces during the POC. Some of them are:
  • Microsoft Sentinel Training Lab- This solution is available within the Sentinel's Content hub which goes through all the core features of Sentinel. It also include a little bit of sample data and can be considered if not much is required for POC.

  • Microsoft Sentinel To-Go!- It is a community resource that also includes some sample data.

  • Ingest Sample CEF  Data into Azure Sentinel- Microsoft Community Hub-  Although this one is older, its sample events are still very relevant. It can be used while testing a specific analytic rule in which a required specific data can be fed to trigger that rule. 

  • AttackIQ- It can be used to generate sufficient incidents to simulate a multistage attack, a Fusion incident.

Some of the other simulation options with other Microsoft Security services are:
  • Alert Validation in Microsoft Defender for Cloud
  • Deploy Microsoft Defender for Endpoint on Linux manually (useful if Defender 365 connector is installed)
  • Simulating risk detections in Defender in Azure AD Identity Protection (useful if Defender 365 connector is installed)
  • New ingestion-SampleData-as-a-service solution, for a great Demos and simulation- Microsoft Community Hub (useful for the elsewhere data need to be ingested to other workspaces)








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