Skip to content

Commit 2e69caa

Browse files
committed
final
1 parent 433a951 commit 2e69caa

File tree

1 file changed

+11
-16
lines changed

1 file changed

+11
-16
lines changed

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

Lines changed: 11 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,21 @@
11
---
22
title: Data retention and sharing across Microsoft Defender for IoT
3-
description: Learn about the data retention periods and capacities for Microsoft Defender for IoT data stored in Azure, the OT sensor, and on-premises management console.
3+
description: Learn about the data retention periods and capacities for Microsoft Defender for IoT data stored in Microsoft Azure, the OT sensor, and on-premises management console.
44
ms.topic: conceptual
55
ms.date: 01/22/2023
66
---
77

88
# Data retention, privacy, and sharing across Microsoft Defender for IoT
99

10-
Microsoft Defender for IoT stores data in the Azure portal, on OT network sensors, and on-premises management consoles.
10+
Microsoft Defender for IoT stores data in the MIcrosoft Azure portal, in OT network sensors, and in on-premises management consoles.
1111

12-
Each storage type has various storage capacity options and retention times. This article describes the data retention policy as well as the amount of data and length of time it's stored in each storage type before being deleted or overwritten.
12+
Each storage type has varying storage capacity options and retention times. This article describes the data retention policy for the amount of data and length of time it's stored in each storage type before being deleted or overwritten.
1313

1414
## What are we collecting?
1515

1616
Defender for IoT collects information from your configured devices and stores it in a service specific, customer-dedicated and segregated tenant. The stored data is for administration, tracking, and reporting purposes.
1717

18-
Information collected includes network connection data (IPs and ports), and device details (device identifiers, names, operating system versions, firmware versions).
19-
20-
Microsoft stores this data securely in Microsoft Azure portal and maintains it in accordance with Microsoft privacy practices and [Microsoft Trust Center policies](https://azure.microsoft.com/explore/trusted-cloud/).
18+
Information collected includes network connection data (IPs and ports), and device details (device identifiers, names, operating system versions, firmware versions). Defender for IoT stores this data securely in accordance with Microsoft privacy practices and [Microsoft Trust Center policies](https://azure.microsoft.com/explore/trusted-cloud/).
2119

2220
This data enables Defender for IoT to:
2321

@@ -32,7 +30,7 @@ Microsoft doesn't use your data for advertising.
3230
Defender for IoT uses the Microsoft Azure data centers in the European Union and the United States. Customer data collected by the service might be stored in one of two geo-locations:
3331

3432
- The geo-location of the tenant as identified during provisioning.
35-
- The geo-location as defined by the data storage rules of an online service if this online service is used by Defender for IoT to process such data.
33+
- The geo-location as defined by the data storage rules of an online service if it's used by Defender for IoT to process such data.
3634

3735
## Data retention
3836

@@ -113,29 +111,26 @@ For more information, see:
113111
- [Troubleshoot the sensor](how-to-troubleshoot-sensor.md)
114112
- [Troubleshoot the on-premises management console](legacy-central-management/how-to-troubleshoot-on-premises-management-console.md)
115113

116-
## On-premises backup file capacity
117-
118-
Both the OT network sensor and the on-premises management console have automated backups running daily.
114+
## Backup file capacity
119115

120-
On both the OT sensor and the on-premises management console, older backup files are overridden when the configured storage capacity reaches its maximum.
116+
Both the OT network sensor and the on-premises management console have automated backups running daily, and older backup files are overwritten when the configured storage capacity reaches its limit.
121117

122118
For more information, see:
123119

124120
- [Set up backup and restore files on an OT sensor](back-up-restore-sensor.md#set-up-backup-and-restore-files)
125121
- [Configure OT sensor backup settings on an on premises management console](legacy-central-management/back-up-sensors-from-management.md#configure-ot-sensor-backup-settings)
126-
- [Configure OT sensor backup settings for an on-premises management console](legacy-central-management/back-up-sensors-from-management.md#configure-ot-sensor-backup-settings)
127122

128123
### Backups on the OT network sensor
129124

130125
The retention of backup files depends on the sensor's architecture, as each hardware profile has a set amount of hard disk space allocated for backup history:
131126

132127
| Hardware profile | Allocated hard disk space |
133128
|---------|---------|
134-
| **L100** | Backups aren't supported |
135-
| **L500** | 20 GB |
129+
| **L100** | Backups aren't supported |
130+
| **L500** | 20 GB |
136131
| **E1000** | 60 GB |
137-
| **E1800** | 100 GB |
138-
| **C5600** | 100 GB |
132+
| **E1800** | 100 GB |
133+
| **C5600** | 100 GB |
139134

140135
If the device can't allocate enough hard disk space, then only the last backup is saved on the on-premises management console.
141136

0 commit comments

Comments
 (0)