Skip to content

Commit b03e9b3

Browse files
Merge pull request #233916 from yoninalmsft/patch-60
Update tutorial-investigate-security-alerts.md
2 parents 979a734 + 4ca8e7e commit b03e9b3

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

articles/defender-for-iot/device-builders/tutorial-investigate-security-alerts.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -27,15 +27,15 @@ In this tutorial you'll learn how to:
2727

2828
- You must have [enabled Microsoft Defender for IoT on your Azure IoT Hub](quickstart-onboard-iot-hub.md).
2929

30-
- You must have [added a resource group to your IoT solution](quickstart-configure-your-solution.md)
30+
- You must have [added a resource group to your IoT solution](quickstart-configure-your-solution.md).
3131

3232
- You must have [created a Defender for IoT micro agent module twin](quickstart-create-micro-agent-module-twin.md).
3333

34-
- You must have [installed the Defender for IoT micro agent](quickstart-standalone-agent-binary-installation.md)
34+
- You must have [installed the Defender for IoT micro agent](quickstart-standalone-agent-binary-installation.md).
3535

36-
- You must have [configured the Microsoft Defender for IoT agent-based solution](how-to-configure-agent-based-solution.md)
36+
- You must have [configured the Microsoft Defender for IoT agent-based solution](how-to-configure-agent-based-solution.md).
3737

38-
- Learned how to [investigate security recommendations](quickstart-investigate-security-recommendations.md)
38+
- Learned how to [investigate security recommendations](quickstart-investigate-security-recommendations.md).
3939

4040
## Investigate security alerts
4141

@@ -51,7 +51,7 @@ The Defender for IoT security alert list displays all of the aggregated security
5151

5252
## Investigate security alert details
5353

54-
Opening each aggregated alert displays the detailed alert description, remediation steps, and device ID for each device that triggered an alert. The alert severity, and direct investigation is accessible using Log Analytics.
54+
Opening each aggregated alert displays the detailed alert description, remediation steps, and device ID for each device that triggered an alert. The alert severity and direct investigation is accessible using Log Analytics.
5555

5656
**To investigate security alert details**:
5757

@@ -61,15 +61,15 @@ Opening each aggregated alert displays the detailed alert description, remediati
6161

6262
1. Select any security alert from the list to open it.
6363

64-
1. Review the alert **description**, **severity**, **source of the detection**, **device details** of all devices that issued this alert in the aggregation period.
64+
1. Review the alert **description**, **severity**, **source of the detection**, and **device details** of all devices that issued this alert in the aggregation period.
6565

6666
:::image type="content" source="media/quickstart/drill-down-iot-alert-details.png" alt-text="Investigate and review the details of each device in an aggregated alert." lightbox="media/quickstart/drill-down-iot-alert-details-expanded.png":::
6767

68-
1. After reviewing the alert specifics, use the **manual remediation step** instructions to help remediate, and resolve the issue that caused the alert.
68+
1. After reviewing the alert specifics, use the **manual remediation step** instructions to help remediate and resolve the issue that caused the alert.
6969

7070
:::image type="content" source="media/quickstart/iot-alert-manual-remediation-steps.png" alt-text="Follow the manual remediation steps to help resolve or remediate your device security alerts":::
7171

72-
## Investigate alerts in Log Analytics workspace
72+
## Investigate alerts in your Log Analytics workspace
7373

7474
You can access your alerts and investigate them with the Log Analytics workspace.
7575

0 commit comments

Comments
 (0)