Skip to content

Commit b16ca28

Browse files
committed
adding images
1 parent 13a40d9 commit b16ca28

File tree

3 files changed

+22
-12
lines changed

3 files changed

+22
-12
lines changed

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

Lines changed: 22 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -17,10 +17,10 @@ To perform the procedures in this article, make sure that you have:
1717

1818
- An OT network sensor [installed](ot-deploy/install-software-ot-sensor.md), [activated, and configured](how-to-activate-and-set-up-your-sensor.md), with network traffic ingested
1919

20-
- To view devices across multiple sensors in a zone, an on-premises management console [installed](ot-deploy/install-software-on-premises-management-console.md), [activated, and configured](how-to-activate-and-set-up-your-on-premises-management-console.md), with multiple sensors connected and assigned to sites and zones.
21-
2220
- Access to your OT sensor or on-premises management console. Users with the **Viewer** role can view data on the map. To import or export data or edit the map view, you need access as a **Security Analyst** or **Admin** user. For more information, see [On-premises users and roles for OT monitoring with Defender for IoT](roles-on-premises.md).
2321

22+
To view devices across multiple sensors in a zone, you'll also need an on-premises management console [installed](ot-deploy/install-software-on-premises-management-console.md), [activated, and configured](how-to-activate-and-set-up-your-on-premises-management-console.md), with multiple sensors connected and assigned to sites and zones.
23+
2424
## View devices on OT sensor device map
2525

2626
1. Sign into your OT sensor and select **Device map**. All devices detected by the OT sensor are displayed by default according to [Purdue layer](best-practices/understand-network-architecture.md#purdue-reference-model-and-defender-for-iot).
@@ -29,7 +29,11 @@ To perform the procedures in this article, make sure that you have:
2929

3030
- Devices with currently active alerts are highlighted in red
3131
- Starred devices are those that had been marked as important
32-
- Devices with no alerts are shown in black, or grey in the zoomed-in, connections view
32+
- Devices with no alerts are shown in black, or grey in the zoomed-in connections view
33+
34+
For example:
35+
36+
:::image type="content" source="media/how-to-work-with-maps/device-map-default.png" alt-text="Screenshot of a default view of an OT sensor's device map." lightbox="media/how-to-work-with-maps/device-map-default.png":::
3337

3438
1. Zoom in and select a specific device to view the connections between it and other devices, highlighted in blue.
3539

@@ -87,7 +91,7 @@ By default, IT devices are automatically aggregated by [subnet](how-to-control-w
8791
1. Select one or more expanded subnets and then select **Collapse All**.
8892

8993

90-
## Create a custom device group from an OT sensor device map
94+
## Create a custom device group
9195

9296
In addition to OT sensor's [built-in device groups](#built-in-device-map-groups), create new custom groups as needed to use when highlighting or filtering devices on the map.
9397

@@ -99,7 +103,7 @@ In addition to OT sensor's [built-in device groups](#built-in-device-map-groups)
99103
- From the **Copy from groups** menu, select any groups you want to copy devices from.
100104
- From the **Devices** menu, select any extra devices to add to your group.
101105

102-
## Import / export device data from an OT sensor device map
106+
## Import / export device data
103107

104108
Use one of the following options to import and export device data:
105109

@@ -108,7 +112,7 @@ Use one of the following options to import and export device data:
108112
- **Export Device Summary**. Select to export a high level summary of all currently displayed devices to a .CSV file.
109113

110114

111-
## Edit devices from the OT sensor device map
115+
## Edit devices
112116

113117
1. Sign into an OT sensor and select **Device map**.
114118

@@ -124,7 +128,7 @@ Use one of the following options to import and export device data:
124128
| **Add to custom group** | Creates a new [custom group](#create-a-custom-device-group-from-an-ot-sensor-device-map) with the selected device. |
125129
| **Delete** |Deletes the device from the inventory. |
126130

127-
## Merge devices from the OT sensor device map
131+
## Merge devices
128132

129133
You may want to merge devices if the OT sensor detected multiple network entities associated with a unique device, such as a PLC with four network cards, or a single laptop with both WiFi and a physical network card.
130134

@@ -147,7 +151,7 @@ You can only merge [authorized devices](device-inventory.md#unauthorized-devices
147151
It can take up to two minutes complete the merge. Merge events are listed in the OT sensor's event timeline.
148152

149153

150-
## Manage device notifications from an OT sensor device map
154+
## Manage device notifications
151155

152156
As opposed to alerts, which provide details about changes in your traffic that might present a threat to your network, device notifications on an OT sensor device map provide details about network activity that might require your attention, but aren't threats.
153157

@@ -159,10 +163,14 @@ For example, you might receive a notification about an inactive device that need
159163

160164
1. In the **Discovery Notifications** pane on the right, filter notifications as needed by time range, device, subnet, or operating systems.
161165

162-
1. Do one of the following:
166+
For example:
163167

164-
- Accept or dismiss each notification, one at a time.
165-
- Select **Select All** to show which notifications can be handled together.Clear selections for specific notifications, and then accept or dismiss any remaining selected notifications together.
168+
:::image type="content" source="media/how-to-work-with-maps/device-notifications.png" alt-text="Screenshot of device notifications on an OT sensor's Device map page." lightbox="media/how-to-work-with-maps/device-notifications.png":::
169+
170+
1. Each notification may have different mitigation options. Do one of the following:
171+
172+
- Handle one notification at a time, selecting a specific mitigation action, or selecting **Dismiss** to close the notification with no activity.
173+
- Select **Select All** to show which notifications can be handled together. Clear selections for specific notifications, and then select **Accept All** or **Dismiss All** to handle any remaining selected notifications together.
166174

167175
When you handle multiple notifications together, you may still have remaining notifications that need to be handled manually, such as for new IP addresses or no subnets detected.
168176

@@ -172,6 +180,8 @@ For example, you might receive a notification about an inactive device that need
172180
> - IT upgraded the OS across multiple network servers and you want to learn all of the new server versions.
173181
> - A group of devices is no longer active, and you want to instruct the OT sensor to remove the devices from the OT sensor.
174182
183+
### Device notification responses
184+
175185
The following table lists available responses for each notification, and when we recommend using each one:
176186

177187
| Type | Description | Available responses |
@@ -195,7 +205,7 @@ On the on-premises management console, zone maps show all network elements relat
195205

196206
1. Sign into an on-premises management console and select **Site Management** > **View Zone Map** for the zone you want to view. For example: <!--fix image-->
197207

198-
:::image type="content" source="media/how-to-work-with-asset-inventory-information/default-region-to-default-business-unit-v2.png" alt-text="Default region to default business unit.":::
208+
:::image type="content" source="media/how-to-work-with-asset-inventory-information/default-region-to-default-business-unit-v2.png" alt-text="Default region to default business unit." lightbox="media/how-to-work-with-asset-inventory-information/default-region-to-default-business-unit-v2.png":::
199209

200210
1. Use any of the following map tools to change your map display:
201211

321 KB
Loading
393 KB
Loading

0 commit comments

Comments
 (0)