Skip to content

Commit 377847c

Browse files
committed
wording
1 parent 460f20c commit 377847c

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

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

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -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 being dependent on the sensor's storage capacity.
47+
> To avoid being dependent on the sensor's storage capacity, use external storage to back up your PCAP data.
4848
4949
### Sensor storage capacity by hardware profile
5050

@@ -92,9 +92,9 @@ Other OT monitoring log files are stored only on the OT network sensor and the o
9292

9393
On both OT sensors and the on-premises management console, log files are stored in two different ways:
9494

95-
- Logs are saved on one file where the oldest content is overridden when the file reaches its maximum allocated size.
95+
- Logs are saved on one file where the oldest content is overridden when the file reaches its maximum capacity.
9696

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.
97+
- Logs are saved on several files, and once the number of files reaches a maximum, the oldest file is deleted to make room for a new one.
9898

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

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

114114
**Backups on the OT network sensor:**
115115

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:
116+
The retention of backup files depends on the sensor's architecture, as each type of device has a set amount of hard disk space allocated for backup history:
117117

118118
| Type of device | Allocated hard disk space |
119119
|---------|---------|
120-
| **Laptop** | zero |
121-
| **Rugged** | zero |
120+
| **Laptop** | Zero |
121+
| **Rugged** | Zero |
122122
| **Medium** | 20 GB |
123123
| **Small prod** | 60 GB |
124124
| **Prod** | 100 GB |
@@ -132,7 +132,7 @@ Allocated hard disk space for on-premises management console backup files is lim
132132

133133
If you're using an on-premises management console, each connected OT sensor also has its own, extra backup directory on the on-premises management console:
134134

135-
- A single sensor backup file is limited to a maximum of 40 GB. If the size of the file exceeds that, it won't be sent to the on-premises management console.
135+
- A single sensor backup file is limited to a maximum of 40 GB. A file exceeding that size won't be sent to the on-premises management console.
136136
- Total hard disk space allocated to sensor backup from all sensors on the on-premises management console is 100 GB.
137137

138138
For more information, see:

0 commit comments

Comments
 (0)