Skip to content

Commit dc3a582

Browse files
committed
initial
1 parent 1b0b890 commit dc3a582

File tree

2 files changed

+18
-1
lines changed

2 files changed

+18
-1
lines changed

articles/defender-for-iot/organizations/alerts.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ ms.date: 08/06/2023
55
ms.topic: how-to
66
ms.custom: enterprise-iot
77
---
8-
8+
<!-- should we reassess the order of this article, does it make sesne? Could the flow be better? -->
99
# Microsoft Defender for IoT alerts
1010

1111
Microsoft Defender for IoT alerts enhance your network security and operations with real-time details about events logged in your network. Alerts are triggered when OT network sensors detect changes or suspicious activity in network traffic that needs your attention.
@@ -50,6 +50,13 @@ For more information, see:
5050

5151
Alert options also differ depending on your location and user role. For more information, see [Azure user roles and permissions](roles-azure.md) and [On-premises users and roles](roles-on-premises.md).
5252

53+
<!-- placing here for initial ease and finding - where should this really go?-->
54+
## Alert grouping
55+
56+
Multiple alerts, from the same alert category, that have the same parameters, ie. the same source and destination IP addresses, are aggregated into one alert report, instead of each alert being displayed individually.
57+
58+
The alert has a violations parameter added to show how many alerts of this type are generated. They can all be remediated simaltaneously using the Learn and Actions recommended, which will apply to all versions of this alert. The alerts can be viewed individually within their respective devices.
59+
5360
## Focused alerts in OT/IT environments
5461

5562
Organizations where sensors are deployed between OT and IT networks deal with many alerts, related to both OT and IT traffic. The amount of alerts, some of which are irrelevant, can cause alert fatigue and affect overall performance. To address these challenges, Defender for IoT's detection policy steers its different [alert engines](alert-engine-messages.md#supported-alert-types) to focus on alerts with business impact and relevance to an OT network, and reduce low-value IT related alerts. For example, the **Unauthorized internet connectivity** alert is highly relevant in an OT network, but has relatively low value in an IT network.

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

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,16 @@ Features released earlier than nine months ago are described in the [What's new
1818
1919
[!INCLUDE [defender-iot-defender-reference](../includes/defender-for-iot-defender-reference.md)]
2020

21+
## November 2024
22+
23+
|Service area |Updates |
24+
|---------|---------|
25+
| **OT networks** | - [Group multiple alerts with the same parameters](#group-multiple-alerts-with-the-same-parameters)|
26+
27+
### Group multiple alerts with the same parameters
28+
29+
To reduce alert fatigue, multiple versions of an alert from the same category and the same parameters are grouped together, the number of alerts are listed and the appropriate remediation or Learn actions are listed. For more information, see [Group multiple alerts with the same parameters](alerts.md#alert-grouping)
30+
2131
## October 2024
2232

2333
|Service area |Updates |

0 commit comments

Comments
 (0)