Track Network and Sensor Activity with the Event Timeline in Microsoft Defender for IoT
In brief
The article received updated metadata, wording, and clearer procedure structure for filtering, viewing, exporting, and manually adding timeline events.
What Defender admins need to know
Administrators can follow the event-timeline procedures more easily, including the stated Admin or Security Analyst access requirement.
Summaries are generated from the documentation change itself.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
Track network and sensor activity with the event timeline
Activity detected by your Microsoft Defender for IoT sensors detect 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.
The OT sensor's event timeline provides a chronological view and context of all network activity,activity to help determine the cause and effect of incidents. The timeline view makes it easy to extract information from network events,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.
Use the event timeline during investigations,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.
For more information, see:
Permissions required to view the event timeline
Before you perform the event timeline procedures described in this section,article, make sure that you have access to an OT sensor as an Admin or Security Analyst role. For more information, see On-premises users and roles for OT monitoring with Defender for IoT.
View the event timeline
Sign in to the sensor
console,console and select Event Timeline from the left menu.Review and filter the events as needed.
Select an event row to view the event details in a pane on the right, where you can also filter to view events of related devices. The User Operations filter is on by default, you can select to hide or show user events as needed.
For example:
You can also view the event timeline of a specific device from the Device inventory.
To view the event timeline of a specific device:device:
- In the sensor console, go to Device inventory.
Filter events on the timeline
Use the following steps to filter events shown on the timeline:
On the event timeline page, select Add filter to specify the events shown.
Select the filter Type. Use any of the following options to filter the devices shown:
Export the event timeline to CSV
You can export the event timeline to a CSV file, thefile. The exported data is according to any filters applied when exporting.
To export the event timeline:timeline:
On the Event timeline page, select Export from the top menu to export the event timeline to a CSV file.
Create an event
In addition to viewing the events that the sensor has detected, you can manually add events to the timeline. This process is useful if an external system event impacts your network,network and you want to record it on the timeline.
To manually add an event to the timeline:
On the Event timeline page, select Create Event.
In the Create Event dialog, add the following event details:
Type
.: Specify the event type (Info, Notice, or Alert).Timestamp
.: Set the date and time of the event.Device
.: Select the device the event should be connected with.Description
.: Provide a description of the event.
Select Save to add the event to the timeline.
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.
The maximum number of events shown in the event timeline is dependent on the OT appliance sizing and hardware profile selected during sensor installation. Each hardware profile has a maximum capacity of events. For more information on the maximum event capacity for eachby OT appliance hardware profile, see OT event timeline retention.
Next stepsRelated content
For more information, see:
@@ -1,19 +1,19 @@ ----title: Track network and sensor activity with the event timeline in Microsoft Defender for IoT+title: Track Network and Sensor Activity with the Event Timeline in Microsoft Defender for IoT description: Track network and sensor activity in the event timeline.-ms.date: 06/12/2026+ms.date: 07/03/2026 ms.topic: how-to-ms.custom: sfi-image-nochange, msecd-doc-authoring-1014+ms.custom: sfi-image-nochange, msecd-doc-authoring-1016 ai-usage: ai-assisted --- # Track network and sensor activity with the event timeline -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.+Activity your Microsoft Defender for IoT sensors detect 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. -The OT sensor's 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.+The OT sensor's 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. -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.+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. For more information, see: @@ -25,16 +25,16 @@ For more information, see: <a name="permissions"></a> ## Permissions required to view the event timeline -Before you perform the procedures described in this section, make sure that you have access to an OT sensor as an **Admin** or **Security Analyst** role. For more information, see [On-premises users and roles for OT monitoring with Defender for IoT](roles-on-premises.md).+Before you perform the event timeline procedures described in this article, make sure that you have access to an OT sensor as an **Admin** or **Security Analyst** role. For more information, see [On-premises users and roles for OT monitoring with Defender for IoT](roles-on-premises.md). ## View the event timeline -1. Sign in to the sensor console, and select **Event Timeline** from the left menu.+1. Sign in to the sensor console and select **Event Timeline** from the left menu. 1. Review and [filter the events](#filter-events-on-the-timeline) as needed. 1. Select an event row to view the event details in a pane on the right, where you can also filter to view events of related devices.-The **User Operations** filter is on by default, you can select to hide or show user events as needed.+ The **User Operations** filter is on by default, you can select to hide or show user events as needed. For example: @@ -42,7 +42,7 @@ The **User Operations** filter is on by default, you can select to hide or show You can also view the event timeline of a specific device from the **Device inventory**. -**To view the event timeline of a specific device**:+To view the event timeline of a specific device: 1. In the sensor console, go to **Device inventory**. @@ -56,6 +56,8 @@ You can also view the event timeline of a specific device from the **Device inve ## Filter events on the timeline +Use the following steps to filter events shown on the timeline:+ 1. On the event timeline page, select **Add filter** to specify the events shown. 1. Select the filter **Type**. Use any of the following options to filter the devices shown:@@ -76,27 +78,29 @@ You can also view the event timeline of a specific device from the **Device inve ## Export the event timeline to CSV -You can export the event timeline to a CSV file, the exported data is according to any filters applied when exporting.+You can export the event timeline to a CSV file. The exported data is according to any filters applied when exporting. -**To export the event timeline**:+To export the event timeline: On the **Event timeline** page, select **Export** from the top menu to export the event timeline to a CSV file.- + ## Create an event -In addition to viewing the events that the sensor has detected, you can manually add events to the timeline. This process is useful if an external system event impacts your network, and you want to record it on the timeline.+In addition to viewing the events that the sensor has detected, you can manually add events to the timeline. This process is useful if an external system event impacts your network and you want to record it on the timeline.++**To manually add an event to the timeline**: 1. On the **Event timeline** page, select **Create Event**. 1. In the **Create Event** dialog, add the following event details:- - - **Type**. Specify the event type (Info, Notice, or Alert).- - - **Timestamp**. Set the date and time of the event.- - - **Device**. Select the device the event should be connected with.- - - **Description**. Provide a description of the event.++ - **Type**: Specify the event type (Info, Notice, or Alert).++ - **Timestamp**: Set the date and time of the event.++ - **Device**: Select the device the event should be connected with.++ - **Description**: Provide a description of the event. 1. Select **Save** to add the event to the timeline. @@ -108,11 +112,9 @@ For example: 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. -The maximum number of events shown in the event timeline is dependent on [the OT appliance sizing and 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](references-data-retention.md#ot-event-timeline-retention).+The maximum number of events shown in the event timeline is dependent on [the OT appliance sizing and hardware profile](ot-appliance-sizing.md) selected during sensor installation. Each hardware profile has a maximum capacity of events. For more information on maximum event capacity by OT appliance hardware profile, see [OT event timeline retention](references-data-retention.md#ot-event-timeline-retention). -## Next steps--For more information, see:+## Related content - [Audit user activity](track-user-activity.md) - [View details and remediate a specific alert](how-to-view-alerts.md#view-details-and-remediate-a-specific-alert) 