Skip to content

Commit 5d8f4ac

Browse files
authored
Merge pull request #264911 from limwainstein/suppression-rules-2410
Suppression rules 2410
2 parents 4ccc8c8 + 79f5d92 commit 5d8f4ac

File tree

8 files changed

+203
-48
lines changed

8 files changed

+203
-48
lines changed

articles/defender-for-iot/organizations/how-to-accelerate-alert-incident-response.md

Lines changed: 163 additions & 42 deletions
Large diffs are not rendered by default.

articles/defender-for-iot/organizations/how-to-manage-cloud-alerts.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: View and manage alerts on the Azure portal - Microsoft Defender for IoT
33
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
55
ms.topic: how-to
66
ms.custom: enterprise-iot
77
---
@@ -27,7 +27,7 @@ Microsoft Defender for IoT alerts enhance your network security and operations w
2727

2828
- **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)
2929

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.
3131

3232
For more information, see [Azure user roles and permissions for Defender for IoT](roles-azure.md).
3333

@@ -64,6 +64,9 @@ For more information, see [Azure user roles and permissions for Defender for IoT
6464
| **Category**| The [category](alert-engine-messages.md#supported-alert-categories) associated with the alert, such as *operational issues*, *custom alerts*, or *illegal commands*. |
6565
| **Type**| The internal name of the alert. |
6666

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+
6770
### Filter alerts displayed
6871

6972
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.
824 Bytes
Loading
641 Bytes
Loading
1.33 KB
Loading

articles/defender-for-iot/organizations/release-notes.md

Lines changed: 21 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,8 +37,8 @@ Cloud features may be dependent on a specific sensor version. Such features are
3737

3838
| Version / Patch | Release date | Scope | Supported until |
3939
| ------- | ------------ | ----------- | ------------------- |
40-
| **23.2** | | | |
41-
| 23.2.0 | 12/2023 | Major | 11/2024 |
40+
| **24.1** | | | |
41+
| 24.1.0 |02/2024 | Major |01/2025 |
4242
| **23.1** | | | |
4343
| 23.1.3 | 09/2023 | Patch | 08/2024 |
4444
| 23.1.2 | 07/2023 | Major | 06/2024 |
@@ -101,10 +101,29 @@ Version numbers are listed only in this article and in the [What's new in Micros
101101

102102
To understand whether a feature is supported in your sensor version, check the relevant version section below and its listed features.
103103

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+
104119
## Versions 23.2.x
105120

106121
### Version 23.2.0
107122

123+
**Release date**: 12/2023
124+
125+
**Supported until**: 11/2024
126+
108127
This version includes the following updates and enhancements:
109128

110129
- [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)

articles/defender-for-iot/organizations/roles-azure.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ Permissions are applied to user roles across an entire Azure subscription, or in
3636
| **[Download OT threat intelligence packages](how-to-work-with-threat-intelligence-packages.md#manually-update-locally-managed-sensors)** <br>Apply per subscription only |||||
3737
| **[Push OT threat intelligence updates](how-to-work-with-threat-intelligence-packages.md#manually-push-updates-to-cloud-connected-sensors)** <br>Apply per subscription only | - ||||
3838
| **[View Azure alerts](how-to-manage-cloud-alerts.md)** <br>Apply per subscription or site |||||
39-
| **[Modify Azure alerts](how-to-manage-cloud-alerts.md) (write access - change status, learn, download PCAP)** <br>Apply per subscription or site| - ||||
39+
| **[Modify Azure alerts](how-to-manage-cloud-alerts.md) (write access - change status, learn, download PCAP, suppression rules)** <br>Apply per subscription or site| - ||||
4040
| **[View Azure device inventory](how-to-manage-device-inventory-for-organizations.md)** <br>Apply per subscription or site |||||
4141
| **[Manage Azure device inventory](how-to-manage-device-inventory-for-organizations.md) (write access)** <br>Apply per subscription or site | - ||||
4242
| **[View Azure workbooks](workbooks.md)**<br>Apply per subscription or site |||||

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

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

2121
|Service area |Updates |
2222
|---------|---------|
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).
2435

2536
### Focused alerts in OT/IT environments
2637

@@ -58,6 +69,7 @@ You might want to update your sensor to a specific version for various reasons,
5869
:::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" :::
5970

6071
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)|
6173

6274
## December 2023
6375

0 commit comments

Comments
 (0)