Microsoft Sentinel Deployment Best Practices

By Ashwin Venugopal -

 





Microsoft Sentinel Cloud-Native SIEM Architecture

The first cloud-native security information and management system (SIEM) from a major public cloud provider is Microsoft Sentinel. It can be deployed in enterprise's Azure tenant and can be accessed through Microsoft Azure gateway. It guarantees compatibility with previous policies for organizational access control. 

Making use of integrations with Microsoft Defender tools and Azure services, like Log Analysis and Logic Apps for analysis and automation capabilities, Microsoft Sentinel enables organizations to obtain  security signals and analyze them completely.

Harnessing the power of flexible computing and capability of storage, built into Azure for the use of heavy data programs like SIEM, is a significant benefit as compared to on-site solutions for analyzing logs. 

Moreover, Microsoft Sentinel has the capability to utilize Infrastructure-as-a-Service (IaaS) and Platform-as-a-Service (PaaS) features offered in Azure to provide workflow automation and analysis services as well as the extension in storage of log data, which is only available as additional services by other SIEM providers.

Microsoft Sentinel for Security Operations

Benefits offered to Security Operations and Content Engineering teams may become even more impactful. The new threat detection content developed in KQL can be easily deployed via various methods, including tools like Azure DevOps for internal content teams, or by leveraging Azure Lighthouse to enhance and extend content development through a partner or MSSP. 

Many times, the security teams does both concurrently, developing internal SecOps capabilities while partnering with an external organization that can offer fast and threat-centric detection content. 

Conclusion

This is a small introduction to the deployment best practices and what could be expected from it. 












































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