Discharge7443/fleet
1
0
Fork 0
Code Issues Pull Requests Actions 27 Packages Projects Releases Wiki Activity

Disk encryption guide: Clarify when escrow happens for macOS (#45412)

Browse Source 
Context:
https://fleetdm.slack.com/archives/C09HG9VMRSS/p1778612106854329
This commit is contained in:
Noah Talerman
2026-05-15 09:03:50 -04:00
committed by GitHub
parent e149911183
commit a8e0212342
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
articles/enforce-disk-encryption.md
+1 -1
View File
@@ -8,7 +8,7 @@ In Fleet, you can enforce disk encryption for your macOS and Windows hosts, and
When disk encryption is enforced, hosts' disk encryption keys will be stored in Fleet.
For macOS hosts that automatically enroll, end users are forced to enable disk encryption during Setup Assistant. For hosts that manually enroll, end users are forced to enable disk encryption the next time they log out and log back in. For both enroll methods, end users can't defer.
For macOS hosts that automatically enroll, end users are forced to enable disk encryption during Setup Assistant and the disk encryption key is automatically escrowed to Fleet. For hosts that manually enroll, end users are forced to enable disk encryption. The key gets escrowed the next time they log out and log back in. For both enroll methods, end users can't defer.
For Windows, currently disk encryption is enforced on the C: volume (default system/OS drive) only on hosts with a [TPM chip](https://support.microsoft.com/en-us/topic/what-s-a-trusted-platform-module-tpm-705f241d-025d-4470-80c5-4feeb24fa1ee). For Linux, encryption requires end user interaction.