Skip to content

Commit ce4f22f

Browse files
committed
review edits
1 parent 91aa85b commit ce4f22f

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

articles/defender-for-iot/organizations/how-to-track-sensor-activity.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,17 @@
11
---
22
title: Track network and sensor activity with the event timeline in Microsoft Defender for IoT
33
description: Track network and sensor activity in the event timeline.
4-
ms.date: 01/23/2023
4+
ms.date: 01/31/2023
55
ms.topic: how-to
66
---
77

88
# Track network and sensor activity with the event timeline
99

1010
Activity detected by your Microsoft Defender for IoT sensors is recorded in the event timeline. Activity includes alerts and alert management actions, network events, and user operations such as user sign-in or user deletion.
1111

12-
The event timeline provides a chronological view of all activity that took place in the network. Use the event timeline during investigations, to understand and analyze the chain of events that preceded and followed an attack or incident.
12+
The event timeline provides a chronological view and context of all network activity, to help determine the cause and effect of incidents. The timeline view makes it easy to extract information from network events, and more efficiently analyze alerts and events observed on the network. With the ability to store vast amounts of data, the event timeline view can be a valuable resource for security teams to perform investigations and gain a deeper understanding of network activity.
13+
14+
Use the event timeline during investigations, to understand and analyze the chain of events that preceded and followed an attack or incident. The centralized view of multiple security-related events on the same timeline helps to identify patterns and correlations, and enable security teams to quickly assess the impact of incidents and respond accordingly.
1315

1416
Enhance your security analysis and incident investigations with the event timeline, with the following options:
1517

@@ -102,12 +104,11 @@ For example:
102104

103105
:::image type="content" source="media/track-sensor-activity/create-new-event.png" alt-text="Screenshot of creating a new event in the timeline.":::
104106

105-
## Maximum event capacity
107+
## Event timeline capacity
106108

107-
The maximum number of events shown in the event timeline is dependent on [the hardware profile](ot-appliance-sizing.md) selected during sensor installation.
108-
Each profile has a maximum capacity of events that will show on the event timeline. Once the maximum event capacity is reached, the oldest events will be rolled over and deprecated.
109+
The amount of data that can be stored in the event timeline depends on various factors, such as the size of the network, the frequency of events, and the storage capacity of your sensor. The data stored in the event timeline can include information about network traffic, security events, and other relevant data points.
109110

110-
For more information on the maximum event capacity for each hardware profile, see [OT event timeline retention](/azure/defender-for-iot/organizations/references-data-retention?branch=pr-en-us-221446).
111+
The maximum number of events shown in the event timeline is dependent on [the hardware profile](ot-appliance-sizing.md) selected during sensor installation. Each hardware profile has a maximum capacity of events. For more information on the maximum event capacity for each hardware profile, see [OT event timeline retention](/azure/defender-for-iot/organizations/references-data-retention?branch=pr-en-us-221446).
111112

112113
## Next steps
113114

0 commit comments

Comments
 (0)