Implementing A New Microsoft Sentinel Solution (part 1)

By Ashwin Venugopal -

 







To read part 2, please click here
To read part 3, please click here
To read part 4, please click here











Here is an overview of the approaches that can be used in a new Microsoft Sentinel environment.

Project Resourcing

Project Planning

some of the key factors that should be considered during a project planning stage are:
  • Access to log sources and users.
  • Types of log sources (standard data connectors vs required development).
  • Complexity of Azure architecture.
  • Requirement for custom SOAR automation playbooks.
  • Azure cost assessment and optimization.
The following roles are needed for a successful Microsoft sentinel deployment:
  • Project Manager- It is recommended to have an experienced Project Management staff having Project Management Professional (PMP) and Information Technology Infrastructure Library (ITIL) backgrounds, as the stakeholder management requirements are quite broad. 

  • Security Architect- As Microsoft Sentinel environment always contain highly sensitive data, the security architect will take care of the overall security design of the Microsoft Sentinel solution.

  • Cloud Engineer- An organization's Azure Cloud engineer/administrator will look after the resiliency requirements, Azure regions, data residency, tagging or templates needed, etc. 

  • Engineering - System's Owner- In order to obtain smooth data transfer to Microsoft Sentinel, Subject Matter Experts (SMEs) as well as asset owners having administrative ability to provide the samples of logs and configure log-forwarding parameters on each asset, will be required to work with the project team.

  • Engineering - SIEM- They are generally responsible for configuring Microsoft Sentinel along with the Log Analytics, Logic Apps, workbooks, and playbooks and also some of the other high-level tasks.

  • Network Engineer- These resources are used on demand in order to make changes in the firewalls or network infrastructures, so that, the log forwarding from data sources to Azure can be facilitated.

  • Business Analyst- This one provides an Azure cost analysis for each technical requirement and can remodel it further (with the help of SIEM engineer) according to the changes made in the IT environment.  

  • Security Operations- These are required to document the detection, alerting, and threat hunting requirements of the solution, because it is their job as the end consumer of the service to articulate the build requirements. 

  • Developers- They are generally used whenever it is required to obtain data from log sources like SaaS applications and can easily leveraged to great effect by Azure functions. 

  • Compliance Manager- In order to fulfill your company's legal, regulatory, or industry-specific compliance requirements via Microsoft Sentinel, it is mandatory to have an interaction between the core Microsoft Sentinel team and the compliance manager; so that the decisions on the log retention period, custom workbooks, etc. can be made easily.
















To read part 2, please click here
To read part 3, please click here
To read part 4, 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...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
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...
Read more