Skip to content

Commit 21da3bd

Browse files
committed
device new
1 parent 4d1c17a commit 21da3bd

File tree

2 files changed

+8
-10
lines changed

2 files changed

+8
-10
lines changed

articles/defender-for-iot/organizations/device-inventory.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,6 @@ For example:
1919

2020
:::image type="content" source="media/device-inventory/azure-device-inventory.png" alt-text="Screenshot of the Defender for IoT Device inventory page in the Azure portal." lightbox="media/device-inventory/azure-device-inventory.png":::
2121

22-
2322
## Supported devices
2423

2524
Defender for IoT's device inventory supports the following device classes:
@@ -49,7 +48,6 @@ Defender for IoT device inventory is available in the following locations:
4948
| **Microsoft Defender XDR** | Enterprise IoT devices detected by Microsoft Defender for Endpoint agents | Correlate devices across Microsoft Defender XDR in purpose-built alerts, vulnerabilities, and recommendations. |
5049
|**OT network sensor consoles** | Devices detected by that OT sensor | - View all detected devices across a network device map<br><br>- View related events on the **Event timeline** |
5150
|**An on-premises management console** | Devices detected across all connected OT sensors | Enhance device data by importing data manually or via script |
52-
|
5351

5452
For more information, see:
5553

@@ -101,7 +99,7 @@ The following table lists the columns available in the Defender for IoT device i
10199
> [!NOTE]
102100
> Noted features listed below are in PREVIEW. The [Azure Preview Supplemental Terms](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) include other legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
103101
104-
|Name |Description
102+
|Name |Description |
105103
|---------|---------|
106104
|**Authorization** * |Editable. Determines whether or not the device is marked as *authorized*. This value might need to change as the device security changes. |
107105
|**Business Function** | Editable. Describes the device's business function. |

articles/defender-for-iot/organizations/ot-deploy/update-device-inventory.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.topic: how-to
77

88
# Verify and update your detected device inventory
99

10-
This article is one in a series of articles describing the [deployment path](../ot-deploy/ot-deploy-path.md) for OT monitoring with Microsoft Defender for IoT, and describes how to review your device inventory and enhance security monitoring with fine-tuned device details.
10+
This article is one in a series of articles describing the [deployment path](../ot-deploy/ot-deploy-path.md) for Opertaional Technology (OT) monitoring with Microsoft Defender for IoT, and describes how to review your device inventory and enhance security monitoring with fine-tuned device details.
1111

1212
:::image type="content" source="../media/deployment-paths/progress-fine-tuning-ot-monitoring.png" alt-text="Diagram of a progress bar with Fine-tune OT monitoring highlighted." border="false" lightbox="../media/deployment-paths/progress-fine-tuning-ot-monitoring.png":::
1313

@@ -21,15 +21,15 @@ Before performing the procedures in this article, make sure that you have:
2121

2222
This step is performed by your deployment teams.
2323

24-
## View your device inventory on the Azure portal
24+
## View the device inventory on your OT sensor
2525

2626
1. Sign into your OT sensor and select the **Device inventory** page.
2727

28-
1. Select **Edit Columns** to view additional information in the grid so that you can review the data detected for each device.
28+
1. Select **Edit Columns** to make changes to the grid layout and display more data fields for reviewing the data detected for each device.
2929

30-
We especially recommend reviewing data for the **Name**, **Class**, **Type**, and **Subtype**, **Authorization**, **Scanner device**, and **Programming device** columns.
30+
We especially recommend reviewing data for the **Name**, **Type**, **Authorization**, **Scanner device**, and **Programming device** columns.
3131

32-
1. Understand the devices that the OT sensor's detected, and identify any sensors where you'll need to identify device properties.
32+
1. Review the devices listed in the device inventory, and identify the devices whose device properties must be edited.
3333

3434
## Edit device properties per device
3535

@@ -56,7 +56,7 @@ For each device where you need to edit device properties:
5656

5757
## Merge duplicate devices
5858

59-
As you review the devices detected on your device inventory, note whether multiple entries have been detected for the same device on your network.
59+
As you review the devices detected on your device inventory, note whether multiple entries were detected for the same device on your network.
6060

6161
For example, this might occur when you have a PLC with four network cards, a laptop with both WiFi and a physical network card, or a single workstation with multiple network cards.
6262

@@ -72,7 +72,7 @@ The devices and all their properties are merged in the device inventory. For exa
7272

7373
## Enhance device data (optional)
7474

75-
You may want to increase device visibility and enhance device data with more details than the default data detected.
75+
You might want to increase device visibility and enhance device data with more details than the default data detected.
7676

7777
- To increase device visibility to Windows-based devices, use the Defender for IoT [Windows Management Instrumentation (WMI) tool](../detect-windows-endpoints-script.md).
7878

0 commit comments

Comments
 (0)