You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/references-data-retention.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,8 +18,8 @@ The following table lists how long device data in stored in each Defender for Io
18
18
| Storage type | Details |
19
19
|---------|---------|
20
20
|**Azure portal**| 90 days from the date of the **Last activity** value. <br><br> For more information, see [Manage your device inventory from the Azure portal](how-to-manage-device-inventory-for-organizations.md). |
21
-
|**OT network sensor**|Device inventory data is stored with no time limit. <br><br> For more information, see [Manage your OT device inventory from a sensor console](how-to-investigate-sensor-detections-in-a-device-inventory.md). |
22
-
|**On-promises management console**|Device inventory data is stored with no time limit. <br><br> For more information, see [Manage your OT device inventory from an on-premises management console](how-to-investigate-all-enterprise-sensor-detections-in-a-device-inventory.md). |
21
+
|**OT network sensor**|The retention of device inventory data is not time limited. <br><br> For more information, see [Manage your OT device inventory from a sensor console](how-to-investigate-sensor-detections-in-a-device-inventory.md). |
22
+
|**On-promises management console**|The retention of device inventory data is not time limited. <br><br> For more information, see [Manage your OT device inventory from an on-premises management console](how-to-investigate-all-enterprise-sensor-detections-in-a-device-inventory.md). |
23
23
24
24
## Alert data retention
25
25
@@ -38,7 +38,7 @@ The following table lists how long PCAP data is stored in each Defender for IoT
38
38
| Storage type | Details |
39
39
|---------|---------|
40
40
|**Azure portal**| PCAP files are available for download from the Azure portal for as long as the OT network sensor stores them. <br><br> Once downloaded, the files are cached on the Azure portal for 48 hours. <br><br> For more information, see [Access alert PCAP data (Public preview)](how-to-manage-cloud-alerts.md#access-alert-pcap-data-public-preview). |
41
-
|**OT network sensor**| 90 days, depending on the sensor's storage capacity <br><br> The maximum size of PCAP file storage is set by default to 133,120 MB. If a sensor exceeds this size, the oldest PCAP file is deleted to accommodate the new one. <br><br> For more information, see [Download PCAP files](how-to-view-alerts.md#download-pcap-files). |
41
+
|**OT network sensor**| 90 days, depending on the sensor's storage capacity. <br><br> The maximum size of PCAP file storage is set by default to 133,120 MB. If a sensor exceeds this size, the oldest PCAP file is deleted to accommodate the new one. <br><br> For more information, see [Download PCAP files](how-to-view-alerts.md#download-pcap-files). |
42
42
|**On-promises management console**| PCAP files aren't stored on the on-premises management console and are only accessed from the on-premises management console via a direct link to the OT sensor. |
43
43
44
44
## Security recommendation retention
@@ -49,7 +49,9 @@ For more information, see [Enhance security posture with security recommendation
49
49
50
50
## OT event timeline retention
51
51
52
-
OT event timeline data is stored on OT network sensors only, for as long as there's available storage space, which differs depending on the sensor's [hardware profile](ot-appliance-sizing.md).
52
+
OT event timeline data is stored on OT network sensors only, and the storage capacity differs depending on the sensor's [hardware profile](ot-appliance-sizing.md).
53
+
54
+
The retention of event timeline data is not time limited. If a sensor exceeds its maximum storage size, the oldest event timeline data file is deleted to accommodate the new one.
53
55
54
56
The following table lists the maximum number of events that can be stored for each hardware profile:
0 commit comments