Skip to content

Commit 2868735

Browse files
Merge pull request #294800 from tarTech23/queryup
Update to queries and remove note
2 parents 5908290 + 6791026 commit 2868735

File tree

2 files changed

+12
-18
lines changed

2 files changed

+12
-18
lines changed

articles/defender-for-iot/organizations/alert-engine-messages.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -331,5 +331,3 @@ For more information, see:
331331
- [Work with alerts on the on-premises management console](legacy-central-management/how-to-work-with-alerts-on-premises-management-console.md)
332332
- [Alert management API reference for on-premises management consoles](api/management-alert-apis.md)
333333
- [Alert management API reference for OT monitoring sensors](api/sensor-alert-apis.md)
334-
- [Forward alert information](how-to-forward-alert-information-to-partners.md)
335-

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

Lines changed: 12 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -32,10 +32,6 @@ Before you start, make sure you have the following requirements on your workspac
3232

3333
- A Defender for IoT plan on your Azure subscription with data streaming into Defender for IoT. For more information, see [Quickstart: Get started with Defender for IoT](getting-started.md).
3434

35-
> [!IMPORTANT]
36-
> Currently, having both the Microsoft Defender for IoT and the [Microsoft Defender for Cloud](../../sentinel/data-connectors/microsoft-defender-for-cloud.md) data connectors enabled on the same Microsoft Sentinel workspace simultaneously may result in duplicate alerts in Microsoft Sentinel. We recommend that you disconnect the Microsoft Defender for Cloud data connector before connecting to Microsoft Defender for IoT.
37-
>
38-
3935
## Connect your data from Defender for IoT to Microsoft Sentinel
4036

4137
Start by enabling the [Defender for IoT data connector](../../sentinel/data-connectors/microsoft-defender-for-iot.md) to stream all your Defender for IoT events into Microsoft Sentinel.
@@ -63,54 +59,54 @@ After you've connected a subscription to Microsoft Sentinel, you'll be able to v
6359
**To see all alerts generated by Defender for IoT**:
6460

6561
```kusto
66-
SecurityAlert | where ProductName == "Azure Security Center for IoT"
62+
SecurityAlert | where ProviderName == "IoTSecurity"
6763
```
6864
6965
**To see specific sensor alerts generated by Defender for IoT**:
7066
7167
```kusto
7268
SecurityAlert
73-
| where ProductName == "Azure Security Center for IoT"
69+
| where ProviderName == "IoTSecurity"
7470
| where tostring(parse_json(ExtendedProperties).SensorId) == “<sensor_name>”
7571
```
7672
7773
**To see specific OT engine alerts generated by Defender for IoT**:
7874
7975
```kusto
8076
SecurityAlert
81-
| where ProductName == "Azure Security Center for IoT"
77+
| where ProviderName == "IoTSecurity"
8278
| where ProductComponentName == "MALWARE"
8379
8480
SecurityAlert
85-
| where ProductName == "Azure Security Center for IoT"
81+
| where ProviderName == "IoTSecurity"
8682
| where ProductComponentName == "ANOMALY"
8783
8884
SecurityAlert
89-
| where ProductName == "Azure Security Center for IoT"
85+
| where ProviderName == "IoTSecurity"
9086
| where ProductComponentName == "PROTOCOL_VIOLATION"
9187
9288
SecurityAlert
93-
| where ProductName == "Azure Security Center for IoT"
89+
| where ProviderName == "IoTSecurity"
9490
| where ProductComponentName == "POLICY_VIOLATION"
9591
9692
SecurityAlert
97-
| where ProductName == "Azure Security Center for IoT"
93+
| where ProviderName == "IoTSecurity"
9894
| where ProductComponentName == "OPERATIONAL"
9995
```
10096
10197
**To see high severity alerts generated by Defender for IoT**:
10298
10399
```kusto
104100
SecurityAlert
105-
| where ProductName == "Azure Security Center for IoT"
101+
| where ProviderName == "IoTSecurity"
106102
| where AlertSeverity == "High"
107103
```
108104
109105
**To see specific protocol alerts generated by Defender for IoT**:
110106
111107
```kusto
112108
SecurityAlert
113-
| where ProductName == "Azure Security Center for IoT"
109+
| where PProviderName == "IoTSecurity"
114110
| where tostring(parse_json(ExtendedProperties).Protocol) == "<protocol_name>"
115111
```
116112
@@ -138,16 +134,16 @@ For more information, see [View alerts on the Defender for IoT portal](how-to-ma
138134
139135
### Understand multiple records per alert
140136
141-
Defender for IoT alert data is streamed to the Microsoft Sentinel and stored in your Log Analytics workspace, in the [SecurityAlert]() table.
137+
Defender for IoT alert data is streamed to the Microsoft Sentinel and stored in your Log Analytics workspace, in the [SecurityAlert](/azure/sentinel/security-alert-schema) table.
142138
143139
Records in the **SecurityAlert** table are created each time an alert is generated or updated in Defender for IoT. Sometimes a single alert will have multiple records, such as when the alert was first created and then again when it was updated.
144140
145141
In Microsoft Sentinel, use the following query to check the records added to the **SecurityAlert** table for a single alert:
146142
147143
```kql
148144
SecurityAlert
149-
| where ProductName == "Azure Security Center for IoT"
150-
| where VendorOriginalId == "Defender for IoT Alert ID"
145+
| where ProviderName == "IoTSecurity"
146+
| where VendorOriginalId == "<Defender for IoT Alert ID>"
151147
| sort by TimeGenerated desc
152148
```
153149

0 commit comments

Comments
 (0)