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-qradar-detection-rules.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ This article describes how to identify, compare, and migrate your QRadar detecti
20
20
Microsoft Sentinel uses machine learning analytics to create high-fidelity and actionable incidents, and some of your existing detections may be redundant in Microsoft Sentinel. Therefore, don't migrate all of your detection and analytics rules blindly. Review these considerations as you identify your existing detection rules.
21
21
22
22
- Make sure to select use cases that justify rule migration, considering business priority and efficiency.
23
-
- Check that you [understand Microsoft Sentinel rule types](detect-threats-built-in.md).
23
+
- Check that you [understand Microsoft Sentinel rule types](threat-detection.md).
24
24
- Check that you understand the [rule terminology](#compare-rule-terminology).
25
25
- Review any rules that haven't triggered any alerts in the past 6-12 months, and determine whether they're still relevant.
26
26
- Eliminate low-level threats or alerts that you routinely ignore.
@@ -48,7 +48,7 @@ Learn more about [best practices for migrating detection rules](https://techcomm
48
48
49
49
In Microsoft Sentinel, go to the **Configuration > Analytics > Rule templates** tab, and create and update each relevant analytics rule.
50
50
51
-
For more information, see [Detect threats out-of-the-box](detect-threats-built-in.md).
51
+
For more information, see [Create scheduled analytics rules from templates](create-analytics-rule-from-template.md).
52
52
53
53
-**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.
54
54
@@ -72,10 +72,10 @@ Learn more about [best practices for migrating detection rules](https://techcomm
72
72
73
73
Learn more about analytics rules:
74
74
75
-
-[**Create custom analytics rules to detect threats**](detect-threats-custom.md). Use [alert grouping](detect-threats-custom.md#alert-grouping) to reduce alert fatigue by grouping alerts that occur within a given timeframe.
75
+
-[**Scheduled analytics rules in Microsoft Sentinel**](scheduled-rules-overview.md). Use [alert grouping](scheduled-rules-overview.md#alert-grouping) to reduce alert fatigue by grouping alerts that occur within a given timeframe.
76
76
-[**Map data fields to entities in Microsoft Sentinel**](map-data-fields-to-entities.md) to enable SOC engineers to define entities as part of the evidence to track during an investigation. Entity mapping also makes it possible for SOC analysts to take advantage of an intuitive [investigation graph (investigate-cases.md#use-the-investigation-graph-to-deep-dive) that can help reduce time and effort.
77
77
-[**Investigate incidents with UEBA data**](investigate-with-ueba.md), as an example of how to use evidence to surface events, alerts, and any bookmarks associated with a particular incident in the incident preview pane.
78
-
-[**Kusto Query Language (KQL)**](/azure/data-explorer/kusto/query/), which you can use to send read-only requests to your [Log Analytics](/azure/azure-monitor/logs/log-analytics-tutorial) database to process data and return results. KQL is also used across other Microsoft services, such as [Microsoft Defender for Endpoint](https://www.microsoft.com/microsoft-365/security/endpoint-defender) and [Application Insights](/azure/azure-monitor/app/app-insights-overview).
78
+
-[**Kusto Query Language (KQL)**](/kusto/query/?view=microsoft-sentinel&preserve-view=true), which you can use to send read-only requests to your [Log Analytics](/azure/azure-monitor/logs/log-analytics-tutorial) database to process data and return results. KQL is also used across other Microsoft services, such as [Microsoft Defender for Endpoint](https://www.microsoft.com/microsoft-365/security/endpoint-defender) and [Application Insights](/azure/azure-monitor/app/app-insights-overview).
79
79
80
80
## Compare rule terminology
81
81
@@ -94,12 +94,12 @@ Use these samples to compare and map rules from QRadar to Microsoft Sentinel in
|Date/time tests |[QRadar syntax](#datetime-tests-syntax) |• [Selected day of the month example](#datetime-tests-selected-day-of-the-month-example-qradar)<br>• [Selected day of the week example](#datetime-tests-selected-day-of-the-week-example-qradar)<br>• [after/before/at example](#datetime-tests-afterbeforeat-example-qradar) |• [Selected day of the month example](#datetime-tests-selected-day-of-the-month-example-kql)<br>• [Selected day of the week example](#datetime-tests-selected-day-of-the-week-example-kql)<br>• [after/before/at example](#datetime-tests-afterbeforeat-example-kql) |• [Date and time operators](/azure/data-explorer/kusto/query/samples?pivots=azuremonitor#date-and-time-operations)<br>• Selected day of the month: [dayofmonth()](/azure/data-explorer/kusto/query/dayofmonthfunction)<br>• Selected day of the week: [dayofweek()](/azure/data-explorer/kusto/query/dayofweekfunction)<br>• after/before/at: [format_datetime()](/azure/data-explorer/kusto/query/format-datetimefunction) |
|Functions: counters |[QRadar syntax](#functions-counters-syntax)|[Event property and time example](#counters-event-property-and-time-example-qradar)|[Event property and time example](#counters-event-property-and-time-example-kql)|[summarize](/azure/data-explorer/kusto/query/summarizeoperator)|
|Date/time tests |[QRadar syntax](#datetime-tests-syntax) |• [Selected day of the month example](#datetime-tests-selected-day-of-the-month-example-qradar)<br>• [Selected day of the week example](#datetime-tests-selected-day-of-the-week-example-qradar)<br>• [after/before/at example](#datetime-tests-afterbeforeat-example-qradar) |• [Selected day of the month example](#datetime-tests-selected-day-of-the-month-example-kql)<br>• [Selected day of the week example](#datetime-tests-selected-day-of-the-week-example-kql)<br>• [after/before/at example](#datetime-tests-afterbeforeat-example-kql) |• [Date and time operators](/kusto/query/datetime-timespan-arithmetic?view=microsoft-sentinel&preserve-view=true)<br>• Selected day of the month: [dayofmonth()](/kusto/query/day-of-month-function?view=microsoft-sentinel&preserve-view=true)<br>• Selected day of the week: [dayofweek()](/kusto/query/day-of-week-function?view=microsoft-sentinel&preserve-view=true)<br>• after/before/at: [format_datetime()](/kusto/query/format-datetime-function?view=microsoft-sentinel&preserve-view=true) |
|Functions: counters |[QRadar syntax](#functions-counters-syntax)|[Event property and time example](#counters-event-property-and-time-example-qradar)|[Event property and time example](#counters-event-property-and-time-example-kql)|[summarize](/kusto/query/summarize-operator?view=microsoft-sentinel&preserve-view=true)|
|IP/port tests |[QRadar syntax](#ipport-tests-syntax)|• [Source port example](#ipport-tests-source-port-example-qradar)<br>• [Source IP example](#ipport-tests-source-ip-example-qradar)|• [Source port example](#ipport-tests-source-port-example-kql)<br>• [Source IP example](#ipport-tests-source-ip-example-kql)||
0 commit comments