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
+9-7Lines changed: 9 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Maintain Defender for IoT OT network sensors from the GUI - Microsoft Defender for IoT
3
3
description: Learn how to perform maintenance activities on individual OT network sensors using the OT sensor console.
4
-
ms.date: 12/07/2023
4
+
ms.date: 12/12/2023
5
5
ms.topic: how-to
6
6
---
7
7
@@ -427,15 +427,17 @@ After clearing data on a cloud-connected sensor:
427
427
428
428
A confirmation message appears that the action was successful. All learned data, allowlists, policies, and configuration settings are cleared from the sensor.
429
429
430
-
## Manage custom plugins (legacy)
430
+
## Manage sensor plugins and monitor plugin performance
431
431
432
-
If you've added custom plugins for proprietary protocols using the legacy Horizon support, you can continue to manage them from the sensor console.
432
+
View data for each protocol monitored by your sensor using the **Protocols DPI (Horizon Plugins)** page in the sensor console.
433
433
434
-
**To access your custom plugins**: Sign into your OT sensor console and select **System settings > Network monitoring > Protocols DPI (Horizon Plugins)**.
434
+
1. Sign into your OT sensor console and select **System settings > Network monitoring > Protocols DPI (Horizon Plugins)**.
435
435
436
-
**To enable or disable plugins**: Select the **Enable/Disable** toggle for each plugin you want to enable or disable.
436
+
1. Do one of the following:
437
+
438
+
- To limit the protocols monitored by your sensor, select the **Enable/Disable** toggle for each plugin as needed.
437
439
438
-
**To monitor plugin performance**: Use the data shown on the **Protocols DPI (Horizon Plugins)** page in the sensor console to understand details about your plugin usage. To help locate a specific plugin, use the **Search** box to enter part of all of a plugin name.
440
+
-To monitor plugin performance, view the data shown on the **Protocols DPI (Horizon Plugins)** page for each plugin. To help locate a specific plugin, use the **Search** box to enter part of all of a plugin name.
439
441
440
442
The **Protocols DPI (Horizon Plugins)** lists the following data per plugin:
441
443
@@ -450,7 +452,7 @@ The **Protocols DPI (Horizon Plugins)** lists the following data per plugin:
450
452
|**Warnings**| The number of warnings detected, such as when packets match the structure and specifications, but unexpected behavior is detected, based on the plugin warning configuration. |
451
453
|**Errors**| The number of errors detected in the last five seconds for packets that failed basic protocol validations for the packets that match protocol definitions. |
452
454
453
-
Horizon log data is available for export in the **Dissection statistics** and **Dissection Logs**, log files. For more information, see [Export troubleshooting logs](how-to-troubleshoot-sensor.md).
455
+
Log data is available for export in the **Dissection statistics** and **Dissection Logs**, log files. For more information, see [Export troubleshooting logs](how-to-troubleshoot-sensor.md).
0 commit comments