You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/sentinel/migration-splunk-detection-rules.md
+12-5Lines changed: 12 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,12 @@
1
1
---
2
-
title: Migrate Splunk detection rules to Microsoft Sentinel | Microsoft Docs
2
+
title: Migrate Splunk detection rules to Microsoft Sentinel
3
+
titleSuffix: Microsoft Sentinel
3
4
description: Learn how to identify, compare, and migrate your Splunk detection rules to Microsoft Sentinel built-in rules.
4
5
author: limwainstein
5
6
ms.author: lwainstein
6
7
ms.topic: how-to
7
-
ms.date: 03/08/2024
8
+
ms.date: 03/11/2024
9
+
#customer intent: As a SOC administrator, I want to migrate Splunk detection rules to KQL so I can migrate to Microsoft Sentinel.
8
10
---
9
11
10
12
# Migrate Splunk detection rules to Microsoft Sentinel
@@ -22,11 +24,12 @@ Microsoft Sentinel uses machine learning analytics to create high-fidelity and a
22
24
- Check that you understand the [rule terminology](#compare-rule-terminology).
23
25
- Review any rules that haven't triggered any alerts in the past 6-12 months, and determine whether they're still relevant.
24
26
- Eliminate low-level threats or alerts that you routinely ignore.
25
-
- Use existing functionality, and check whether Microsoft Sentinel’s [built-in analytics rules](https://github.com/Azure/Azure-Sentinel/tree/master/Detections) might address your current use cases. Because Microsoft Sentinel uses machine learning analytics to produce high-fidelity and actionable incidents, it’s likely that some of your existing detections won’t be required anymore.
27
+
- Use existing functionality, and check whether Microsoft Sentinel's [built-in analytics rules](https://github.com/Azure/Azure-Sentinel/tree/master/Detections) might address your current use cases. Because Microsoft Sentinel uses machine learning analytics to produce high-fidelity and actionable incidents, it's likely that some of your existing detections won't be required anymore.
26
28
- Confirm connected data sources and review your data connection methods. Revisit data collection conversations to ensure data depth and breadth across the use cases you plan to detect.
29
+
- Test the capabilities of the [SIEM migration experience](siem-migration.md) to determine if the automated translation is suitable.
27
30
- Explore community resources such as the [SOC Prime Threat Detection Marketplace](https://my.socprime.com/platform-overview/) to check whether your rules are available.
28
31
- Consider whether an online query converter such as Uncoder.io might work for your rules.
29
-
- If rules aren’t available or can’t be converted, they need to be created manually, using a KQL query. Review the [rules mapping](#map-and-compare-rule-samples) to create new queries.
32
+
- If rules aren't available or can't be converted, they need to be created manually, using a KQL query. Review the [rules mapping](#map-and-compare-rule-samples) to create new queries.
30
33
31
34
Learn more about [best practices for migrating detection rules](https://techcommunity.microsoft.com/t5/microsoft-sentinel-blog/best-practices-for-migrating-detection-rules-from-arcsight/ba-p/2216417).
32
35
@@ -41,14 +44,18 @@ Learn more about [best practices for migrating detection rules](https://techcomm
41
44
1.**Confirm that you have any required data sources connected,** and review your data connection methods.
42
45
43
46
1. Verify whether your detections are available as built-in templates in Microsoft Sentinel:
47
+
48
+
-**Use the SIEM migration experience** to automate translation and migration.
49
+
50
+
For more information, see [Use the SIEM migration experience](siem-migration.md).
44
51
45
52
-**If the built-in rules are sufficient**, use built-in rule templates to create rules for your own workspace.
46
53
47
54
In Microsoft Sentinel, go to the **Configuration > Analytics > Rule templates** tab, and create and update each relevant analytics rule.
48
55
49
56
For more information, see [Detect threats out-of-the-box](detect-threats-built-in.md).
50
57
51
-
-**If you have detections that aren't covered by Microsoft Sentinel's built-in rules**, try an online query converter, such as [Uncoder.io](https://uncoder.io/) to convert your queries to KQL.
58
+
-**If you have detections that aren't covered by Microsoft Sentinel's built-in rules**, try an online query converter, such as [Uncoder.io](https://uncoder.io/)or [SPL2KQL](https://azure.github.io/spl2kql)to convert your queries to KQL.
52
59
53
60
Identify the trigger condition and rule action, and then construct and review your KQL query.
Copy file name to clipboardExpand all lines: articles/sentinel/siem-migration.md
+2-4Lines changed: 2 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,12 +31,10 @@ You need the following from the source SIEM:
31
31
32
32
You need the following on the target, Microsoft Sentinel:
33
33
34
-
- The SIEM migration experience deploys analytics rules which requires the **Microsoft Sentinel Contributor** role.For more information about other roles and permissions supported for Microsoft Sentinel, see [Permissions in Microsoft Sentinel](roles.md).
34
+
- The SIEM migration experience deploys analytics rules. This capability requires the **Microsoft Sentinel Contributor** role.<br><br>For more information, see [Permissions in Microsoft Sentinel](roles.md).
35
35
- Ingest security data previously used in your source SIEM into Microsoft Sentinel by enabling an out-of-the-box (OOTB) data connector.
36
36
- If the data connector isn't installed yet, find the relevant solution in **Content hub**.
37
-
- If no data connector exists, create a custom ingestion pipeline.
38
-
39
-
For more information, see [Discover and manage Microsoft Sentinel out-of-the-box content](sentinel-solutions-deploy.md) or [Custom data ingestion and transformation](data-transformation.md).
37
+
- If no data connector exists, create a custom ingestion pipeline.<br><br>For more information, see [Discover and manage Microsoft Sentinel out-of-the-box content](sentinel-solutions-deploy.md) or [Custom data ingestion and transformation](data-transformation.md).
0 commit comments