Skip to content

Commit 157bbe3

Browse files
add integrating sections to migrate docs
1 parent a1d947c commit 157bbe3

File tree

4 files changed

+22
-15
lines changed

4 files changed

+22
-15
lines changed

articles/sentinel/migration-splunk-detection-rules.md

Lines changed: 12 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,12 @@
11
---
2-
title: Migrate Splunk detection rules to Microsoft Sentinel | Microsoft Docs
2+
title: Migrate Splunk detection rules to Microsoft Sentinel
3+
titleSuffix: Microsoft Sentinel
34
description: Learn how to identify, compare, and migrate your Splunk detection rules to Microsoft Sentinel built-in rules.
45
author: limwainstein
56
ms.author: lwainstein
67
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.
810
---
911

1012
# Migrate Splunk detection rules to Microsoft Sentinel
@@ -22,11 +24,12 @@ Microsoft Sentinel uses machine learning analytics to create high-fidelity and a
2224
- Check that you understand the [rule terminology](#compare-rule-terminology).
2325
- Review any rules that haven't triggered any alerts in the past 6-12 months, and determine whether they're still relevant.
2426
- Eliminate low-level threats or alerts that you routinely ignore.
25-
- Use existing functionality, and check whether Microsoft Sentinels [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, its likely that some of your existing detections wont 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.
2628
- 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.
2730
- Explore community resources such as the [SOC Prime Threat Detection Marketplace](https://my.socprime.com/platform-overview/) to check whether your rules are available.
2831
- Consider whether an online query converter such as Uncoder.io might work for your rules.
29-
- If rules arent available or cant 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.
3033

3134
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).
3235

@@ -41,14 +44,18 @@ Learn more about [best practices for migrating detection rules](https://techcomm
4144
1. **Confirm that you have any required data sources connected,** and review your data connection methods.
4245

4346
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).
4451

4552
- **If the built-in rules are sufficient**, use built-in rule templates to create rules for your own workspace.
4653

4754
In Microsoft Sentinel, go to the **Configuration > Analytics > Rule templates** tab, and create and update each relevant analytics rule.
4855

4956
For more information, see [Detect threats out-of-the-box](detect-threats-built-in.md).
5057

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.
5259

5360
Identify the trigger condition and rule action, and then construct and review your KQL query.
5461

articles/sentinel/migration-splunk-historical-data.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,12 @@
11
---
2-
title: "Microsoft Sentinel migration: Export Splunk data to target platform | Microsoft Docs"
3-
description: Learn how to export your historical data from Splunk.
2+
title: Export Splunk data to target platform
3+
titlesuffix: Microsoft Sentinel
4+
description: Learn how to export your historical data from Splunk for a Microsoft Sentinel migration of security monitoring use cases
45
author: limwainstein
56
ms.author: lwainstein
67
ms.topic: how-to
7-
ms.date: 05/03/2022
8+
ms.date: 03/11/2024
9+
#customer intent: As a SOC administrator, I want to migrate historical data from Splunk so I have continuity when I migrate to Microsoft Sentinel.
810
---
911

1012
# Export historical data from Splunk

articles/sentinel/siem-migration.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -31,12 +31,10 @@ You need the following from the source SIEM:
3131

3232
You need the following on the target, Microsoft Sentinel:
3333

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).
3535
- Ingest security data previously used in your source SIEM into Microsoft Sentinel by enabling an out-of-the-box (OOTB) data connector.
3636
- 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).
4038

4139
## Translate Splunk detection rules
4240

articles/sentinel/whats-new.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
title: What's new in Microsoft Sentinel
3-
description: This article describes new features in Microsoft Sentinel from the past few months.
3+
description: Learn about the latest new features and announcement in Microsoft Sentinel from the past few months.
44
author: yelevin
55
ms.author: yelevin
6-
ms.topic: conceptual
7-
ms.date: 02/28/2024
6+
ms.topic: concept
7+
ms.date: 03/11/2024
88
---
99

1010
# What's new in Microsoft Sentinel

0 commit comments

Comments
 (0)