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

By Ashwin Venugopal -

 





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

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different groups of computers, re
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning of alert rule parameter
Read more

Design Planning (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Complex Organizational Structures SIEM can be an expensive security control, hence, it is common multiple businesses to contribute to the overall expense. Various organizational units may require a level of access to specific dashboards or sets of data. Microsoft Sentinel offers the ability to assign table-level permissions and limit the level of access to the minimum required to perform requisite job functions.  Role-based Access Control (RBAC) Requirements Microsoft Sentinel offers an extensive list of Azure built-in roles that can be used to provide granular access according to the job requirements and permitted level of access. Some of them are various Microsoft Sentinel dedicated roles: Microsoft Sentinel Contributor- Can perform all engineering-related configuration, such as creating alert rules, configuring data connectors, and additional similar tasks.  Microsoft Sentinel Reader- Can query the log data stor
Read more