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

 





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






Migrations

Currently, MSSPs on POC needs to migrate from the legacy SIEM in use and generally, the main concern is to convert the existing rule into Sentinel KOL. However, the focus should be on data sources because many of the connectors are available as Content hub solutions, which  means that the connector will also have other artifacts like analytic rules, workbooks, playbooks, etc. Over 250 solutions are there in the marketplace and once it is determined which data sources needed to be covered during the POC. After that, the rules will be mapped within the SIEM legacy to the rules provided within the solution. 

Partners may end up with some gaps, but, not all the rules will have to be converted. Some repositories like unified Microsoft Sentinel and Microsoft 365 Defender repository, also have many artifacts available. Some tools also offers free Sigma rule translations, such as SOC Prime's Uncoder I.O. Also, partners going through the POC may sometimes come up with their own solutions that can be published to the marketplace.

Which Connectors?

The types of connectors required to be configured and tested during during a Sentinel POC depends on what compliance regulations or internal security requirements or internal priorities the partners must comply with. 

There are various data ingestion methods for Microsoft Sentinel. Some of the connectors like syslog and CEF can also support a variety of data sources. It is just a matter of time in figuring out the right method of ingesting a data source. There is also a Zero Trust solution in Content hub having some recommended data connectors, and it sorts them from Foundational, to Basic, to Intermediate, to Advanced.

Considerations:

  • Free data- Some data is always free.

  • Microsoft Sentinel benefit for Microsoft 365 E5, A5, F5, and G5 customers- Customers currently paying for those licenses can receive "a data grant of up to 5MB per user/day to ingest Microsoft 365 data." 

  • Ingestion time transformation- Many tables support ingestion time transformation as another way to reduce cost. Partners can use ingestion time transformations to filter out data that is not useful for security analysis. There is also a library of transformations available and these transformations can also be used to mask data.

  • Commitment tiers- Previously known as Capacity Reservations, is another way to reduce costs, as much as 65% compared to pay-as-you-go.






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












































Comments

Popular posts from this blog

Query, Visualize, & Monitor Data in Azure Sentinel

Planning for Implementing SAP Solutions on Azure (Part 2 of 5)

Work with String Data Using KQL Statements