Skip to content

Commit 460f20c

Browse files
committed
minor edits
1 parent b377197 commit 460f20c

File tree

1 file changed

+11
-12
lines changed

1 file changed

+11
-12
lines changed

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

Lines changed: 11 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -18,8 +18,8 @@ The following table lists how long device data is 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** | The retention of device inventory data is not limited by time. <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 limited by time. <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 isn't limited by time. <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 isn't limited by time. <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

@@ -44,7 +44,7 @@ The following table lists how long PCAP data is stored in each Defender for IoT
4444
The utilization of available PCAP storage space depends on factors such as the number of alerts, the type of the alert, and the network bandwidth, all of which affect the size of the PCAP file.
4545

4646
> [!TIP]
47-
> Use external storage to back up PCAP data without dependency on the sensor's storage capacity.
47+
> Use external storage to back up PCAP data without being dependent on the sensor's storage capacity.
4848
4949
### Sensor storage capacity by hardware profile
5050

@@ -68,7 +68,7 @@ For more information, see [Enhance security posture with security recommendation
6868

6969
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).
7070

71-
The retention of event timeline data is not limited by time. If a sensor exceeds its maximum storage size, the oldest event timeline data file is deleted to accommodate the new one.
71+
The retention of event timeline data isn't limited by time. If a sensor exceeds its maximum storage size, the oldest event timeline data file is deleted to accommodate the new one.
7272

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

@@ -90,12 +90,11 @@ Service and processing log files are stored on the Azure portal for 30 days from
9090

9191
Other OT monitoring log files are stored only on the OT network sensor and the on-premises management console.
9292

93-
On both OT sensors and the on-premises management console, files are stored for as long as there's available storage space. When the appliance's storage capacity reaches its maximum, the oldest log files are deleted to make room for the new ones.
93+
On both OT sensors and the on-premises management console, log files are stored in two different ways:
9494

95-
Logs are stored in two different ways:
95+
- Logs are saved on one file where the oldest content is overridden when the file reaches its maximum allocated size.
9696

97-
- Logs are saved on one file where the oldest content is overridden when the file reaches it's maximum size
98-
- Logs are saved on a number of files, and once the number of files reaches the maximum, the oldest file is deleted.
97+
- Logs are saved on several files, and once the number of files reaches the maximum storage capacity, the oldest file is deleted to make room for a new one.
9998

10099
Log files sizes differ depending on the amount of content, but the average size per log file is 100-150 MB.
101100

@@ -114,18 +113,18 @@ For more information, see [Set up backup and restore files](how-to-manage-indivi
114113

115114
**Backups on the OT network sensor:**
116115

117-
The retention of backup files is dependent on the OT network sensor's architecture, where each type of device has a set amount of hard disk space allocated for backup history:
116+
The retention of backup files is dependent on the OT network sensor's architecture. Each type of device has a set amount of hard disk space allocated for backup history:
118117

119118
| Type of device | Allocated hard disk space |
120119
|---------|---------|
121-
| **Laptop** | 0 |
122-
| **Rugged** | 0 |
120+
| **Laptop** | zero |
121+
| **Rugged** | zero |
123122
| **Medium** | 20 GB |
124123
| **Small prod** | 60 GB |
125124
| **Prod** | 100 GB |
126125
| **Core** | 100 GB |
127126

128-
If the device has 0 allocated hard disk space, then only the last backup will be saved.
127+
If the device has zero allocated hard disk space, then only the last backup will be saved.
129128

130129
**Backups on the on-premises management console:**
131130

0 commit comments

Comments
 (0)