Skip to content

Commit 06128ab

Browse files
committed
edits
1 parent 0d756fc commit 06128ab

File tree

2 files changed

+22
-10
lines changed

2 files changed

+22
-10
lines changed

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

Lines changed: 11 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -247,7 +247,7 @@ When signing into a pre-configured sensor for the first time, you'll need to per
247247
1. Select **Next**, and your user, and a system-generated password for your OT sensor will then appear.
248248

249249
> [!NOTE]
250-
> When you sign in to a sensor for the first time, it's linked to your Azure subscription, which you'll need if you need to recover the password for the *admin* user. For more information, see [Recover privileged access to a sensor](manage-users-sensor.md#recover-privileged-access-to-a-sensor).
250+
> When you sign in to a sensor for the first time, it's linked to your Azure subscription, which you need if you need to recover the password for the *admin* user. For more information, see [Recover privileged access to a sensor](manage-users-sensor.md#recover-privileged-access-to-a-sensor).
251251
252252
## Investigate a lack of traffic
253253

@@ -257,7 +257,7 @@ An indicator appears at the top of the console when the sensor recognizes that t
257257

258258
When a new sensor is deployed or a sensor is working slowly or not showing any alerts, you can check system performance.
259259

260-
1. Sign in to the sensor and select **Overview**. Make sure that **PPS** is greater than 0, and that **Devices** are being discovered.
260+
1. Sign in to the sensor and select **Overview**. Make sure that **PPS** is greater than 0, and that **Devices** are being discovered.
261261
1. In the **Data Mining** page, generate a report.
262262
1. In the **Trends & Statistics** page, create a dashboard.
263263
1. In the **Alerts** page, check that the alert was created.
@@ -289,7 +289,7 @@ For more information, see:
289289

290290
## Connect the sensor to NTP
291291

292-
You can configure a standalone sensor and a OT sensor console, with the sensors related to it, to connect to NTP.
292+
You can configure a standalone sensor and an OT sensor console, with the sensors related to it, to connect to NTP.
293293

294294
> [!TIP]
295295
> When you're ready to start managing your OT sensor settings at scale, define NTP settings from the Azure portal. Once you apply settings from the Azure portal, settings on the sensor console are read-only. For more information, see [Configure OT sensor settings from the Azure portal (Public preview)](configure-sensor-settings-portal.md).
@@ -319,7 +319,7 @@ For more information on how to clear system data, see [Clear OT sensor data](how
319319

320320
## Export logs from the sensor console for troubleshooting
321321

322-
For further troubleshooting, you may want to export logs to send to the support team, such as database or operating system logs.
322+
For further troubleshooting, you might want to export logs to send to the support team, such as database or operating system logs.
323323

324324
**To export log data**:
325325

@@ -348,15 +348,19 @@ For further troubleshooting, you may want to export logs to send to the support
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
351+
## Configure a backup server after false positive alert
352352
<!-- what should the title be?-->
353353

354-
If a false positive alert is produced the backup server might be misconfiigured. In order to correct this:
354+
When a false positive alert is produced the backup server might be misconfigured. In confirm the correct settings:
355355

356356
1. In the sensor console, go to **System settings** > **Sensor management** > **Advanced configurations**.
357+
357358
1. Select the **Global** category. Ensure that **is_reduce_backup_malware_enabled=1** (Note: **true** is also an acceptable parameter).
358-
1. Select the **Vulnerability assessment** category. Ensure **backup_servers** contains the back up server device's IP address.
359+
360+
1. Select the **Vulnerability assessment** category. Ensure **backup_servers** contains the backup server device's IP address.
361+
359362
1. Select the **Ports** category. Ensure that **backup_known_ports** contains the list of port(s) used for the backup server.
363+
360364
1. Select **Save**.
361365

362366
## Next steps

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

Lines changed: 11 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: What's new in Microsoft Defender for IoT
33
description: This article describes new features available in Microsoft Defender for IoT, including both OT and Enterprise IoT networks, and both on-premises and in the Azure portal.
44
ms.topic: whats-new
5-
ms.date: 10/14/2024
5+
ms.date: 04/08/2025
66
ms.custom: enterprise-iot
77
---
88

@@ -22,6 +22,16 @@ Features released earlier than nine months ago are described in the [What's new
2222

2323
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).
2424

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).
34+
2535
## March 2025
2636

2737
|Service area |Updates |
@@ -32,8 +42,6 @@ The legacy on-premises management console won't be available for download after
3242

3343
The "Unauthorized Internet Connectivity Detected" alert details now includes the URL from which the suspicious connection initiated, helping SOC analysts assess and respond to incidents more effectively.
3444

35-
:::image type="content" source="media/whats-new/url-parameters.png" alt-text="Screenshot of URL information in alert details." lightbox="media/whats-new/url-parameters.png":::
36-
3745
### Improved RDP brute force detection
3846

3947
The “Excessive Number of Sessions” alert now includes support by default to a remote desktop protocol (RDP) port, enhancing visibility into potential brute-force attacks and unauthorized access attempts.

0 commit comments

Comments
 (0)