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: defender-xdr/advanced-hunting-defender-use-custom-rules.md
+18-14Lines changed: 18 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,19 +36,20 @@ To use a function from Microsoft Sentinel, go to the **Functions** tab and scrol
36
36
You can also select the vertical ellipses (  ) to the right of the function and select **Insert to query** to insert the function into a query in the query editor.
37
37
38
38
Other options include:
39
-
-**View details** – opens the function side pane containing its details
40
-
-**Load function code** – opens a new tab containing the function code
39
+
-**View details** – Opens the function side pane containing its details.
40
+
-**Load function code** – Opens a new tab containing the function code.
41
41
42
42
For editable functions, more options are available when you select the vertical ellipses:
43
-
-**Edit details** – opens the function side pane to allow you to edit details about the function (except folder names for Sentinel functions)
44
-
-**Delete** – deletes the function
43
+
-**Edit details** – Opens the function side pane to allow you to edit details about the function (except folder names for Sentinel functions).
44
+
-**Delete** – Deletes the function.
45
45
46
46
### Use adx() operator for Azure Data Explorer queries (Preview)
47
47
Use the `adx()` operator to query tables stored in Azure Data Explorer. Read [What is Azure Data Explorer?](/azure/data-explorer/data-explorer-overview) for more details.
48
48
49
49
This feature was previously only available in log analytics in Microsoft Sentinel. Users can now use the operator in advanced hunting in the unified Microsoft Defender portal without needing to manually open a Microsoft Sentinel window.
50
50
51
51
In the query editor, enter the query in the following format:
52
+
52
53
```Kusto
53
54
adx('<Cluster URI>/<Database Name>').<Table Name>
54
55
```
@@ -58,13 +59,13 @@ For example, to get the first 10 rows of data from the `StormEvents` table store
58
59
:::image type="content" source="/defender-xdr/media/adx-sample.png" alt-text="Screenshot of adx operator in advanced hunting." lightbox="/defender-xdr/media/adx-sample.png":::
59
60
60
61
> [!NOTE]
61
-
> The `adx()` operator is not supported for custom detections.
62
+
> The `adx()` operator isn't supported for custom detections.
62
63
63
64
64
65
### Use arg() operator for Azure Resource Graph queries
65
66
The `arg()` operator can be used to query across deployed Azure resources like subscriptions, virtual machines, CPU, storage, and the like.
66
67
67
-
This feature was previously only available in log analytics in Microsoft Sentinel. In the Microsoft Defender portal, the `arg()` operator works over Microsoft Sentinel data (that is, Defender XDR tables are not supported). This allows users to use the operator in advanced hunting without needing to manually open a Microsoft Sentinel window.
68
+
This feature was previously only available in log analytics in Microsoft Sentinel. In the Microsoft Defender portal, the `arg()` operator works over Microsoft Sentinel data (that is, Defender XDR tables aren't supported). This allows users to use the operator in advanced hunting without needing to manually open a Microsoft Sentinel window.
68
69
69
70
Note that queries using the `arg()` operator return the first 1,000 records only. Read [Query data in Azure Resource Graph by using arg()](/azure/azure-monitor/logs/azure-monitor-data-explorer-proxy#query-data-in-azure-resource-graph-by-using-arg-preview) for more details.
70
71
@@ -92,22 +93,22 @@ arg("").Resources
92
93
93
94
To use a saved query from Microsoft Sentinel, go to the **Queries** tab and scroll until you find the query that you want. Double-click the query name to load the query in the query editor. For more options, select the vertical ellipses (  ) to the right of the query. From here, you can perform the following actions:
94
95
95
-
-**Run query** – loads the query in the query editor and runs it automatically
96
-
-**Open in query editor** – loads the query in the query editor
97
-
-**View details** – opens the query details side pane where you can inspect the query, run the query, or open the query in the editor
96
+
-**Run query** – Loads the query in the query editor and runs it automatically.
97
+
-**Open in query editor** – Loads the query in the query editor.
98
+
-**View details** – Opens the query details side pane where you can inspect the query, run the query, or open the query in the editor.
98
99
99
-
:::image type="content" source="/defender/media/advanced-hunting-unified-view-details.png" alt-text="Screenshot of the options available in saved queries in the Microsoft Defender portal" lightbox="/defender/media/advanced-hunting-unified-view-details.png":::
100
+
:::image type="content" source="/defender/media/advanced-hunting-unified-view-details.png" alt-text="Screenshot of the options available in saved queries in the Microsoft Defender portal." lightbox="/defender/media/advanced-hunting-unified-view-details.png":::
100
101
101
102
102
103
For editable queries, more options are available:
103
104
104
-
-**Edit details** – opens the query details side pane with the option to edit the details like description (if applicable) and the query itself; only the folder names (location) of Microsoft Sentinel queries can't be edited
105
-
-**Delete** – deletes the query
106
-
-**Rename** – allows you to modify the query name
105
+
-**Edit details** – Opens the query details side pane with the option to edit the details like description (if applicable) and the query itself; only the folder names (location) of Microsoft Sentinel queries can't be edited.
106
+
-**Delete** – Deletes the query.
107
+
-**Rename** – Allows you to modify the query name.
107
108
108
109
## Create custom analytics and detection rules
109
110
110
-
To help discover threats and anomalous behaviors in your environment, you can create custom detection policies.
111
+
To help discover threats and anomalous behaviors in your environment, you can create customized detection rules.
111
112
112
113
For analytics rules that apply to data ingested through the connected Microsoft Sentinel workspace, select **Manage rules > Create analytics rule**.
113
114
@@ -117,4 +118,7 @@ The **Analytics rule wizard** appears. Fill up the required details as described
117
118
118
119
You can also create custom detection rules that query data from both Microsoft Sentinel and Defender XDR tables. Select **Manage rules > Create custom detection**. Read [Create and manage custom detection rules](custom-detection-rules.md) for more information.
119
120
121
+
In custom detection rule creation, you can only query data ingested as analytics logs (that is, not as basic logs or auxiliary logs, see [log management plans](/azure/sentinel/log-plans#log-management-plans) to check the different tiers) otherwise the rule creation won't proceed.
122
+
120
123
If your Defender XDR data is ingested into Microsoft Sentinel, you have the option to choose between **Create custom detection** and **Create analytics rule**.
0 commit comments