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/defender-for-iot/organizations/how-to-accelerate-alert-incident-response.md
+38-9Lines changed: 38 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,15 +20,10 @@ This article describes the following methods for reducing OT network alert fatig
20
20
21
21
## Prerequisites
22
22
23
-
- To create alert comments or custom alert rules on an OT network sensor, you must have:
23
+
- To create alert comments or custom alert rules on an OT network sensor, you must have an OT network sensor installed and access to the sensor as an **Admin** user.
24
24
25
-
- An OT network sensor installed
26
-
- Access to the sensor as an **Admin** user.
27
-
28
-
- To create alert exclusion rules on an on-premises management console, you must have:
29
-
30
-
- An on-premises management console installed
31
-
- Access to the on-premises management console as an **Admin** user.
25
+
- To create a DNS allowlist on an OT sensor, you must have an OT network sensor installed and access to the sensor as a **Support** user.
26
+
- To create alert exclusion rules on an on-premises management console, you must have an on-premises management console installed and access to the on-premises management console as an **Admin** user.
32
27
33
28
For more information, see [Install OT agentless monitoring software](how-to-install-software.md) and [On-premises users and roles for OT monitoring with Defender for IoT](roles-on-premises.md).
34
29
@@ -89,6 +84,40 @@ Disable custom alert rules to prevent them from running without deleting them al
89
84
90
85
In the **Custom alert rules** page, select one or more rules, and then select **Disable**, **Enable**, or **Delete** in the toolbar as needed.
91
86
87
+
## Allow internet connections on an OT network
88
+
89
+
Decrease the number of unauthorized internet alerts by creating an allowlist of domain names on your OT sensor. When a DNS allowlist is configured, the sensor checks each unauthorized internet connectivity attempt against the list before triggering an alert. If the domain's FQDN is included in the allowlist, the sensor doesn’t trigger the alert and allows the traffic automatically.
90
+
91
+
All OT sensor users can view a currently configured list of domains in a [data mining report](how-to-create-data-mining-queries.md), including the FQDNs, resolved IP addresses, and the last resolution time.
92
+
93
+
94
+
**To define a DNS allowlist:**
95
+
96
+
1. Sign into your OT sensor as the *support* user and select the **Support** page.
97
+
98
+
1. In the search box, search for **DNS** and then locate the engine with the **Internet Domain Allowlist** description.
99
+
100
+
1. Select **Edit** :::image type="icon" source="media/how-to-generate-reports/manage-icon.png" border="false"::: for the **Internet Domain Allowlist** row. For example:
101
+
102
+
:::image type="content" source="media/how-to-accelerate-alert-incident-response/dns-edit-configuration.png" alt-text="Screenshot of how to edit configurations for DNS in the sensor console." lightbox="media/how-to-accelerate-alert-incident-response/dns-edit-configuration.png":::
103
+
104
+
1. In the **Edit configuration** pane > **Fqdn allowlist** field, enter one or more domain names. Separate multiple domain names with commas. Your sensor won't generate alerts for unauthorized internet connectivity attempts on the configured domains.
105
+
106
+
1. Select **Submit** to save your changes.
107
+
108
+
109
+
**To view the current allowlist in a data mining report:**
110
+
111
+
When selecting a category in your [custom data mining report](how-to-create-data-mining-queries.md#create-an-ot-sensor-custom-data-mining-report), make sure to select **Internet Domain Allowlist** under the **DNS** category.
112
+
113
+
For example:
114
+
115
+
:::image type="content" source="media/how-to-accelerate-alert-incident-response/data-mining-allowlist.png" alt-text="Screenshot of how to generate a custom data mining report for the allowlist in the sensor console." lightbox="media/how-to-accelerate-alert-incident-response/data-mining-allowlist.png":::
116
+
117
+
The generated data mining report shows a list of the allowed domains and each IP address that’s being resolved for those domains. The report also includes the TTL, in seconds, during which those IP addresses won't trigger an internet connectivity alert. For example:
118
+
119
+
:::image type="content" source="media/how-to-accelerate-alert-incident-response/data-mining-report-allowlist.png" alt-text="Screenshot of data mining report of allowlist in the sensor console." lightbox="media/how-to-accelerate-alert-incident-response/data-mining-report-allowlist.png":::
120
+
92
121
## Create alert exclusion rules on an on-premises management console
93
122
94
123
Create alert exclusion rules to instruct your sensors to ignore specific traffic on your network that would otherwise trigger an alert.
@@ -146,4 +175,4 @@ For more information, see
146
175
> [View and manage alerts on the the on-premises management console](how-to-work-with-alerts-on-premises-management-console.md)
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/how-to-create-data-mining-queries.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,7 @@ Create your own custom data mining report if you have reporting needs not covere
51
51
|---------|---------|
52
52
|**Name** / **Description**| Enter a meaningful name for your report and an optional description. |
53
53
|**Send to CM**| Select to send your report to the on-premises management console. |
54
-
|**Choose category**| Select the categories to include in your report. |
54
+
|**Choose category**| Select the categories to include in your report. <br><br> For example, select **Internet Domain Allowlist** under **DNS** to create a report of the allowed internet domains and their resolved IP addresses. |
55
55
|**Order by**| Select to sort your data by category or by activity. |
56
56
|**Filter by**| Define a filter for your report using any of the following parameters: <br><br> - **Results within the last**: Enter a number and then select **Minutes**, **Hours**, or **Days** <br> - **IP address / MAC address / Port**: Enter one or more IP addresses, MAC addresses, and ports to filter into your report. Enter a value and then select + to add it to the list.<br> - **Device group**: Select one or mode device groups to filter into your report. |
57
57
|**Add filter type**| Select to add any of the following filter types into your report. <br><br> - Transport (GENERIC) <br> - Protocol (GENERIC) <br> - TAG (GENERIC) <br> - Maximum value (GENERIC) <br> - State (GENERIC) <br> - Minimum value (GENERIC) <br><br> Enter a value in the relevant field and then select + to add it to the list. |
0 commit comments