Skip to content

Commit 79f1142

Browse files
committed
Yonina/Ariel event timeline feedback
1 parent 24f3f0d commit 79f1142

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

articles/defender-for-iot/organizations/references-data-retention.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -18,8 +18,8 @@ The following table lists how long device data in stored in each Defender for Io
1818
| Storage type | Details |
1919
|---------|---------|
2020
| **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). |
2323

2424
## Alert data retention
2525

@@ -38,7 +38,7 @@ The following table lists how long PCAP data is stored in each Defender for IoT
3838
| Storage type | Details |
3939
|---------|---------|
4040
| **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). |
4242
| **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. |
4343

4444
## Security recommendation retention
@@ -49,7 +49,9 @@ For more information, see [Enhance security posture with security recommendation
4949

5050
## OT event timeline retention
5151

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.
5355

5456
The following table lists the maximum number of events that can be stored for each hardware profile:
5557

0 commit comments

Comments
 (0)