Skip to content

Commit 5fe67d6

Browse files
committed
Clean up hunting, livestream articles
1 parent c7a2ef7 commit 5fe67d6

File tree

7 files changed

+55
-78
lines changed

7 files changed

+55
-78
lines changed

articles/sentinel/bookmarks.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ appliesto:
1313

1414
# Keep track of data during hunting with Microsoft Sentinel
1515

16-
Hunting bookmarks in Microsoft Sentinel helps you preserve the queries and query results that you deem relevant. You can also record your contextual observations and reference your findings by adding notes and tags. Bookmarked data is visible to you and your teammates for easy collaboration. For more information, see [Bookmarks](hunting.md#bookmarks).
16+
Hunting bookmarks in Microsoft Sentinel helps you preserve the queries and query results that you deem relevant. You can also record your contextual observations and reference your findings by adding notes and tags. Bookmarked data is visible to you and your teammates for easy collaboration. For more information, see [Bookmarks](hunting.md#bookmarks-to-keep-track-of-data).
1717

1818
[!INCLUDE [unified-soc-preview](includes/unified-soc-preview.md)]
1919

articles/sentinel/hunting.md

Lines changed: 41 additions & 62 deletions
Original file line numberDiff line numberDiff line change
@@ -20,9 +20,11 @@ For example, one built-in query provides data about the most uncommon processes
2020
[!INCLUDE [reference-to-feature-availability](includes/reference-to-feature-availability.md)]
2121
[!INCLUDE [unified-soc-preview](includes/unified-soc-preview.md)]
2222

23+
<a name="use-built-in-queries"></a>
24+
2325
## Built-in hunting queries
2426

25-
The [hunting dashboard](#use-the-hunting-dashboard) provides ready-made query examples designed to get you started and get you familiar with the tables and the query language. Queries run on data stored in log tables, such as for process creation, DNS events, or other event types.
27+
The hunting dashboard provides ready-made query examples designed to get you started and get you familiar with the tables and the query language. Queries run on data stored in log tables, such as for process creation, DNS events, or other event types.
2628

2729
Built-in hunting queries are developed by Microsoft security researchers on a continuous basis, both adding new queries and fine-tuning existing queries to provide you with an entry point to look for new detections and figure out where to start hunting for the beginnings of new attacks.
2830

@@ -46,11 +48,13 @@ You can also create hunting and livestream queries over data stored in Azure Dat
4648

4749
Use community resources, such as the [Microsoft Sentinel GitHub repository](https://github.com/Azure/Azure-Sentinel/tree/master/Hunting%20Queries) to find more queries and data sources.
4850

51+
<a name="use-the-hunting-dashboard"></a>
52+
4953
## Hunting dashboard
5054

51-
The hunting dashboard enables you to run all your queries, or a selected subset, in a single selection. In the Microsoft Sentinel portal, select **Hunting**.
55+
The hunting dashboard enables you to run all your queries, or a selected subset, in a single selection. In the Microsoft Sentinel, select **Hunting**.
5256

53-
The table shown lists all the queries written by Microsoft's team of security analysts and any extra query you created or modified. Each query provides a description of what it hunts for, and what kind of data it runs on. These queries are grouped by their MITRE ATT&CK **tactics**. The icons on the right categorize the type of threat, such as initial access, persistence, and exfiltration. MITRE ATT&CK **techniques** are shown in the **Techniques** column and describe the specific behavior identified by the hunting query.
57+
The **Queries** tab lists all the hunting queries installed with security solutions from the **Content hub**, and any extra query you created or modified. Each query provides a description of what it hunts for, and what kind of data it runs on. These queries are grouped by their MITRE ATT&CK **tactics**. The icons on the right categorize the type of threat, such as initial access, persistence, and exfiltration. MITRE ATT&CK **techniques** are shown in the **Techniques** column and describe the specific behavior identified by the hunting query.
5458

5559
:::image type="content" source="media/hunting/hunting-start.png" alt-text="Microsoft Sentinel starts hunting" lightbox="media/hunting/hunting-start.png":::
5660

@@ -72,59 +76,18 @@ The following table describes detailed actions available from the hunting dashbo
7276

7377
## Custom hunting queries
7478

75-
Create or modify a query and save it as your own query or share it with users who are in the same tenant.
79+
Create or edit a query and save it as your own query or share it with users who are in the same tenant. In Microsoft Sentinel, create a custom hunting query from the **Hunting** > **Queries** tab.
7680

81+
# [Azure portal](#tab/azure-portal)
7782
:::image type="content" source="./media/hunting/save-query.png" alt-text="Save query" lightbox="./media/hunting/save-query.png":::
83+
# [Defender portal](#tab/defender-portal)
84+
:::image type="content" source="./media/hunting/save-query-defender.png" alt-text="Save query" lightbox="./media/hunting/save-query-defender.png":::
7885

79-
**To create a new query**:
80-
81-
1. Select **New query**.
82-
83-
1. Fill in all the blank fields and select **Create**.
84-
85-
1. Create entity mappings by selecting entity types, identifiers, and columns.
86-
87-
:::image type="content" source="media/hunting/map-entity-types-hunting.png" alt-text="Screenshot for mapping entity types in hunting queries.":::
88-
89-
1. Map MITRE ATT&CK techniques to your hunting queries by selecting the tactic, technique, and sub-technique (if applicable).
90-
91-
:::image type="content" source="./media/hunting/mitre-attack-mapping-hunting.png" alt-text="New query" lightbox="./media/hunting/new-query.png":::
92-
93-
**To clone and modify an existing query**:
94-
95-
1. From the table, select the hunting query you want to modify.
96-
1. Select the ellipsis (...) in the line of the query you want to modify, and select **Clone query**.
97-
98-
:::image type="content" source="./media/hunting/clone-query.png" alt-text="Clone query" lightbox="./media/hunting/clone-query.png":::
99-
100-
1. Modify the query and select **Create**.
101-
102-
**To modify an existing custom query**:
103-
104-
1. From the table, select the hunting query that you wish to modify. Only queries that from a custom content source can be edited. Other content sources have to be edited at that source.
105-
106-
1. Select the ellipsis (...) in the line of the query you want to modify, and select **Edit query**.
107-
108-
1. Modify the **Custom query** field with the updated query. You can also modify the entity mapping and techniques as explained in the "**To create a new query**" section of this documentation.
109-
110-
## Sample query
111-
112-
A typical query starts with a table or parser name followed by a series of operators separated by a pipe character ("\|").
113-
114-
In the example above, start with the table name SecurityEvent and add piped elements as needed.
115-
116-
1. Define a time filter to review only records from the previous seven days.
117-
118-
1. Add a filter in the query to only show event ID 4688.
119-
120-
1. Add a filter in the query on the command line to contain only instances of cscript.exe.
121-
122-
1. Project only the columns you're interested in exploring and limit the results to 1000 and select **Run query**.
123-
124-
1. Select the green triangle and run the query. You can test the query and run it to look for anomalous behavior.
86+
---
12587

126-
We recommend that your query uses an [Advanced Security Information Model (ASIM) parser](normalization-about-parsers.md) and not a built-in table. This ensures that the query will support any current or future relevant data source rather than a single data source.
88+
For more information, see [Create custom hunting queries in Microsoft Sentinel](hunts-custom-queries.md).
12789

90+
<a name="use-the-hunting-dashboard"></a>
12891

12992
## Bookmarks to keep track of data
13093

@@ -144,12 +107,32 @@ During the hunting and investigation process, you might come across query result
144107
You can also create an incident from one or more bookmarks, or add one or more bookmarks to an existing incident. Select a checkbox to the left of any bookmarks you want to use, and then select **Incident actions** > **Create new incident** or **Add to existing incident**. Triage and investigate the incident like any other.
145108
- View your bookmarked data directly in the **HuntingBookmark** table in your Log Analytics workspace. For example:
146109

147-
:::image type="content" source="media/hunting/bookmark-table.png" alt-text="Screenshot of the hunting bookmarks table in the Log Analytics workspace." lightbox="media/bookmarks/bookmark-table.png":::
110+
:::image type="content" source="media/hunting/bookmark-table.png" alt-text="Screenshot of the hunting bookmarks table in the Log Analytics workspace." lightbox="media/hunting/bookmark-table.png":::
148111

149112
Viewing bookmarks from the table enables you to filter, summarize, and join bookmarked data with other data sources, making it easy to look for corroborating evidence.
150113

151114
To start using bookmarks, see [Keep track of data during hunting with Microsoft Sentinel](bookmarks.md).
152115

116+
<a name="use-notebooks-to-power-investigations"></a>
117+
118+
## Livestream sessions
119+
120+
Create interactive sessions that let you test newly created queries as events occur, get notifications from the sessions when a match is found, and launch investigations if necessary. You can quickly create a livestream session using any Log Analytics query.
121+
122+
- **Test newly created queries as events occur**
123+
124+
You can test and adjust queries without any conflicts to current rules that are being actively applied to events. After you confirm these new queries work as expected, it's easy to promote them to custom alert rules by selecting an option that elevates the session to an alert.
125+
126+
- **Get notified when threats occur**
127+
128+
You can compare threat data feeds to aggregated log data and be notified when a match occurs. Threat data feeds are ongoing streams of data that are related to potential or current threats, so the notification might indicate a potential threat to your organization. Create a livestream session instead of a custom alert rule to be notified of a potential issue without the overheads of maintaining a custom alert rule.
129+
130+
- **Launch investigations**
131+
132+
If there's an active investigation that involves an asset such as a host or user, view specific (or any) activity in the log data as it occurs on that asset. Be notified when that activity occurs.
133+
134+
For more information, see [Detect threats by using hunting livestream in Microsoft Sentinel](livestream.md).
135+
153136
## Notebooks to power investigations
154137

155138
When your hunting and investigations become more complex, use Microsoft Sentinel notebooks to enhance your activity with machine learning, visualizations, and data analysis.
@@ -195,7 +178,7 @@ MSTICPy also includes some time-saving notebook tools, such as widgets that set
195178
For more information, see:
196179

197180
- [MSTICPy documentation](https://msticpy.readthedocs.io/en/latest/)
198-
- [Tutorial: Get started with Jupyter notebooks and MSTICPy in Microsoft Sentinel](notebook-get-started.md)
181+
- [Jupyter notebooks with Microsoft Sentinel hunting capabilities](notebooks.md)
199182
- [Advanced configurations for Jupyter notebooks and MSTICPy in Microsoft Sentinel](notebooks-msticpy-advanced.md)
200183

201184
## Useful operators and functions
@@ -228,13 +211,9 @@ The following operators are especially helpful in Microsoft Sentinel hunting que
228211

229212
- **adx()** - This function performs cross-resource queries of Azure Data Explorer data sources from the Microsoft Sentinel hunting experience and Log Analytics. For more information, see [Cross-resource query Azure Data Explorer by using Azure Monitor](../azure-monitor/logs/azure-monitor-data-explorer-proxy.md).
230213

231-
## Next steps
232-
233-
In this article, you learned how to run a hunting investigation with Microsoft Sentinel.
234-
235-
For more information, see:
236-
237-
- [Use notebooks to run automated hunting campaigns](notebooks.md)
238-
- [Use bookmarks to save interesting information while hunting](bookmarks.md)
214+
## Related articles
239215

240-
Learn from an example of using custom analytics rules when [monitoring Zoom](https://techcommunity.microsoft.com/t5/azure-sentinel/monitoring-zoom-with-azure-sentinel/ba-p/1341516) with a [custom connector](create-custom-connector.md).
216+
- [Jupyter notebooks with Microsoft Sentinel hunting capabilities](notebooks.md)
217+
- [Keep track of data during hunting with Microsoft Sentinel](bookmarks.md)
218+
- [Detect threats by using hunting livestream in Microsoft Sentinel](livestream.md)
219+
- Learn from an example of using custom analytics rules when [monitoring Zoom](https://techcommunity.microsoft.com/t5/azure-sentinel/monitoring-zoom-with-azure-sentinel/ba-p/1341516) with a [custom connector](create-custom-connector.md).

articles/sentinel/hunts-custom-queries.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,13 @@ In Microsoft Sentinel, create a custom hunting query from the **Hunting** > **Qu
2424
1. Select the **Queries** tab.
2525
1. From the command bar, select **New query**.
2626

27+
# [Azure portal](#tab/azure-portal)
28+
:::image type="content" source="./media/hunts-custom-queries/save-query.png" alt-text="Save query" lightbox="./media/hunts-custom-queries/save-query.png":::
29+
30+
# [Defender portal](#tab/defender-portal)
31+
:::image type="content" source="./media/hunts-custom-queries/save-query-defender.png" alt-text="Save query" lightbox="./media/hunts-custom-queries/save-query-defender.png":::
32+
---
33+
2734
1. Fill in all the blank fields.
2835

2936
1. Create entity mappings by selecting entity types, identifiers, and columns.

articles/sentinel/livestream.md

Lines changed: 6 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Detect threats by using hunting livestream in Microsoft Sentinel
33
description: Learn how to use hunting livestream in Microsoft Sentinel to actively monitor a compromise event.
44
ms.topic: how-to
5-
ms.date: 03/12/2024
5+
ms.date: 04/24/2024
66
ms.author: austinmc
77
author: austinmccollum
88
ms.collection: usx-security
@@ -15,18 +15,6 @@ appliesto:
1515

1616
Use hunting livestream to create interactive sessions that let you test newly created queries as events occur, get notifications from the sessions when a match is found, and launch investigations if necessary. You can quickly create a livestream session using any Log Analytics query.
1717

18-
- **Test newly created queries as events occur**
19-
20-
You can test and adjust queries without any conflicts to current rules that are being actively applied to events. After you confirm these new queries work as expected, it's easy to promote them to custom alert rules by selecting an option that elevates the session to an alert.
21-
22-
- **Get notified when threats occur**
23-
24-
You can compare threat data feeds to aggregated log data and be notified when a match occurs. Threat data feeds are ongoing streams of data that are related to potential or current threats, so the notification might indicate a potential threat to your organization. Create a livestream session instead of a custom alert rule to be notified of a potential issue without the overheads of maintaining a custom alert rule.
25-
26-
- **Launch investigations**
27-
28-
If there's an active investigation that involves an asset such as a host or user, view specific (or any) activity in the log data as it occurs on that asset. Be notified when that activity occurs.
29-
3018
[!INCLUDE [unified-soc-preview](includes/unified-soc-preview.md)]
3119

3220
## Create a livestream session
@@ -68,6 +56,8 @@ You can create a livestream session from an existing hunting query, or create yo
6856

6957
## View your livestream sessions
7058

59+
Find your livestream sessions on the **Hunting** > **Livestream** tab.
60+
7161
1. For Microsoft Sentinel in the [Azure portal](https://portal.azure.com), under **Threat management**, select **Hunting**.<br> For Microsoft Sentinel in the [Defender portal](https://security.microsoft.com/), select **Microsoft Sentinel** > **Threat management** > **Hunting**.
7262

7363
1. Select the **Livestream** tab.
@@ -81,11 +71,12 @@ You can create a livestream session from an existing hunting query, or create yo
8171

8272
## Receive notifications when new events occur
8373

84-
Because livestream notifications for new events use Azure portal notifications, you see these notifications whenever you use the Azure portal. For example:
74+
Livestream notifications for new events appear with the Azure or Defender portal notifications. For example:
8575

8676
![Azure portal notification for livestream](./media/livestream/notification.png)
8777

88-
Select the notification to open the **Livestream** pane.
78+
1. In the Azure or Defender portal, go to the notifications on the top right-hand side of the portal page.
79+
1. Select the notification to open the **Livestream** pane.
8980

9081
## Elevate a livestream session to an alert
9182

166 KB
Loading
166 KB
Loading
65.5 KB
Loading

0 commit comments

Comments
 (0)