Skip to content

Commit dba0964

Browse files
Merge pull request #228847 from yoninalmsft/22.3.6-sensor
22.3.6 sensor device inventory updates
2 parents d12460d + cb12fcb commit dba0964

File tree

2 files changed

+22
-14
lines changed

2 files changed

+22
-14
lines changed

articles/defender-for-iot/organizations/how-to-investigate-sensor-detections-in-a-device-inventory.md

Lines changed: 20 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Manage your OT device inventory from a sensor console
33
description: Learn how to view and manage OT devices (assets) from the Device inventory page on a sensor console.
4-
ms.date: 07/21/2022
4+
ms.date: 02/28/2023
55
ms.topic: how-to
66
---
77

@@ -49,7 +49,13 @@ If you're working with a cloud-connected sensor, any edits you make in the senso
4949

5050
**To edit device details**:
5151

52-
1. Select one or more devices in the grid, and then select **View full details** in the pane on the right.
52+
1. Select a device in the grid, and then select **Edit** in the toolbar at the top of the page.
53+
54+
1. In the **Edit** pane on the right, modify the device fields as needed, and then select **Save** when you're done.
55+
56+
You can also open the edit pane from the device details page:
57+
58+
1. Select a device in the grid, and then select **View full details** in the pane on the right.
5359

5460
1. In the device details page, select **Edit Properties**.
5561

@@ -61,8 +67,9 @@ Editable fields include:
6167
- Device name
6268
- Device type
6369
- OS
64-
- Purdue layer
70+
- Purdue level
6571
- Description
72+
- Scanner or programming device
6673

6774
For more information, see [Device inventory column reference](#device-inventory-column-reference).
6875

@@ -91,11 +98,9 @@ For example, if you merge two devices, each with an IP address, both IP addresse
9198

9299
**To merge devices from the device inventory:**
93100

94-
1. Use the SHIFT key to select two devices from the inventory, and then right-click one of them.
101+
In the device inventory grid, select the devices you want to merge, and then select **Merge** in the toolbar at the top of the page.
95102

96-
1. Select **Merge** to merge the devices. This can take up to 2 minutes to complete.
97-
98-
1. When the **Set merge device attributes** dialog appears, enter a meaningful name for your merged device, and then select **Save**.
103+
The devices are merged, and a confirmation message appears at the top right.
99104

100105
## View inactive devices
101106

@@ -120,14 +125,17 @@ You may want to delete devices from your device inventory, such as if they've be
120125

121126
Deleted devices are removed from the **Device map** and the device inventories on the Azure portal and on-premises management console, and aren't calculated when generating reports, such as Data Mining, Risk Assessment, or Attack Vector reports.
122127

123-
**To delete a single device**:
128+
**To delete one or more devices**:
129+
130+
You can delete a device when it's been inactive for more than 10 minutes.
131+
132+
1. In the **Device inventory** page, select the device or devices you want to delete, and then select **Delete** :::image type="icon" source="media/how-to-manage-device-inventory-on-the-cloud/delete-device.png" border="false"::: in the toolbar at the top of the page.
124133

125-
You can delete a single device when they’ve been inactive for more than 10 minutes.
134+
1. At the prompt, select **Confirm** to confirm that you want to delete the device from Defender for IoT.
126135

127-
1. In the **Device inventory** page, select the device you want to delete, and then select **Delete** :::image type="icon" source="media/how-to-manage-device-inventory-on-the-cloud/delete-device.png" border="false"::: in the toolbar at the top of the page.
128-
1. At the prompt, select **Yes** to confirm that you want to delete the device from Defender for IoT.
136+
A confirmation message appears at the top right.
129137

130-
**To delete all inactive devices**
138+
**To delete all inactive devices**:
131139

132140
This procedure is supported for the *cyberx* and admin users only.
133141

articles/defender-for-iot/organizations/references-data-retention.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,8 +18,8 @@ The following table lists how long device data is stored in each Defender for Io
1818
| Storage type | Details |
1919
|---------|---------|
2020
| **Azure portal** | 90 days from the date of the **Last activity** value. <br><br> For more information, see [Manage your device inventory from the Azure portal](how-to-manage-device-inventory-for-organizations.md). |
21-
| **OT network sensor** | The retention of device inventory data isn't limited by time. <br><br> For more information, see [Manage your OT device inventory from a sensor console](how-to-investigate-sensor-detections-in-a-device-inventory.md). |
22-
| **On-premises management console** | The retention of device inventory data isn't limited by time. <br><br> For more information, see [Manage your OT device inventory from an on-premises management console](how-to-investigate-all-enterprise-sensor-detections-in-a-device-inventory.md). |
21+
| **OT network sensor** | 90 days from the date of the **Last activity** value. <br><br> For more information, see [Manage your OT device inventory from a sensor console](how-to-investigate-sensor-detections-in-a-device-inventory.md). |
22+
| **On-premises management console** | 90 days from the date of the **Last activity** value. <br><br> For more information, see [Manage your OT device inventory from an on-premises management console](how-to-investigate-all-enterprise-sensor-detections-in-a-device-inventory.md). |
2323

2424
## Alert data retention
2525

0 commit comments

Comments
 (0)