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-6Lines changed: 5 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -218,7 +218,7 @@ You'd configured your OT sensor network configuring during [installation](ot-dep
218
218
219
219
### Turn off learning mode manually
220
220
<!-- Limor should most of this intro be moved to create-learned-baseline.md? that is a 'concept' page about learning mode-->
221
-
An OT network sensor starts monitoring your network automatically as soon as it's connected to your network and you've [signed in](ot-deploy/activate-deploy-sensor.md#sign-in-to-the-sensor-console-and-change-the-default-password). Network devices start appearing in your [device inventory](device-inventory.md), and [alerts](alerts.md) are triggered for any security or operational incidents that occur in your network.
221
+
An OT network sensor starts monitoring your network automatically as soon as it connects to your network and you[sign in](ot-deploy/activate-deploy-sensor.md#sign-in-to-the-sensor-console-and-change-the-default-password). Network devices start appearing in your [device inventory](device-inventory.md), and [alerts](alerts.md) are triggered for any security or operational incidents that occur in your network.
222
222
223
223
There are three stages to the monitoring process. For more information, see [overview of the multi stage monitoring process](ot-deploy/create-learned-baseline.md).
224
224
@@ -234,11 +234,11 @@ Two to six weeks after deploying your sensor the detection levels should accurat
234
234
235
235
1. Sign into your OT network sensor and select **System settings > Network monitoring > Detection engines and network modeling**.
236
236
237
-
1. In **Network modelling**, toggle off **Learning**.
237
+
1. In **Network modeling**, toggle off **Learning**.
238
238
239
239
1. Select **OK** in the confirmation message, and then select **Close** to save your changes.
240
240
241
-
Once learning mode has been turned off, the sensor starts to generate **Policy Violation** alerts and this setting is now available by selecting **Support** in the side menu. We recommend leaving the mode settings for each alert to automatically update from dynamic to operational. However, for testing or other reasons, you could manually change the mode setting. This is not recommended as it can produce a large number of alerts.<!-- keep or remove last sentence?-->
241
+
Once learning mode is turned off, the sensor starts to generate **Policy Violation** alerts and this setting is now available by selecting **Support** in the side menu. We recommend leaving the mode settings for each alert to automatically update from dynamic to operational. For testing or other reasons, you could manually change the mode setting, however, this isn't recommended as it can produce a large number of alerts.
242
242
243
243
**Manually change a Policy Violations setting**:
244
244
@@ -250,7 +250,7 @@ Once learning mode has been turned off, the sensor starts to generate **Policy V
250
250
251
251
## Update a sensor's monitoring interfaces (configure ERSPAN)
252
252
253
-
You may want to change the interfaces used by your sensor to monitor traffic. You originally configured these details as part of your [initial sensor setup](ot-deploy/activate-deploy-sensor.md#define-the-interfaces-you-want-to-monitor), but may need to modify the settings as part of system maintenance, such as configuring ERSPAN monitoring.
253
+
You might want to change the interfaces used by your sensor to monitor traffic. You originally configured these details as part of your [initial sensor setup](ot-deploy/activate-deploy-sensor.md#define-the-interfaces-you-want-to-monitor), but might need to modify the settings as part of system maintenance, such as configuring ERSPAN monitoring.
254
254
255
255
For more information, see [ERSPAN ports](best-practices/traffic-mirroring-methods.md#erspan-ports).
256
256
@@ -265,7 +265,7 @@ For more information, see [ERSPAN ports](best-practices/traffic-mirroring-method
265
265
266
266
- Select the **Enable/Disable** toggle for any interfaces you want the sensor to monitor. You must have at least one interface enabled for each sensor.
267
267
268
-
If you're not sure about which interface to use, select the :::image type="icon" source="media/install-software-ot-sensor/blink-interface.png" border="false"::: **Blink physical interface LED** button to have the selected port blink on your machine.
268
+
If you're not sure about which interface to use, select the :::image type="icon" source="media/install-software-ot-sensor/blink-interface.png" border="false"::: **Blink physical interface LED** button to have the selected port blink on your machine.
269
269
270
270
> [!TIP]
271
271
> We recommend that you optimize performance on your sensor by configuring your settings to monitor only the interfaces that are actively in use.
@@ -284,7 +284,6 @@ For more information, see [ERSPAN ports](best-practices/traffic-mirroring-method
284
284
285
285
1. Select **Save** to save your changes. Your sensor software restarts to implement your changes.
286
286
287
-
288
287
## Synchronize time zones on an OT sensor
289
288
290
289
You may want to configure your OT sensor with a specific time zone so that all users see the same times regardless of the user's location.
0 commit comments