Skip to content

Commit 401010a

Browse files
authored
Merge pull request #284538 from tarTech23/editab
Correct Device inventory editable
2 parents 6ae856b + 64fa800 commit 401010a

File tree

1 file changed

+52
-52
lines changed

1 file changed

+52
-52
lines changed

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

Lines changed: 52 additions & 52 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ Defender for IoT's device inventory helps you identify details about specific de
1111

1212
- **Manage all your IoT/OT devices** by building up-to-date inventory that includes all your managed and unmanaged devices
1313

14-
- **Protect devices with risk-based approach** to identify risks such as missing patches, vulnerabilities and prioritize fixes based on risk scoring and automated threat modeling
14+
- **Protect devices with risk-based approach** to identify risks such as missing patches, vulnerabilities, and prioritize fixes based on risk scoring and automated threat modeling
1515

1616
- **Update your inventory** by deleting irrelevant devices and adding organization-specific information to emphasize your organization preferences
1717

@@ -58,7 +58,7 @@ For more information, see:
5858

5959
## Automatically consolidated devices
6060

61-
When you've deployed Defender for IoT at scale, with several OT sensors, each sensor might detect different aspects of the same device. To prevent duplicated devices in your device inventory, Defender for IoT assumes that any devices found in the same zone, with a logical combination of similar characteristics, is the same device. Defender for IoT automatically consolidates these devices and lists them only once in the device inventory.
61+
When you deploy Defender for IoT at scale, with several OT sensors, each sensor might detect different aspects of the same device. To prevent duplicated devices in your device inventory, Defender for IoT assumes that any devices found in the same zone, with a logical combination of similar characteristics, is the same device. Defender for IoT automatically consolidates these devices and lists them only once in the device inventory.
6262

6363
For example, any devices with the same IP and MAC address detected in the same zone are consolidated and identified as a single device in the device inventory. If you have separate devices from recurring IP addresses that are detected by multiple sensors, you want each of these devices to be identified separately. In such cases, [onboard your OT sensors](onboard-sensors.md) to different zones so that each device is identified as a separate and unique device, even if they have the same IP address. Devices that have the same MAC addresses, but different IP addresses aren't merged, and continue to be listed as unique devices.
6464

@@ -94,60 +94,60 @@ Mark OT devices as *important* to highlight them for extra tracking. On an OT se
9494

9595
## Device inventory column data
9696

97-
The following table lists the columns available in the Defender for IoT device inventory on the Azure portal. Starred items **(*)** are also available from the OT sensor.
97+
The following table lists the columns available in the Defender for IoT device inventory on the Azure portal and the OT sensor, a description of each column and whether and in which platform it is editible. Starred items **(*)** are also available from the OT sensor.
9898

9999
> [!NOTE]
100100
> 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.
101101
102-
|Name |Description |
103-
|---------|---------|
104-
|**Authorization** * |Editable. Determines whether or not the device is marked as *authorized*. This value might need to change as the device security changes. |
105-
|**Business Function** | Editable. Describes the device's business function. |
106-
| **Class** | Editable. The device's class. <br>Default: `IoT` |
107-
|**Data source** | The source of the data, such as a micro agent, OT sensor, or Microsoft Defender for Endpoint. <br>Default: `MicroAgent`|
108-
|**Description** * | Editable. The device's description. |
109-
| **Device Id** | The device's Azure-assigned ID number. |
110-
| **Firmware model** | The device's firmware model.|
111-
| **Firmware vendor** | Editable. The vendor of the device's firmware. |
112-
| **Firmware version** * |Editable. The device's firmware version. |
113-
|**First seen** * | The date and time the device was first seen. Shown in `MM/DD/YYYY HH:MM:SS AM/PM` format. On the OT sensor, shown as **Discovered**.|
114-
|**Importance** | Editable. The device's important level: `Low`, `Medium`, or `High`. |
115-
| **IPv4 Address** | The device's IPv4 address. |
116-
|**IPv6 Address** | The device's IPv6 address.|
117-
|**Last activity** * | The date and time the device last sent an event through to Azure or to the OT sensor, depending on where you're viewing the device inventory. Shown in `MM/DD/YYYY HH:MM:SS AM/PM` format. |
118-
|**Location** | Editable. The device's physical location. |
119-
| **MAC Address** * | The device's MAC address. |
120-
|**Model** *| Editable The device's hardware model. |
121-
|**Name** * | Mandatory, and editable. The device's name as the sensor discovered it, or as entered by the user. |
122-
|**Network location** (Public preview) | The device's network location. Displays whether the device is defined as *local* or *routed*, according to the configured subnets. |
123-
|**OS architecture** | Editable. The device's operating system architecture. |
124-
|**OS distribution** | Editable. The device's operating system distribution, such as Android, Linux, and Haiku. |
125-
|**OS platform** * | Editable. The device's operating system, if detected. On the OT sensor, shown as **Operating System**. |
126-
|**OS version** | Editable. The device's operating system version, such as Windows 10 or Ubuntu 20.04.1. |
127-
|**PLC mode** * | The device's PLC operating mode, including both the *Key* state (physical / logical) and the *Run* state (logical). If both states are the same, then only one state is listed.<br><br>- Possible *Key* states include: `Run`, `Program`, `Remote`, `Stop`, `Invalid`, and `Programming Disabled`. <br><br>- Possible *Run* states are `Run`, `Program`, `Stop`, `Paused`, `Exception`, `Halted`, `Trapped`, `Idle`, or `Offline`. |
128-
|**Programming device** * | Editable. Defines whether the device is defined as a *Programming Device*, performing programming activities for PLCs, RTUs, and controllers, which are relevant to engineering stations. |
129-
|**Protocols** *| The protocols that the device uses. |
130-
| **Purdue level** | Editable. The Purdue level in which the device exists.|
131-
|**Scanner device** * | Editable. Defines whether the device performs scanning-like activities in the network. |
132-
|**Sensor**| The sensor the device is connected to. |
133-
|**Serial number** *| The device's serial number. |
134-
| **Site** | The device's site. <br><br>All Enterprise IoT sensors are automatically added to the **Enterprise network** site. |
135-
| **Slots** | The number of slots the device has. |
136-
| **Subtype** | Editable. The device's subtype, such as *Speaker* or *Smart TV*. <br>**Default**: `Managed Device` |
137-
| **Tags** | Editable. The device's tags. |
138-
|**Type** * | Editable. The device type, such as *Communication* or *Industrial*. <br>**Default**: `Miscellaneous` |
139-
|**Vendor** *| The name of the device's vendor, as defined in the MAC address. |
140-
| **VLAN** * | The device's VLAN. |
141-
|**Zone** | The device's zone. |
142-
143-
The following columns are available on OT sensors only:
144-
145-
- The device's **DHCP Address**
146-
- The device's **FQDN** address and **FQDN Last Lookup Time**
147-
- The device **Groups** that include the device, as [defined on the OT sensor's device map](how-to-work-with-the-sensor-device-map.md#create-a-custom-device-group)
148-
- The device's **Module address**
149-
- The device's **Rack** and **Slot**
150-
- The number of **Unacknowledged Alerts** alerts associated with the device
102+
|Name |Description | Editable|
103+
|---------|---------|----|
104+
|**Authorization** * |Determines whether or not the device is marked as *authorized*. This value might need to change as the device security changes. Toggle **Authorized device**. | Editable in Azure and OT Sensor|
105+
|**Business Function** | Describes the device's business function. |Editable in Azure|
106+
| **Class** | The device's class. <br>Default: `IoT` |Editable in Azure|
107+
|**Data source** | The source of the data, such as a micro agent, OT sensor, or Microsoft Defender for Endpoint. <br>Default: `MicroAgent` | Not editable|
108+
|**Description** * |The device's description. |Editable in both Azure and the OT Sensor|
109+
| **Device Id** | The device's Azure-assigned ID number. |Not editable|
110+
| **Firmware model** | The device's firmware model. |Editable in Azure|
111+
| **Firmware vendor** | The vendor of the device's firmware. |Not editable|
112+
| **Firmware version** * |The device's firmware version. |Editable in Azure |
113+
|**First seen** * | The date and time the device was first seen. Shown in `MM/DD/YYYY HH:MM:SS AM/PM` format. On the OT sensor, shown as **Discovered**.|Not editable|
114+
|**Importance** | The device's important level: `Low`, `Medium`, or `High`. |Editable in Azure|
115+
| **IPv4 Address** *| The device's IPv4 address. |Not editable|
116+
|**IPv6 Address** | The device's IPv6 address.|Not editable|
117+
|**Last activity** * | The date and time the device last sent an event through to Azure or to the OT sensor, depending on where you're viewing the device inventory. Shown in `MM/DD/YYYY HH:MM:SS AM/PM` format. |Not editable|
118+
|**Location** | The device's physical location. |Editable in Azure|
119+
| **MAC Address** * | The device's MAC address. |Not editable|
120+
|**Model** *| The device's hardware model. |Editable in Azure |
121+
|**Name** * | Mandatory. The device's name as the sensor discovered it, or as entered by the user. |Editable in Azure and OT sensor|
122+
|**Network location** (Public preview) * | The device's network location. Displays whether the device is defined as *local* or *routed*, according to the configured subnets. |Not editable|
123+
|**OS architecture** |The device's operating system architecture. |Not editable|
124+
|**OS distribution** | The device's operating system distribution, such as Android, Linux, and Haiku. |Not editable|
125+
|**OS platform** * | The device's operating system, if detected. On the OT sensor, shown as **Operating System**. |Editable in OT Sensor|
126+
|**OS version** | The device's operating system version, such as Windows 10 or Ubuntu 20.04.1. |Not editable|
127+
|**PLC mode** * | The device's PLC operating mode, including both the *Key* state (physical / logical) and the *Run* state (logical). If both states are the same, then only one state is listed.<br><br>- Possible *Key* states include: `Run`, `Program`, `Remote`, `Stop`, `Invalid`, and `Programming Disabled`. <br><br>- Possible *Run* states are `Run`, `Program`, `Stop`, `Paused`, `Exception`, `Halted`, `Trapped`, `Idle`, or `Offline`. | Editable in OT Sensor|
128+
|**Programming device** * | Defines whether the device is defined as a *Programming Device*, performing programming activities for PLCs, RTUs, and controllers, which are relevant to engineering stations. |Editable in Azure and OT sensor |
129+
|**Protocols** *| The protocols that the device uses. |Not editable|
130+
| **Purdue level** | The Purdue level in which the device exists.| Editable in OT sensor |
131+
|**Scanner device** * |Defines whether the device performs scanning-like activities in the network. |Editable in OT Sensor|
132+
|**Sensor**| The sensor the device is connected to. |Not editable|
133+
|**Serial number** *| The device's serial number. |Not editable|
134+
| **Site** | The device's site. <br><br>All Enterprise IoT sensors are automatically added to the **Enterprise network** site. |Not editable|
135+
| **Slots** * | The number of slots the device has. |Not editable|
136+
| **Subtype** | The device's subtype, such as *Speaker* or *Smart TV*. <br>**Default**: `Managed Device` |Editable in Azure|
137+
| **Tags** | The device's tags. |Editable in Azure|
138+
|**Type** * | The device type, such as *Communication* or *Industrial*. <br>**Default**: `Miscellaneous` |Editable in Azure and OT sensor |
139+
|**Vendor** *| The name of the device's vendor, as defined in the MAC address. < Also inconsistent - in inventory called vendor, in pane called hardware vendor>|Editable in Azure |
140+
| **VLAN** * | The device's VLAN. |Not editable|
141+
|**Zone** | The device's zone. |Not editable|
142+
143+
The following columns are available in the OT sensors only, and aren't editible.
144+
145+
- The device's **DHCP Address**.
146+
- The device's **FQDN** address and **FQDN Last Lookup Time**.
147+
- The device **Groups** that include the device, as [defined on the OT sensor's device map](how-to-work-with-the-sensor-device-map.md#create-a-custom-device-group).
148+
- The device's **Module address**.
149+
- The device's **Rack**.
150+
- The number of **Unacknowledged Alerts** alerts associated with the device.
151151

152152
> [!NOTE]
153153
> The additional **Agent type** and **Agent version** columns are used for by device builders. For more information, see [Microsoft Defender for IoT for device builders documentation](../device-builders/index.yml).

0 commit comments

Comments
 (0)