Skip to content

Commit d7bbf73

Browse files
authored
Merge pull request #201969 from cwatson-cat/docs-editor/work-with-threat-indicators-1655480580
Sentinel TI - Add table for IP indicator matching
2 parents 591ecd4 + 348da02 commit d7bbf73

File tree

1 file changed

+32
-20
lines changed

1 file changed

+32
-20
lines changed

articles/sentinel/work-with-threat-indicators.md

Lines changed: 32 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,6 @@ The **Threat intelligence** page also allows you to create threat indicators dir
7070

7171
> [!IMPORTANT]
7272
> GeoLocation and WhoIs enrichment is currently in PREVIEW. The [Azure Preview Supplemental Terms](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) include additional legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
73-
>
7473
7574
#### Create a new indicator
7675

@@ -123,20 +122,22 @@ Below is an example of how to enable and configure a rule to generate security a
123122
:::image type="content" source="media/work-with-threat-indicators/threat-intel-create-analytics-rule.png" alt-text="Create analytics rule":::
124123

125124
1. The rule logic portion of the wizard has been pre-populated with the following items:
126-
- The query that will be used in the rule.
127125

128-
- Entity mappings, which tell Microsoft Sentinel how to recognize entities like Accounts, IP addresses, and URLs, so that **incidents** and **investigations** understand how to work with the data in any security alerts generated by this rule.
126+
- The query that will be used in the rule.
129127

130-
- The schedule to run this rule.
128+
- Entity mappings, which tell Microsoft Sentinel how to recognize entities like Accounts, IP addresses, and URLs, so that **incidents** and **investigations** understand how to work with the data in any security alerts generated by this rule.
131129

132-
- The number of query results needed before a security alert is generated.
130+
- The schedule to run this rule.
131+
132+
- The number of query results needed before a security alert is generated.
133133

134134
The default settings in the template are:
135-
- Run once an hour.
136135

137-
- Match any IP address threat indicators from the **ThreatIntelligenceIndicator** table with any IP address found in the last one hour of events from the **AzureActivity** table.
136+
- Run once an hour.
137+
138+
- Match any IP address threat indicators from the **ThreatIntelligenceIndicator** table with any IP address found in the last one hour of events from the **AzureActivity** table.
138139

139-
- Generate a security alert if the query results are greater than zero, meaning if any matches are found.
140+
- Generate a security alert if the query results are greater than zero, meaning if any matches are found.
140141

141142
You can leave the default settings or change them to meet your requirements, and you can define incident-generation settings on the **Incident settings** tab. For more information, see [Create custom analytics rules to detect threats](detect-threats-custom.md). When you are finished, select the **Automated response** tab.
142143

@@ -156,7 +157,6 @@ IMPORTANT: Microsoft Sentinel refreshes indicators every 14 days to make sure th
156157

157158
> [!IMPORTANT]
158159
> Matching analytics is currently in PREVIEW. See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for additional legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
159-
>
160160
161161
[Create a rule](detect-threats-built-in.md#use-built-in-analytics-rules) using the built-in **Microsoft Threat Intelligence Matching Analytics** analytics rule template to have Microsoft Sentinel match Microsoft-generated threat intelligence data with the logs you've ingested in to Microsoft Sentinel.
162162

@@ -192,41 +192,52 @@ In the **Threat Intelligence** page:
192192

193193
### Supported log sources for matching analytics
194194

195-
The **Microsoft Threat Intelligence Matching Analytics** rule is currently supported for the following log sources:
195+
The Microsoft Threat Intelligence Matching Analytics matches the log sources in the following tables with domain and IP indicators.
196+
197+
#### Domain indicator matching
196198

197199
| Log source | Description |
198200
| --------- | --------- |
199201
| [CEF](connect-common-event-format.md) | Matching is done for all CEF logs that are ingested in the Log Analytics **CommonSecurityLog** table, except for any where the `DeviceVendor` is listed as `Cisco`. <br><br>To match Microsoft-generated threat intelligence with CEF logs, make sure to map the domain in the `RequestURL` field of the CEF log. |
200202
| [DNS](./data-connectors-reference.md#windows-dns-server-preview) | Matching is done for all DNS logs that are lookup DNS queries from clients to DNS services (`SubType == "LookupQuery"`). DNS queries are processed only for IPv4 (`QueryType=”A”`) and IPv6 queries (`QueryType=” AAAA”`).<br><br>To match Microsoft-generated threat intelligence with DNS logs, no manual mapping of columns is needed, as all columns are standard from Windows DNS Server, and the domains will be in the `Name` column by default. |
201203
| [Syslog](connect-syslog.md) | Matching is currently done for only for Syslog events where the `Facility` is `cron`. <br><br>To match Microsoft-generated threat intelligence with Syslog, no manual mapping of columns is needed. The details come in the `SyslogMessage` field of the Syslog by default, and the rule will parse the domain directly from the SyslogMessage. |
202204

205+
#### IP indicator matching
203206

207+
Microsoft Threat Intelligence Matching Analytics currently matches only with IPv4 indicators.
208+
209+
| Log source | Description |
210+
| --------- | --------- |
211+
|[CEF](connect-common-event-format.md) |Matching is done for all CEF logs that are ingested in the **CommonSecurityLog** table of log analytics except for ones that have `DeviceVendor` as `Cisco`. <br><br>To match Microsoft generated threat intelligence with CEF logs, no manual mapping needs to be done. The IP is populated in the `DestinationIP` field by default.|
212+
| [DNS](./data-connectors-reference.md#windows-dns-server-preview) | Matching is done for all DNS logs that are lookup DNS queries from clients to DNS services (`SubType == "LookupQuery"`). Threat intelligence matching analytics only process DNS queries for IPv4 (`QueryType="A"`). <br><br>To match Microsoft-generated threat intelligence with DNS logs, no manual mapping of columns is needed. All columns are standard from Windows DNS Server. The IPs are in the `IPAddresses` column by default. |
213+
| [Syslog](connect-syslog.md) | Matching is currently done for only for Syslog events where the `Facility` is `cron`. <br><br>To match Microsoft-generated threat intelligence with Syslog, no manual mapping of columns is needed. The details come in the `SyslogMessage` field of the Syslog by default. The rule parses the IP directly from the `SyslogMessage`. |
204214

205215
## Workbooks provide insights about your threat intelligence
206216

207217
You can use a purpose-built Microsoft Sentinel workbook to visualize key information about your threat intelligence in Microsoft Sentinel, and you can easily customize the workbook according to your business needs.
208218

209219
Here's how to find the threat intelligence workbook provided in Microsoft Sentinel, and an example of how to make edits to the workbook to customize it.
210220

211-
1. From the [Azure portal](https://portal.azure.com/), navigate to the **Microsoft Sentinel** service.
221+
1. From the [Azure portal](https://portal.azure.com/), navigate to the **Microsoft Sentinel** service.
212222

213-
1. Choose the **workspace** to which you’ve imported threat indicators using either threat intelligence data connector.
223+
1. Choose the **workspace** to which you’ve imported threat indicators using either threat intelligence data connector.
214224

215-
1. Select **Workbooks** from the **Threat management** section of the Microsoft Sentinel menu.
225+
1. Select **Workbooks** from the **Threat management** section of the Microsoft Sentinel menu.
216226

217-
1. Find the workbook titled **Threat Intelligence** and verify you have data in the **ThreatIntelligenceIndicator** table as shown below.
227+
1. Find the workbook titled **Threat Intelligence** and verify you have data in the **ThreatIntelligenceIndicator** table as shown below.
218228

219-
:::image type="content" source="media/work-with-threat-indicators/threat-intel-verify-data.png" alt-text="Verify data":::
229+
:::image type="content" source="media/work-with-threat-indicators/threat-intel-verify-data.png" alt-text="Verify data":::
220230

221-
1. Select the **Save** button and choose an Azure location to store the workbook. This step is required if you are going to modify the workbook in any way and save your changes.
231+
1. Select the **Save** button and choose an Azure location to store the workbook. This step is required if you are going to modify the workbook in any way and save your changes.
222232

223-
1. Now select the **View saved workbook** button to open the workbook for viewing and editing.
233+
1. Now select the **View saved workbook** button to open the workbook for viewing and editing.
224234

225-
1. You should now see the default charts provided by the template. To modify a chart, select the **Edit** button at the top of the page to enter editing mode for the workbook.
235+
1. You should now see the default charts provided by the template. To modify a chart, select the **Edit** button at the top of the page to enter editing mode for the workbook.
226236

227-
1. Add a new chart of threat indicators by threat type. Scroll to the bottom of the page and select **Add Query**.
237+
1. Add a new chart of threat indicators by threat type. Scroll to the bottom of the page and select **Add Query**.
238+
239+
1. Add the following text to the **Log Analytics workspace Log Query** text box:
228240

229-
1. Add the following text to the **Log Analytics workspace Log Query** text box:
230241
```kusto
231242
ThreatIntelligenceIndicator
232243
| summarize count() by ThreatType
@@ -245,6 +256,7 @@ There is also a rich community of [Azure Monitor workbooks on GitHub](https://gi
245256
## Next steps
246257
247258
In this article, you learned all the ways you can work with threat intelligence indicators throughout Microsoft Sentinel. For more about threat intelligence in Microsoft Sentinel, see the following articles:
259+
248260
- [Understand threat intelligence in Microsoft Sentinel](understand-threat-intelligence.md).
249261
- Connect Microsoft Sentinel to [STIX/TAXII threat intelligence feeds](./connect-threat-intelligence-taxii.md).
250262
- [Connect threat intelligence platforms](./connect-threat-intelligence-tip.md) to Microsoft Sentinel.

0 commit comments

Comments
 (0)