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/concept-sentinel-integration.md
+27-20Lines changed: 27 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,41 +72,48 @@ For example, use SOAR playbooks to:
72
72
73
73
- Send an email to relevant stakeholders when suspicious activity is detected, for example unplanned PLC reprogramming. The mail may be sent to OT personnel, such as a control engineer responsible on the related production line.
74
74
75
-
76
-
77
75
## Comparing Defender for IoT events, alerts, and incidents
78
76
79
77
This section clarifies the differences between Defender for IoT events, alerts, and incidents in Microsoft Sentinel. Use the listed queries to view a full list of the current events, alerts, and incidents for your OT networks.
80
78
81
79
You'll typically see more Defender for IoT *events* in Microsoft Sentinel than *alerts*, and more Defender for IoT *alerts* than *incidents*.
82
80
81
+
### Defender for IoT events in Microsoft Sentinel
82
+
83
+
Each alert log that streams to Microsoft Sentinel from Defender for IoT is an *event*. If the alert log reflects a new or updated alert in Defender for IoT, a new record is added to the **SecurityAlert** table.
84
+
85
+
To view all Defender for IoT events in Microsoft Sentinel, run the following query on the **SecurityAlert** table:
83
86
84
-
-**Events**: Each alert log that streams to Microsoft Sentinel from Defender for IoT is an *event*. If the alert log reflects a new or updated alert in Defender for IoT, a new record is added to the **SecurityAlert** table.
87
+
```kql
88
+
SecurityAlert
89
+
| where ProviderName == 'IoTSecurity' or ProviderName == 'CustomAlertRule'
90
+
Instead
91
+
```
85
92
86
-
To view all Defender for IoT events in Microsoft Sentinel, run the following query on the **SecurityAlert** table:
93
+
### Defender for IoT alerts in Microsoft Sentinel
87
94
88
-
```kql
89
-
SecurityAlert
90
-
| where ProviderName == 'IoTSecurity' or ProviderName == 'CustomAlertRule'
91
-
Instead
92
-
```
95
+
Microsoft Sentinel creates alerts based on your current analytics rules and the alert logs listed in the **SecurityAlert** table. If you don't have any active analytics rules for Defender for IoT, Microsoft Sentinel considers each alert log as an *event*.
93
96
94
-
- **Alerts**: Microsoft Sentinel creates alerts based on your current analytics rules and the alert logs listed in the **SecurityAlert** table. If you don't have any active analytics rules for Defender for IoT, Microsoft Sentinel considers each alert log as an *event*.
97
+
To view alerts in Microsoft Sentinel, run the following query on the**SecurityAlert** table:
98
+
```kql
99
+
SecurityAlert
100
+
| where ProviderName == 'ASI Scheduled Alerts' or ProviderName =='CustomAlertRule'
101
+
```
95
102
96
-
To view alerts in Microsoft Sentinel, run the following query on the **SecurityAlert** table:
103
+
After you've installed the Microsoft Defender for IoT solution and deployed the [AD4IoT-AutoAlertStatusSync](iot-advanced-threat-monitoring.md#update-alert-statuses-in-defender-for-iot) playbook, alert status changes are synchronized from Microsoft Sentinel to Defender for IoT. Alert status changes are *not* synchronized from Defender for IoT to Microsoft Sentinel.
97
104
98
-
```kql
99
-
SecurityAlert
100
-
| where ProviderName == 'ASI Scheduled Alerts' or ProviderName == 'CustomAlertRule'
101
-
```
105
+
> [!IMPORTANT]
106
+
> We recommend that you manage your alert statuses together with the related incidents in Microsoft Sentinel. For more information, see [Work with incident tasks in Microsoft Sentinel](/azure/sentinel/work-with-tasks).
107
+
>
102
108
103
-
- **Incidents**. Microsoft Sentinel creates incidents based on your analytics rules. You might have several alerts grouped in the same incident, or you may have analytics rules configured to *not* create incidents for specific alert types.
109
+
### Defender for IoT incidents in Microsoft Sentinel
104
110
105
-
To view incidents in Microsoft Sentinel, run the following query:
111
+
Microsoft Sentinel creates incidents based on your analytics rules. You might have several alerts grouped in the same incident, or you may have analytics rules configured to *not* create incidents for specific alert types.
106
112
107
-
```kql
108
-
SecurityIncident
109
-
```
113
+
To view incidents in Microsoft Sentinel, run the following query:
0 commit comments