Migrate ArcSight SOAR automation to Microsoft Sentinel
Microsoft Sentinel provides Security Orchestration, Automation, and Response (SOAR) capabilities with automation rules and playbooks. Automation rules automate incident handling and response, and playbooks run predetermined sequences of actions to response and remediate threats. This article discusses how to identify SOAR use cases, and how to migrate your ArcSight SOAR automation to Microsoft Sentinel.
Automation rules simplify complex workflows for your incident orchestration processes, and allow you to centrally manage your incident handling automation.
With automation rules, you can:
- Perform simple automation tasks without necessarily using playbooks. For example, you can assign, tag incidents, change status, and close incidents.
- Automate responses for multiple analytics rules at once.
- Control the order of actions that are executed.
- Run playbooks for those cases where more complex automation tasks are necessary.
Identify SOAR use cases
Here’s what you need to think about when migrating SOAR use cases from ArcSight.
- Use case quality. Choose good use cases for automation. Use cases should be based on procedures that are clearly defined, with minimal variation, and a low false-positive rate. Automation should work with efficient use cases.
- Manual intervention. Automated response can have wide ranging effects and high impact automations should have human input to confirm high impact actions before they’re taken.
- Binary criteria. To increase response success, decision points within an automated workflow should be as limited as possible, with binary criteria. Binary criteria reduces the need for human intervention, and enhances outcome predictability.
- Accurate alerts or data. Response actions are dependent on the accuracy of signals such as alerts. Alerts and enrichment sources should be reliable. Microsoft Sentinel resources such as watchlists and reliable threat intelligence can enhance reliability.
- Analyst role. While automation where possible is great, reserve more complex tasks for analysts, and provide them with the opportunity for input into workflows that require validation. In short, response automation should augment and extend analyst capabilities.
Migrate SOAR workflow
This section shows how key SOAR concepts in ArcSight translate to Microsoft Sentinel components, and provides general guidelines for how to migrate each step or component in the SOAR workflow.
| Step (in diagram) | ArcSight | Microsoft Sentinel |
|---|---|---|
| 1 | Ingest events into Enterprise Security Manager (ESM) and trigger correlation events. | Ingest events into the Log Analytics workspace. |
| 2 | Automatically filter alerts for case creation. | Use analytics rules to trigger alerts. Enrich alerts using the custom details feature to create dynamic incident names. |
| 3 | Classify cases. | Use automation rules. With automation rules, Microsoft Sentinel treats incidents according to the analytics rule that triggered the incident, and the incident properties that match defined criteria. |
| 4 | Consolidate cases. | You can consolidate several alerts to a single incident according to properties such as matching entities, alert details, or creation timeframe, using the alert grouping feature. |
| 5 | Dispatch cases. | Assign incidents to specific analysts using an integration between Microsoft Teams, Azure Logic Apps, and Microsoft Sentinel automation rules. |
Map SOAR components
Review which Microsoft Sentinel or Azure Logic Apps features map to the main ArcSight SOAR components.
| ArcSight | Microsoft Sentinel/Azure Logic Apps |
|---|---|
| Trigger | Trigger |
| Automation bit | Azure Function connector |
| Action | Action |
| Scheduled playbooks | Playbooks initiated by the recurrence trigger |
| Workflow playbooks | Playbooks automatically initiated by Microsoft Sentinel alert or incident triggers |
| Marketplace | • Automation > Templates tab • Content hub catalog • GitHub |
Operationalize playbooks and automation rules in Microsoft Sentinel
Most of the playbooks that you use with Microsoft Sentinel are available in either the Automation > Templates tab, the Content hub catalog, or GitHub. In some cases, however, you might need to create playbooks from scratch or from existing templates.
You typically build your custom logic app using the Azure Logic App Designer feature. The logic apps code is based on Azure Resource Manager (ARM) templates, which facilitate development, deployment and portability of Azure Logic Apps across multiple environments. To convert your custom playbook into a portable ARM template, you can use the ARM template generator.
Use these resources for cases where you need to build your own playbooks either from scratch or from existing templates.
- Automate incident handling in Microsoft Sentinel
- Automate threat response with playbooks in Microsoft Sentinel
- Tutorial: Use playbooks with automation rules in Microsoft Sentinel
- How to use Microsoft Sentinel for Incident Response, Orchestration and Automation
- Adaptive Cards to enhance incident response in Microsoft Sentinel
SOAR post migration best practices
Here are best practices you should take into account after your SOAR migration:
- After you migrate your playbooks, test the playbooks extensively to ensure that the migrated actions work as expected.
- Periodically review your automations to explore ways to further simplify or enhance your SOAR. Microsoft Sentinel constantly adds new connectors and actions that can help you to further simplify or increase the effectiveness of your current response implementations.
- Monitor the performance of your playbooks using the Playbooks health monitoring workbook.
- Use managed identities and service principals: Authenticate against various Azure services within your Logic Apps, store the secrets in Azure Key Vault, and obscure the output of the flow execution. We also recommend that you monitor the activities of these service principals.
Next steps
In this article, you learned how to map your SOAR automation from ArcSight to Microsoft Sentinel.