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
+11-16Lines changed: 11 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,23 +1,21 @@
1
1
---
2
2
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.
4
4
ms.topic: conceptual
5
5
ms.date: 01/22/2023
6
6
---
7
7
8
8
# Data retention, privacy, and sharing across Microsoft Defender for IoT
9
9
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.
11
11
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.
13
13
14
14
## What are we collecting?
15
15
16
16
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.
17
17
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/).
21
19
22
20
This data enables Defender for IoT to:
23
21
@@ -32,7 +30,7 @@ Microsoft doesn't use your data for advertising.
32
30
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:
33
31
34
32
- 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.
36
34
37
35
## Data retention
38
36
@@ -113,29 +111,26 @@ For more information, see:
113
111
-[Troubleshoot the sensor](how-to-troubleshoot-sensor.md)
114
112
-[Troubleshoot the on-premises management console](legacy-central-management/how-to-troubleshoot-on-premises-management-console.md)
115
113
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
119
115
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.
121
117
122
118
For more information, see:
123
119
124
120
-[Set up backup and restore files on an OT sensor](back-up-restore-sensor.md#set-up-backup-and-restore-files)
125
121
-[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)
127
122
128
123
### Backups on the OT network sensor
129
124
130
125
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:
131
126
132
127
| Hardware profile | Allocated hard disk space |
133
128
|---------|---------|
134
-
|**L100**| Backups aren't supported|
135
-
|**L500**| 20 GB|
129
+
|**L100**| Backups aren't supported |
130
+
|**L500**|20 GB |
136
131
|**E1000**| 60 GB |
137
-
|**E1800**| 100 GB |
138
-
|**C5600**| 100 GB |
132
+
|**E1800**| 100 GB |
133
+
|**C5600**| 100 GB |
139
134
140
135
If the device can't allocate enough hard disk space, then only the last backup is saved on the on-premises management console.
0 commit comments