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

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