Skip to content

Commit 357ef8a

Browse files
committed
moved to maintain
1 parent 06128ab commit 357ef8a

File tree

3 files changed

+17
-28
lines changed

3 files changed

+17
-28
lines changed

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

Lines changed: 16 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -416,7 +416,7 @@ After clearing data on a cloud-connected sensor:
416416
417417
**To clear system data**:
418418

419-
1. Sign in to the OT sensor as the *admin* user. For more information, see [Default privileged on-premises users](roles-on-premises.md#default-privileged-on-premises-users).
419+
1. Sign into the OT sensor as the *admin* user. For more information, see [Default privileged on-premises users](roles-on-premises.md#default-privileged-on-premises-users).
420420

421421
1. Select **Support** > **Clear data**.
422422

@@ -430,7 +430,7 @@ A confirmation message appears that the action was successful. All learned data,
430430

431431
View data for each protocol monitored by your sensor using the **Protocols DPI (Horizon Plugins)** page in the sensor console.
432432

433-
1. Sign into your OT sensor console and select **System settings > Network monitoring > Protocols DPI (Horizon Plugins)**.
433+
1. Sign in to your OT sensor console and select **System settings > Network monitoring > Protocols DPI (Horizon Plugins)**.
434434

435435
1. Do one of the following:
436436

@@ -453,6 +453,20 @@ The **Protocols DPI (Horizon Plugins)** lists the following data per plugin:
453453

454454
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).
455455

456+
## Configure a backup server
457+
458+
Ensure that your backup server is correctly configured, otherwise a false-positive alert might be triggered.
459+
460+
1. Sign into your OT sensor console and select **System settings** > **Sensor management** > **Advanced configurations**.
461+
462+
1. Select the **Global** category. Ensure the parameter **is_reduce_backup_malware_enabled=1** (Note: **true** is also an acceptable parameter) is set correctly.
463+
464+
1. Select the **Vulnerability assessment** category. Ensure **backup_servers** lists the backup server device's IP address.
465+
466+
1. Select the **Ports** category. Ensure that **backup_known_ports** lists the port(s) that the backup server uses.
467+
468+
1. Select **Save**.
469+
456470
## Next steps
457471

458472
For more information, see:

articles/defender-for-iot/organizations/how-to-troubleshoot-sensor.md

Lines changed: 0 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -348,21 +348,6 @@ For further troubleshooting, you might want to export logs to send to the suppor
348348
> [!NOTE]
349349
> Support ticket diagnostics can be downloaded from the sensor console and then uploaded directly to the support team in the Azure portal. For more information on downloading diagnostic logs, see [Download a diagnostics log for support](how-to-troubleshoot-sensor.md#download-a-diagnostics-log-for-support).
350350
351-
## Configure a backup server after false positive alert
352-
<!-- what should the title be?-->
353-
354-
When a false positive alert is produced the backup server might be misconfigured. In confirm the correct settings:
355-
356-
1. In the sensor console, go to **System settings** > **Sensor management** > **Advanced configurations**.
357-
358-
1. Select the **Global** category. Ensure that **is_reduce_backup_malware_enabled=1** (Note: **true** is also an acceptable parameter).
359-
360-
1. Select the **Vulnerability assessment** category. Ensure **backup_servers** contains the backup server device's IP address.
361-
362-
1. Select the **Ports** category. Ensure that **backup_known_ports** contains the list of port(s) used for the backup server.
363-
364-
1. Select **Save**.
365-
366351
## Next steps
367352

368353
- [View alerts](how-to-view-alerts.md)

articles/defender-for-iot/organizations/whats-new.md

Lines changed: 1 addition & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -20,17 +20,7 @@ Features released earlier than nine months ago are described in the [What's new
2020

2121
## On-premises management console retirement
2222

23-
The legacy on-premises management console won't be available for download after **January 1st, 2025**. We recommend transitioning to the new architecture using the full spectrum of on-premises and cloud APIs before this date. For more information, see [on-premises management console retirement](ot-deploy/on-premises-management-console-retirement.md).
24-
25-
## April 2025
26-
27-
|Service area |Updates |
28-
|---------|---------|
29-
| **OT networks** | - [Configure a backup server after false positive alert](#configure-a-backup-server-after-false-positive-alert)<br> |
30-
31-
### Configure a backup server after false positive alert
32-
33-
When a false positive alert is produced, the backup server might need to be reconfigured. For more information, see [configure a backup server after false positive alert](how-to-troubleshoot-sensor.md#configure-a-backup-server-after-false-positive-alert).
23+
The legacy on-premises management console isn't available for download after **January 1st, 2025**. We recommend transitioning to the new architecture using the full spectrum of on-premises and cloud APIs before this date. For more information, see [on-premises management console retirement](ot-deploy/on-premises-management-console-retirement.md).
3424

3525
## March 2025
3626

0 commit comments

Comments
 (0)