Skip to content

Commit cbe620c

Browse files
committed
removing comments
1 parent 101146e commit cbe620c

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

articles/defender-for-iot/organizations/respond-ot-alert.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ Then, check the alert details page for the following details to aid in your inve
4040

4141
- **Source and destination device details**. Source and destination devices are listed in **Alert details** tab, and also in the **Entities** area below, as Microsoft Sentinel *entities*, with their own [entity pages](iot-advanced-threat-monitoring.md#investigate-further-with-iot-device-entities). In the **Entities** area, you'll use the links in the **Name** column to open the relevant device details pages for [further investigation](#investigate-related-alerts-on-the-azure-portal).
4242

43-
- **Site and zone**. These values help you understand the geographic and network location of the alert and if there are areas of the network that are now more vulnerable to attack. <!--need new screenshot showing these details-->
43+
- **Site and zone**. These values help you understand the geographic and network location of the alert and if there are areas of the network that are now more vulnerable to attack.
4444

4545
- **MITRE ATT&CK** tactics and techniques. Scroll down in the left pane to view all MITRE ATT&CK details. In addition to descriptions of the tactics and techniques, select the links to the MITRE ATT&CK site to learn more about each one.
4646

@@ -79,13 +79,12 @@ On the sensor's alert details page:
7979

8080
- Select the **Map view** tab to view the alert inside the sensor's device map. For more information, see [Investigate sensor detections in the Device map](how-to-work-with-the-sensor-device-map.md).
8181

82-
- Select the **Event timeline** tab to view the alert's full event timeline, including other related activity also detected by the sensor. For more information, see [Track sensor activity](how-to-track-sensor-activity.md). <!--lets give the users more here- we don't have enough on the event timeline-->
82+
- Select the **Event timeline** tab to view the alert's full event timeline, including other related activity also detected by the sensor. For more information, see [Track sensor activity](how-to-track-sensor-activity.md).
8383

84-
- Select **Export PDF** to download a PDF summary of the alert details. <!--there isn't much included here. worth including?-->
84+
- Select **Export PDF** to download a PDF summary of the alert details.
8585

8686
## Take remediation action
8787

88-
<!--ask meir where the best place to do this in?-->
8988
The timing for when you take remediation actions may depend on the severity of the alert. For example, for high severity alerts, you might want to take action even before investigating, such as if you need to immediately quarantine an area of your network.
9089

9190
For lower severity alerts, or for operational alerts, you might want to investigate before taking action.

0 commit comments

Comments
 (0)