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/alert-engine-messages.md
+41-7Lines changed: 41 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,19 +1,19 @@
1
1
---
2
-
title: Alert types and descriptions
3
-
description: Review Defender for IoT Alert descriptions.
4
-
ms.date: 12/13/2021
5
-
ms.topic: how-to
2
+
title: OT monitoring alert types and descriptions
3
+
description: Learn more about the alerts that are triggered for traffic on OT networks.
4
+
ms.date: 11/01/2022
5
+
ms.topic: reference
6
6
---
7
7
8
-
# Alert types and descriptions
8
+
# OT monitoring alert types and descriptions
9
9
10
10
This article provides information on the alert types, descriptions, and severity that may be generated from the Defender for IoT engines. This information can be used to help map alerts into playbooks, define Forwarding rules, Exclusion rules, and custom alerts and define the appropriate rules within a SIEM. Alerts appear in the Alerts window, which allows you to manage the alert event.
11
11
12
12
### Alert news
13
13
14
-
New alerts may be added and existing alerts may be updated or disabled. Certain disabled alerts can be re-enabled from the Support page of the sensor console. Alerts that can be re-enabled are marked with an asterisk (*) in the tables below.
14
+
New alerts may be added and existing alerts may be updated or disabled. Certain disabled alerts can be re-enabled from the **Support** page of the sensor console. Alerts that can be re-enabled are marked with an asterisk (*) in the tables below.
15
15
16
-
You may have configured newly disabled alerts in your Forwarding rules. If so, you may need to update related Defender for IoT Exclusion rules, or update SIEM rules and playbooks where relevant.
16
+
You may have configured newly disabled alerts in your Forwarding rules. If so, you may need to update related Defender for IoT Exclusion rules, or update SIEM rules and playbooks where relevant.
17
17
18
18
See [What's new in Microsoft Defender for IoT?](release-notes.md#whats-new-in-microsoft-defender-for-iot) for detailed information about changes made to alerts.
19
19
@@ -27,6 +27,40 @@ See [What's new in Microsoft Defender for IoT?](release-notes.md#whats-new-in-m
27
27
| Malware alerts | Triggered when the Malware engine detects malicious network activity. For example, the engine detects a known attack such as Conficker. |
28
28
| Anomaly alerts | Triggered when the Anomaly engine detects a deviation. For example, a device is performing network scans but isn't defined as a scanning device. |
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/how-to-manage-cloud-alerts.md
+1-34Lines changed: 1 addition & 34 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,7 +60,7 @@ The following alert details are displayed by default in the grid:
60
60
|**Source device**| The IP address, MAC, or device name. |
61
61
|**Tactics**| The MITRE ATT&CK stage. |
62
62
63
-
**To view additional information:**
63
+
### View more alert details
64
64
65
65
1. Select **Edit columns** from the Alerts page.
66
66
1. In the Edit Columns dialog box, select **Add Column** and choose an item to add. The following items are available:
@@ -87,39 +87,6 @@ For example, filter alerts by **Category**:
87
87
88
88
:::image type="content" source="media/how-to-view-manage-cloud-alerts/category-filter.png" alt-text="Screenshot of the Category filter option in Alerts page in the Azure portal.":::
89
89
90
-
Supported categories include:
91
-
92
-
:::row:::
93
-
:::column span="":::
94
-
- Abnormal Communication Behavior
95
-
- Abnormal HTTP Communication Behavior
96
-
- Authentication
97
-
- Backup
98
-
- Bandwidth Anomalies
99
-
- Buffer overflow
100
-
- Command Failures
101
-
- Configuration changes
102
-
- Custom Alerts
103
-
- Discovery
104
-
- Firmware change
105
-
- Illegal commands
106
-
:::column-end:::
107
-
:::column span="":::
108
-
- Internet Access
109
-
- Operation Failures
110
-
- Operational issues
111
-
- Programming
112
-
- Remote access
113
-
- Restart/Stop Commands
114
-
- Scan
115
-
- Sensor traffic
116
-
- Suspicion of malicious activity
117
-
- Suspicion of Malware
118
-
- Unauthorized Communication Behavior
119
-
- Unresponsive
120
-
:::column-end:::
121
-
:::row-end:::
122
-
123
90
### Group alerts displayed
124
91
125
92
Use the **Group by** menu at the top right to collapse the grid into subsections according to specific parameters.
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/release-notes.md
+17-1Lines changed: 17 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,6 +60,22 @@ For more information, see the [Microsoft Security Development Lifecycle practice
60
60
| 10.5.3 | 10/2021 | 07/2022 |
61
61
| 10.5.2 | 10/2021 | 07/2022 |
62
62
63
+
## October 2022
64
+
65
+
|Service area |Updates |
66
+
|---------|---------|
67
+
|**OT networks**|[Enhanced OT monitoring alert reference](#enhanced-ot-monitoring-alert-reference)|
68
+
69
+
### Enhanced OT monitoring alert reference
70
+
71
+
Our alert reference article now includes the following details for each alert:
72
+
73
+
-**Alert category**, helpful when you want to investigate alerts that are aggregated by a specific activity or configure SIEM rules to generate incidents based on specific activities
74
+
75
+
-**Alert threshold**, for relevant alerts. Thresholds indicate the specific point at which an alert is triggered. Modify alert thresholds as needed from the sensor's **Support** page.
76
+
77
+
For more information, see [OT monitoring alert types and descriptions](alert-engine-messages.md), specifically [Supported alert categories](alert-engine-messages.md#supported-alert-categories).
78
+
63
79
## September 2022
64
80
65
81
|Service area |Updates |
@@ -855,4 +871,4 @@ Unicode characters are now supported when working with sensor certificate passph
855
871
856
872
## Next steps
857
873
858
-
[Getting started with Defender for IoT](getting-started.md)
874
+
[Getting started with Defender for IoT](getting-started.md)
0 commit comments