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-cloud-alerts.md
+5-2Lines changed: 5 additions & 2 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: View and manage alerts on the Azure portal - Microsoft Defender for IoT
3
3
description: Learn about viewing and managing alerts triggered by cloud-connected Microsoft Defender for IoT network sensors on the Azure portal.
4
-
ms.date: 12/12/2022
4
+
ms.date: 12/19/2023
5
5
ms.topic: how-to
6
6
ms.custom: enterprise-iot
7
7
---
@@ -27,7 +27,7 @@ Microsoft Defender for IoT alerts enhance your network security and operations w
27
27
28
28
-**To view alerts on the Azure portal**, you must have access as a [Security Reader](../../role-based-access-control/built-in-roles.md#security-reader), [Security Admin](../../role-based-access-control/built-in-roles.md#security-admin), [Contributor](../../role-based-access-control/built-in-roles.md#contributor), or [Owner](../../role-based-access-control/built-in-roles.md#owner)
29
29
30
-
-**To manage alerts on the Azure portal**, you must have access as a [Security Admin](../../role-based-access-control/built-in-roles.md#security-admin), [Contributor](../../role-based-access-control/built-in-roles.md#contributor), or [Owner](../../role-based-access-control/built-in-roles.md#owner). Alert management activities include modifying their statuses or severities, *Learning* an alert, or accessing PCAP data.
30
+
-**To manage alerts on the Azure portal**, you must have access as a [Security Admin](../../role-based-access-control/built-in-roles.md#security-admin), [Contributor](../../role-based-access-control/built-in-roles.md#contributor), or [Owner](../../role-based-access-control/built-in-roles.md#owner). Alert management activities include modifying their statuses or severities, *Learning* an alert, accessing PCAP data, or using alert suppression rules.
31
31
32
32
For more information, see [Azure user roles and permissions for Defender for IoT](roles-azure.md).
33
33
@@ -64,6 +64,9 @@ For more information, see [Azure user roles and permissions for Defender for IoT
64
64
|**Category**| The [category](alert-engine-messages.md#supported-alert-categories) associated with the alert, such as *operational issues*, *custom alerts*, or *illegal commands*. |
65
65
|**Type**| The internal name of the alert. |
66
66
67
+
> [!TIP]
68
+
> If you're seeing more alerts than expected, you might want to create suppression rules to prevent alerts from being triggered for legitimate network activity. For more information, see [Suppress irrelevant alerts](how-to-accelerate-alert-incident-response.md#suppress-irrelevant-alerts).
69
+
67
70
### Filter alerts displayed
68
71
69
72
Use the **Search** box, **Time range**, and **Add filter** options to filter the alerts displayed by specific parameters or to help locate a specific alert.
@@ -101,10 +101,29 @@ Version numbers are listed only in this article and in the [What's new in Micros
101
101
102
102
To understand whether a feature is supported in your sensor version, check the relevant version section below and its listed features.
103
103
104
+
## Versions 24.1.x
105
+
106
+
### Version 24.1.0
107
+
108
+
**Release date**: 02/2024
109
+
110
+
**Supported until**: 03/2025
111
+
112
+
This version includes the following updates and enhancements:
113
+
114
+
-[Alert suppression rules from the Azure portal](how-to-accelerate-alert-incident-response.md#suppress-irrelevant-alerts)
115
+
-[Focused alerts in OT/IT environments](alerts.md#focused-alerts-in-otit-environments)
116
+
-[Alert ID (Id field) is now aligned on the Azure portal and sensor console](how-to-manage-cloud-alerts.md#view-alerts-on-the-azure-portal)
117
+
-[New setting to focus local networks in the device inventory](configure-sensor-settings-portal.md#configure-subnets-in-the-azure-portal)
118
+
104
119
## Versions 23.2.x
105
120
106
121
### Version 23.2.0
107
122
123
+
**Release date**: 12/2023
124
+
125
+
**Supported until**: 11/2024
126
+
108
127
This version includes the following updates and enhancements:
109
128
110
129
-[Sensor software runs on a Debian 11 operating system](ot-deploy/install-software-ot-sensor.md) and [updates to this version may be heavier and longer than usual](whats-new.md#ot-network-sensors-now-run-on-debian-11)
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/whats-new.md
+13-1Lines changed: 13 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,18 @@ Features released earlier than nine months ago are described in the [What's new
20
20
21
21
|Service area |Updates |
22
22
|---------|---------|
23
-
|**OT networks**| - [Focused alerts in OT/IT environments](#focused-alerts-in-otit-environments)<br>- [Alert ID now aligned on the Azure portal and sensor console](#alert-id-now-aligned-on-the-azure-portal-and-sensor-console)<br>- [New setting to focus local networks in the device inventory](#new-setting-to-focus-local-networks-in-the-device-inventory)|
23
+
|**OT networks**| - [Alert suppression rules from the Azure portal (Public preview)](#alert-suppression-rules-from-the-azure-portal-public-preview)<br>- [Focused alerts in OT/IT environments](#focused-alerts-in-otit-environments)<br>- [Alert ID now aligned on the Azure portal and sensor console](#alert-id-now-aligned-on-the-azure-portal-and-sensor-console)<br>- [New setting to focus local networks in the device inventory](#new-setting-to-focus-local-networks-in-the-device-inventory)|
24
+
25
+
### Alert suppression rules from the Azure portal (Public preview)
26
+
27
+
Now you can configure alert suppression rules from the Azure portal to instruct your OT sensors to specified traffic on your network that would otherwise trigger an alert.
28
+
29
+
- Configure which alerts to suppress by specifying an alert title, IP/MAC address, hostname, subnet, sensor, or site.
30
+
- Set each suppression rule to be active always, or only during a predefined period, such as for a specific maintenance window.
31
+
32
+
> [!TIP]
33
+
> If you're currently using exclusion rules on the on-premises management console, we recommend that you migrate them to suppression rules on the Azure portal.
34
+
For more information, see [Suppress irrelevant alerts](how-to-accelerate-alert-incident-response.md#suppress-irrelevant-alerts).
24
35
25
36
### Focused alerts in OT/IT environments
26
37
@@ -58,6 +69,7 @@ You might want to update your sensor to a specific version for various reasons,
58
69
:::image type="content" source="media/whats-new/send-package-multiple-versions-400.png" alt-text="Screenshot of sensor update pane with option to choose sensor update version." border="false" lightbox="media/whats-new/send-package-multiple-versions.png" :::
59
70
60
71
For more information, see [Update Defender for IoT OT monitoring software](update-ot-software.md#send-the-software-update-to-your-ot-sensor).
72
+
|**OT networks**|**Version 24.1.0**: <br>- [Alert suppression rules from the Azure portal (Public preview)](#alert-suppression-rules-from-the-azure-portal-public-preview)|
0 commit comments