Deployment (Part 1)

By Ashwin Venugopal -

 




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



Azure Resources

Microsoft Sentinel needs following resources to be created:
  1. Subscription (if a dedicated subscription(s) will be used)
  2. Resource group(s)
  3. Log Analytics workspace(s) Automation rules/playbook Alert rules
  4. 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 undocumented changes. 

  • Automation Tools- Microsoft Sentinel resources support several infrastructure-as-code tools, such as Hashicorp Terraform, that can offer consistency to processes. One of the native Microsoft Sentinel features, allows the use of a GitHub or Azure DevOps repository to automate the deployment of detection rules, Microsoft Sentinel functions and workbooks. The repositories can be used to deploy content across multiple Microsoft Sentinel instances. 

  • Custom Scripts/Programs- Microsoft provides a PowerShell automation library called Az.SecurityInsights that can be used to script a wide range of Microsoft Sentinel-related deployment tasks. The Microsoft Sentinel community also offers additional resources like AzSentinel PowerShell library and a wide range of Azure Resource Manager (ARM) templates for various playbooks, alert rules, and workbooks. Optional Azure resources:

    • Service Principal Names (SPNs)- They are typically used in automation of playbooks for authentication while accessing various resources. They should be given minimal permissions required to perform their tasks. 
    • Storage accounts- They can be used for temporary storage of analysis data, long-term log retention, and other tasks that require basic storage outside Log Analytics.
    • Function Apps- They can perform a wide variety of tasks as serverless compute resources. However, only one type of compute platform can be used for one resource group. 
    • Key Vaults- Typically used for secure storage of secrets used by various log collectors. 
    • Event Hubs- They can be used to share analysis data in certain designs requiring integration with legacy SIEMs or third-party analytical platforms. 

However, none of the optional resources are required for the initial Microsoft Sentinel configuration.

Log Source Onboarding

Microsoft Sentinel includes many data connectors for a wide range of log sources. Hence, according to the type of log source, the onboarding process might vary from just a few clicks of the mouse, deployment of AMA, or to more complex configurations involving the deployment of additional log collection resources such as Microsoft Sentinel playbooks based on Azure Logic Apps, Azure Function Apps, and vendor-provided log retrieval tools.

Built-in Data Connectors

Microsoft Sentinel contains many connectors that can be deployed with a few clicks via Microsoft Sentinel portal and the requisite RBAC permissions. New data connectors for other products are added regularly. The built-in data connectors should be considered over the custom ones, wherever feasible, as they are fully supported by Microsoft and the Microsoft Sentinel community. 


Conclusion:

The key considerations for the deployment phase, after the completion of the high-level design, are discussed here. 





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