Skip to content

Commit 8a9fc2a

Browse files
committed
removing procedure to change threshold
1 parent 73490aa commit 8a9fc2a

File tree

2 files changed

+2
-19
lines changed

2 files changed

+2
-19
lines changed

articles/defender-for-iot/organizations/how-to-manage-individual-sensors.md

Lines changed: 0 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -429,20 +429,6 @@ Maximum size for uploaded files is 2 GB.
429429
> [!TIP]
430430
> Select **Clear All** to clear the sensor of all PCAP files loaded.
431431
432-
## Modify notification auto-resolve thresholds
433-
434-
By default, selected device notifications are automatically resolved if they aren't dismissed or otherwise handled within 14 days. Admin users can change this threshold to more or fewer days in the OT sensor's system settings.
435-
436-
**To modify auto-resolve thresholds**:
437-
438-
1. Sign into your OT sensor as an **Admin** user.
439-
1. Select **System settings** > **Advanced configurations** > **Conflicts**.
440-
1. Locate the `notifications_resolve_threshold_days=14` line and change `14` to another integer.
441-
1. Select **Save** > **Close** to save your changes.
442-
443-
For more information, see [Manage device notifications](how-to-work-with-the-sensor-device-map.md#manage-device-notifications).
444-
445-
446432
## Adjust system properties
447433

448434
System properties control various operations and settings in the sensor. Editing or modifying them might damage the operation of the sensor console.

articles/defender-for-iot/organizations/how-to-work-with-the-sensor-device-map.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -177,10 +177,8 @@ For example, you might receive a notification about an inactive device that need
177177
- Select **Select All** to show which notifications can be [handled together](#handling-multiple-notifications-together). Clear selections for specific notifications, and then select **Accept All** or **Dismiss All** to handle any remaining selected notifications together.
178178

179179
> [!NOTE]
180-
> By default, selected notifications are automatically resolved if they aren't dismissed or otherwise handled within 14 days. Admin users can change this threshold in the OT sensor's system setting.
181-
>
182-
> For more information, see the action indicated in the **Auto-resolve** column in the table [below](#device-notification-responses) and <xref>.
183-
>
180+
> Selected notifications are automatically resolved if they aren't dismissed or otherwise handled within 14 days. For more information, see the action indicated in the **Auto-resolve** column in the table [below](#device-notification-responses).
181+
>
184182
185183
### Handling multiple notifications together
186184

@@ -200,7 +198,6 @@ The following table lists available responses for each notification, and when we
200198
| Type | Description | Available responses | Auto-resolve|
201199
|--|--|--|--|
202200
| **New IP detected** | A new IP address is associated with the device. This may occur in the following scenarios: <br><br>- A new or additional IP address was associated with a device already detected, with an existing MAC address.<br><br> - A new IP address was detected for a device that's using a NetBIOS name. <br /><br /> - An IP address was detected as the management interface for a device associated with a MAC address. <br /><br /> - A new IP address was detected for a device that's using a virtual IP address. | - **Set Additional IP to Device**: Merge the devices <br />- **Replace Existing IP**: Replaces any existing IP address with the new address <br /> - **Dismiss**: Remove the notification. |**Dismiss** |
203-
| <!--check w meir and remove this-->**New OT devices** | A subnet includes an OT device that's not defined in an ICS subnet. <br><br>This may occur when a device is detected that can be defined as an ICS subnet. We recommend defining such devices as ICS subnets to differentiate between OT and IT devices on the map. | - **Set as ICS Subnet**: Define the device as an ICS subnet. <br>- **Dismiss**: Remove the notification if the device isn't part of the subnet. |No automatic handling|
204201
| **No subnets configured** | No subnets are currently configured in your network. <br /><br /> We recommend configuring subnets for the ability to differentiate between OT and IT devices on the map. | - **Open Subnets Configuration** and [configure subnets](how-to-control-what-traffic-is-monitored.md#configure-subnets). <br />- **Dismiss**: Remove the notification. |**Dismiss** |
205202
| **Operating system changes** | One or more new operating systems have been associated with the device. | - Select the name of the new OS that you want to associate with the device.<br /> - **Dismiss**: Remove the notification. |No automatic handling<!--Set with new operating system only if not already configured manually. <br><br>If the operating system has already been configured: **Dismiss**.-->|
206203
| **New subnets** | New subnets were discovered. |- **Learn**: Automatically add the subnet.<br />- **Open Subnet Configuration**: Add all missing subnet information.<br />- **Dismiss**<br />Remove the notification. |**Dismiss** |

0 commit comments

Comments
 (0)