Skip to content

Commit 1979643

Browse files
committed
edit pass: sentinel-threat-intelligence-batch2
1 parent 6d14268 commit 1979643

File tree

4 files changed

+17
-17
lines changed

4 files changed

+17
-17
lines changed

articles/sentinel/add-entity-to-threat-intelligence.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -22,21 +22,21 @@ With Microsoft Sentinel, you can flag these types of entities from within your i
2222

2323
## Add an entity to your threat intelligence
2424

25-
The [Incident details page](investigate-incidents.md) and the investigation graph give you two ways to add entities to threat intelligence. Both ways are shown here.
25+
The [Incident details page](investigate-incidents.md) and the investigation graph give you two ways to add entities to threat intelligence.
2626

2727
# [Incident details page](#tab/incidents)
2828

2929
1. On the Microsoft Sentinel menu, select **Incidents** from the **Threat management** section.
3030

3131
1. Select an incident to investigate. On the **Incident details** pane, select **View full details** to open the **Incident details** page.
3232

33-
:::image type="content" source="media/add-entity-to-threat-intelligence/incident-details-overview.png" alt-text="Screenshot that shows the Incident details page." lightbox="media/add-entity-to-threat-intelligence/incident-details-overview.png":::
34-
3533
1. On the **Entities** pane, find the entity that you want to add as a threat indicator. (You can filter the list or enter a search string to help you locate it.)
3634

35+
:::image type="content" source="media/add-entity-to-threat-intelligence/incident-details-overview.png" alt-text="Screenshot that shows the Incident details page." lightbox="media/add-entity-to-threat-intelligence/incident-details-overview.png":::
36+
3737
1. Select the three dots to the right of the entity, and select **Add to TI** from the pop-up menu.
3838

39-
Only add the following types of entities as threat indicators:
39+
Add only the following types of entities as threat indicators:
4040

4141
- Domain name
4242
- IP address (IPv4 and IPv6)
@@ -75,20 +75,20 @@ Whichever of the two interfaces you choose, you end up here.
7575
- **Types**
7676
- The type of indicator represented by the entity you're adding.
7777
- Dropdown list with possible values: `ipv4-addr`, `ipv6-addr`, `URL`, `file`, and `domain-name`.
78-
- Required. Automatically populated based on the **entity type**.
78+
- Required. Automatically populated based on the *entity type*.
7979

8080
- **Value**
8181
- The name of this field changes dynamically to the selected indicator type.
8282
- The value of the indicator itself.
83-
- Required. Automatically populated by the **entity value**.
83+
- Required. Automatically populated by the *entity value*.
8484

8585
- **Tags**
8686
- Free-text tags you can add to the indicator.
87-
- Optional. Automatically populated by the **incident ID**. You can add others.
87+
- Optional. Automatically populated by the *incident ID*. You can add others.
8888

8989
- **Name**
9090
- Name of the indicator. This name is what appears in your list of indicators.
91-
- Optional. Automatically populated by the **incident name.**
91+
- Optional. Automatically populated by the *incident name*.
9292

9393
- **Created by**
9494
- Creator of the indicator.
@@ -126,7 +126,7 @@ Whichever of the two interfaces you choose, you end up here.
126126

127127
:::image type="content" source="media/add-entity-to-threat-intelligence/new-indicator-panel.png" alt-text="Screenshot that shows entering information in the new threat indicator pane.":::
128128

129-
1. When all the fields are filled in to your satisfaction, select **Apply**. A confirmation message appears in the upper-right corner stating that your indicator was created.
129+
1. When all the fields are filled in to your satisfaction, select **Apply**. A message appears in the upper-right corner to confirm that your indicator was created.
130130

131131
1. The entity is added as a threat indicator in your workspace. You can find it [in the list of indicators on the Threat intelligence page](work-with-threat-indicators.md#find-and-view-your-indicators-on-the-threat-intelligence-page). You can also find it [in the ThreatIntelligenceIndicators table in Logs](work-with-threat-indicators.md#find-and-view-your-indicators-in-logs).
132132

articles/sentinel/indicators-bulk-file-import.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -106,7 +106,7 @@ Review each template to ensure that your indicators are imported successfully. B
106106

107107
1. Delete the entire first row from the template to remove the comments before upload.
108108

109-
- The maximum file size for a CSV file import is 50 MB.
109+
The maximum file size for a CSV file import is 50 MB.
110110

111111
Here's an example domain-name indicator that uses the CSV template:
112112

@@ -125,7 +125,7 @@ Phishing,"demo, csv",MDTI article - Franken-Phish domainname,Entity appears in M
125125

126126
1. Close the last indicator in the array by using the `}` without a comma.
127127

128-
- The maximum file size for a JSON file import is 250 MB.
128+
The maximum file size for a JSON file import is 250 MB.
129129

130130
Here's an example `ipv4-addr` indicator that uses the JSON template:
131131

articles/sentinel/use-matching-analytics-to-detect-threats.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,15 +15,15 @@ ms.collection: usx-security
1515

1616
# Use matching analytics to detect threats
1717

18-
Take advantage of threat intelligence produced by Microsoft to generate high-fidelity alerts and incidents with the **Microsoft Defender Threat Intelligence Analytics** rule. This built-in rule in Microsoft Sentinel matches indicators with Common Event Format (CEF) logs, Windows domain name system (DNS) events with domain and IPv4 threat indicators, syslog data, and more.
18+
Take advantage of threat intelligence produced by Microsoft to generate high-fidelity alerts and incidents with the **Microsoft Defender Threat Intelligence Analytics** rule. This built-in rule in Microsoft Sentinel matches indicators with Common Event Format (CEF) logs, Windows DNS events with domain and IPv4 threat indicators, syslog data, and more.
1919

2020
> [!IMPORTANT]
2121
> 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 more legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
2222
>
2323
2424
## Prerequisites
2525

26-
To produce high-fidelity alerts and incidents, one or more of the supported data connectors must be installed. A premium Microsoft Defender Threat Intelligence license isn't required. Install the appropriate solutions from the **Content hub** to connect these data sources:
26+
You must install one or more of the supported data connectors to produce high-fidelity alerts and incidents. A premium Microsoft Defender Threat Intelligence license isn't required. Install the appropriate solutions from the **Content hub** to connect these data sources:
2727

2828
- Common Event Format
2929
- DNS (preview)
@@ -79,15 +79,15 @@ Use the following steps to triage through the incidents generated by the **Micro
7979

8080
1. In the Microsoft Sentinel workspace where you enabled the **Microsoft Defender Threat Intelligence Analytics** rule, select **Incidents**, and search for **Microsoft Defender Threat Intelligence Analytics**.
8181

82-
Any incidents found are shown in the grid.
82+
Any incidents that are found appear in the grid.
8383

8484
1. Select **View full details** to view entities and other details about the incident, such as specific alerts.
8585

8686
Here's an example.
8787

8888
:::image type="content" source="media/use-matching-analytics-to-detect-threats/matching-analytics.png" alt-text="Screenshot of incident generated by matching analytics with details pane.":::
8989

90-
1. Observe the severity assigned to the alerts and the incident. Depending on how the indicator is matched, an appropriate severity is assigned to an alert from `Informational` to `High`. For example, if the indicator is matched with firewall logs that allowed the traffic, a high-severity alert is generated. If the same indicator was matched with firewall logs that blocked the traffic, the alert generated is low or medium.
90+
1. Observe the severity assigned to the alerts and the incident. Depending on how the indicator is matched, an appropriate severity is assigned to an alert from `Informational` to `High`. For example, if the indicator is matched with firewall logs that allowed the traffic, a high-severity alert is generated. If the same indicator was matched with firewall logs that blocked the traffic, the generated alert is low or medium.
9191

9292
Alerts are then grouped on a per-observable basis of the indicator. For example, all alerts generated in a 24-hour time period that match the `contoso.com` domain are grouped into a single incident with a severity assigned based on the highest alert severity.
9393

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ Here's an example.
5353
5454
### Find and view your indicators in Logs
5555

56-
This procedure describes how to view your imported threat indicators in the Microsoft Sentinel **Logs** area, together with other Microsoft Sentinel event data, regardless of the source feed or the connector used.
56+
This procedure describes how to view your imported threat indicators in the Microsoft Sentinel **Logs** area, together with other Microsoft Sentinel event data, regardless of the source feed or the connector that you used.
5757

5858
Imported threat indicators are listed in the Microsoft Sentinel `ThreatIntelligenceIndicator` table. This table is the basis for threat intelligence queries run elsewhere in Microsoft Sentinel, such as in **Analytics** or **Workbooks**.
5959

@@ -97,7 +97,7 @@ Tagging threat indicators is an easy way to group them together to make them eas
9797

9898
With Microsoft Sentinel, you can also edit indicators, whether they were created directly in Microsoft Sentinel or come from partner sources, like TIP and TAXII servers. For indicators created in Microsoft Sentinel, all fields are editable. For indicators that come from partner sources, only specific fields are editable, including tags, **Expiration date**, **Confidence**, and **Revoked**. Either way, only the latest version of the indicator appears on the **Threat Intelligence** page. For more information on how indicators are updated, see [Understand threat intelligence](understand-threat-intelligence.md#view-and-manage-your-threat-indicators).
9999

100-
## Workbooks provide insights about your threat intelligence
100+
## Gain insights about your threat intelligence with workbooks
101101

102102
Use a purpose-built Microsoft Sentinel workbook to visualize key information about your threat intelligence in Microsoft Sentinel, and customize the workbook according to your business needs.
103103

0 commit comments

Comments
 (0)