Skip to content

Commit fd5fc52

Browse files
authored
Merge pull request #223757 from yoninalmsft/manual-config-caution
caution manual configurations
2 parents 2bea623 + 2ebede3 commit fd5fc52

File tree

6 files changed

+24
-3
lines changed

6 files changed

+24
-3
lines changed

articles/defender-for-iot/organizations/cli-ot-sensor.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,8 @@ ms.topic: reference
99

1010
This article lists the CLI commands available from Defender for IoT OT network sensors.
1111

12+
[!INCLUDE [caution do not use manual configurations](includes/caution-manual-configurations.md)]
13+
1214
## Prerequisites
1315

1416
Before you can run any of the following CLI commands, you'll need access to the CLI on your OT network sensor as a privileged user.

articles/defender-for-iot/organizations/how-to-manage-individual-sensors.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,8 @@ This article describes how to manage individual sensors, such as managing activa
1111

1212
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).
1313

14+
[!INCLUDE [caution do not use manual configurations](includes/caution-manual-configurations.md)]
15+
1416
## View overall sensor status
1517

1618
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:
454456

455457
## Retrieve forensics data stored on the sensor
456458

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:
458460

459461
- Device data
460462
- Alert data
@@ -481,7 +483,7 @@ Clearing data deletes all detected or learned data on the sensor. After clearing
481483

482484
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:
483485

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":::
485487

486488
A confirmation message appears that the action was successful. All learned data, allowlists, policies, and configuration settings are cleared from the sensor.
487489

@@ -496,4 +498,4 @@ For more information, see:
496498
- [Manage sensors with Defender for IoT in the Azure portal](how-to-manage-sensors-on-the-cloud.md)
497499
- [Threat intelligence research and packages](how-to-work-with-threat-intelligence-packages.md)
498500
- [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)
Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
---
2+
title: include
3+
author: batamig
4+
ms.date: 01/12/2023
5+
ms.topic: include
6+
---
7+
8+
<!-- docutune:disable -->
9+
10+
> [!CAUTION]
11+
> 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.

articles/defender-for-iot/organizations/ot-deploy/install-software-on-premises-management-console.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -144,6 +144,8 @@ sudo ethtool -p <port value> <time-in-seconds>
144144
145145
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.
146146
147+
[!INCLUDE [caution do not use manual configurations](../includes/caution-manual-configurations.md)]
148+
147149
## Next steps
148150
149151
> [!div class="nextstepaction"]

articles/defender-for-iot/organizations/ot-deploy/install-software-ot-sensor.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -143,6 +143,8 @@ This procedure describes how to install OT monitoring software on a sensor.
143143

144144
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).
145145

146+
[!INCLUDE [caution do not use manual configurations](../includes/caution-manual-configurations.md)]
147+
146148
## Next steps
147149

148150
> [!div class="nextstepaction"]

articles/defender-for-iot/organizations/references-work-with-defender-for-iot-cli-commands.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,8 @@ To access the Defender for IoT CLI, you'll need access to the sensor or on-premi
1414
- 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).
1515
- For Enterprise IoT sensors, you can sign in as any user.
1616

17+
[!INCLUDE [caution do not use manual configurations](includes/caution-manual-configurations.md)]
18+
1719
## Privileged user access for OT monitoring
1820

1921
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

Comments
 (0)