You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/how-to-manage-individual-sensors.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,8 @@ This article describes how to manage individual sensors, such as managing activa
11
11
12
12
You can also perform some management tasks for multiple sensors simultaneously from the Azure portal or an on-premises management console. For more information, see [Next steps](#next-steps).
13
13
14
+
[!INCLUDE [caution do not use manual configurations](includes/caution-manual-configurations.md)]
15
+
14
16
## View overall sensor status
15
17
16
18
When you sign into your sensor, the first page shown is the **Overview** page.
@@ -454,7 +456,7 @@ This feature is supported for the following sensor versions:
454
456
455
457
## Retrieve forensics data stored on the sensor
456
458
457
-
Use Defender for IoT data mining reports on an OT network sensor to retrieve forensic data from that sensor’s storage. The following types of forensic data is stored locally on OT sensors, for devices detected by that sensor:
459
+
Use Defender for IoT data mining reports on an OT network sensor to retrieve forensic data from that sensor’s storage. The following types of forensic data are stored locally on OT sensors, for devices detected by that sensor:
458
460
459
461
- Device data
460
462
- Alert data
@@ -481,7 +483,7 @@ Clearing data deletes all detected or learned data on the sensor. After clearing
481
483
482
484
1. In the confirmation dialog box, select **Yes** to confirm that you do want to clear all data from the sensor and reset it. For example:
483
485
484
-
:::image type="content" source="media/how-to-manage-individual-sensors/clear-system-data.png" alt-text="Screenshot of clearing system data on the support page in the sensor console.":::
486
+
:::image type="content" source="media/how-to-manage-individual-sensors/clear-system-data.png" alt-text="Screenshot of clearing system data on the support page in the sensor console." lightbox="media/how-to-manage-individual-sensors/clear-system-data.png":::
485
487
486
488
A confirmation message appears that the action was successful. All learned data, allowlists, policies, and configuration settings are cleared from the sensor.
487
489
@@ -496,4 +498,4 @@ For more information, see:
496
498
-[Manage sensors with Defender for IoT in the Azure portal](how-to-manage-sensors-on-the-cloud.md)
497
499
-[Threat intelligence research and packages](how-to-work-with-threat-intelligence-packages.md)
498
500
-[Manage sensors from the management console](how-to-manage-sensors-from-the-on-premises-management-console.md)
499
-
-[Troubleshoot the sensor and on-premises management console](how-to-troubleshoot-the-sensor-and-on-premises-management-console.md)
501
+
-[Troubleshoot the sensor and on-premises management console](how-to-troubleshoot-the-sensor-and-on-premises-management-console.md)
> Only documented configuration parameters on the OT network sensor and on-premises management console are supported for customer configuration. Do not change any non-documented configuration parameters, as changes may cause unexpected behavior and system failures.
This command will cause the light on the port to flash for the specified time period. For example, entering `sudo ethtool -p eno1 120`, will have port eno1 flash for 2 minutes, allowing you to find the port on the back of your appliance.
146
146
147
+
[!INCLUDE [caution do not use manual configurations](../includes/caution-manual-configurations.md)]
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/ot-deploy/install-software-ot-sensor.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -143,6 +143,8 @@ This procedure describes how to install OT monitoring software on a sensor.
143
143
144
144
Make sure that your sensor is connected to your network, and then you can sign in to your sensor via a network-connected browser. For more information, see [Activate and set up your sensor](../how-to-activate-and-set-up-your-sensor.md#activate-and-set-up-your-sensor).
145
145
146
+
[!INCLUDE [caution do not use manual configurations](../includes/caution-manual-configurations.md)]
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/references-work-with-defender-for-iot-cli-commands.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,8 @@ To access the Defender for IoT CLI, you'll need access to the sensor or on-premi
14
14
- For OT sensors or the on-premises management console, you'll need to sign in as a [privileged user](#privileged-user-access-for-ot-monitoring).
15
15
- For Enterprise IoT sensors, you can sign in as any user.
16
16
17
+
[!INCLUDE [caution do not use manual configurations](includes/caution-manual-configurations.md)]
18
+
17
19
## Privileged user access for OT monitoring
18
20
19
21
Privileged users for OT monitoring are pre-defined together with the [OT monitoring software installation](../how-to-install-software.md), as part of the hardened operating system.
0 commit comments