Skip to content

Commit be78c3b

Browse files
committed
remove
1 parent a1d3133 commit be78c3b

File tree

1 file changed

+0
-36
lines changed

1 file changed

+0
-36
lines changed

articles/defender-for-iot/organizations/how-to-accelerate-alert-incident-response.md

Lines changed: 0 additions & 36 deletions
Original file line numberDiff line numberDiff line change
@@ -111,42 +111,6 @@ If you're currently using an on-premises management console with cloud-connected
111111

112112
Your rules are added to the list of suppression rules on the **Suppression rules (Preview)** page. Select a rule to edit or delete it as needed.
113113

114-
### Create alert exclusion rules on an on-premises management console
115-
116-
We recommend creating alert exclusion rules on an on-premises management console only for locally managed sensors. For cloud-connected sensors, any suppression rules created on the Azure portal will override exclusion rules created on the on-premises management console for that sensor.
117-
118-
**To create an alert exclusion rule**:
119-
120-
1. Sign into your on-premises management console and select **Alert Exclusion** on the left-hand menu.
121-
122-
1. On the **Alert Exclusion** page, select the **+** button at the top-right to add a new rule.
123-
124-
1. In the **Create Exclusion Rule** dialog, enter the following details:
125-
126-
|Name |Description |
127-
|---------|---------|
128-
|**Name** | Enter a meaningful name for your rule. The name can't contain quotes (`"`). |
129-
|**By Time Period** | Select a time zone and the specific time period you want the exclusion rule to be active, and then select **ADD**. <br><br>Use this option to create separate rules for different time zones. For example, you might need to apply an exclusion rule between 8:00 AM and 10:00 AM in three different time zones. In this case, create three separate exclusion rules that use the same time period and the relevant time zone. |
130-
|**By Device Address** | Select and enter the following values, and then select **ADD**: <br><br>- Select whether the designated device is a source, destination, or both a source and destination device. <br>- Select whether the address is an IP address, MAC address, or subnet <br>- Enter the value of the IP address, MAC address, or subnet. |
131-
|**By Alert Title** | Select one or more alerts to add to the exclusion rule and then select **ADD**. To find alert titles, enter all, or part of an alert title and select the one you want from the dropdown list. |
132-
|**By Sensor Name** | Select one or more sensors to add to the exclusion rule and then select **ADD**. To find sensor names, enter all or part of the sensor name and select the one you want from the dropdown list. |
133-
134-
> [!IMPORTANT]
135-
> Alert exclusion rules are `AND` based, which means that alerts are only excluded when all rule conditions are met.
136-
> If a rule condition is not defined, all options are included. For example, if you don't include the name of a sensor in the rule, the rule is applied to all sensors.
137-
138-
A summary of the rule parameters is shown at the bottom of the dialog.
139-
140-
1. Check the rule summary shown at the bottom of the **Create Exclusion Rule** dialog and then select **SAVE**
141-
142-
**To create alert exclusion rules via API**:
143-
144-
Use the [Defender for IoT API](references-work-with-defender-for-iot-apis.md) to create on-premises management console alert exclusion rules from an external ticketing system or other system that manage network maintenance processes.
145-
146-
Use the [maintenanceWindow (Create alert exclusions)](api/management-alert-apis.md#maintenancewindow-create-alert-exclusions) API to define the sensors, analytics engines, start time, and end time to apply the rule. Exclusion rules created via API are shown in the on-premises management console as read-only.
147-
148-
For more information, see [Defender for IoT API reference](references-work-with-defender-for-iot-apis.md).
149-
150114
## Allow internet connections on an OT network
151115

152116
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.

0 commit comments

Comments
 (0)