Available in Fleet Premium
In Fleet, you can enforce disk encryption for your macOS and Windows hosts.
When disk encryption is enforced, hosts’ disk encryption keys will be stored in Fleet.
For Windows hosts, disk encryption is enforced on the C: volume (default system/OS drive).
You can enforce disk encryption using the Fleet UI, Fleet API, or Fleet's GitOps workflow.
In Fleet, head to the Controls > OS settings > Disk encryption page.
Choose which team you want to enforce disk encryption on by selecting the desired team in the teams dropdown in the upper left corner.
Check the box next to Turn on and select Save.
Fleet API: API documentation is here.
In the Fleet UI, head to the Controls > OS settings > Disk encryption tab. You will see a table that shows the status of disk encryption on your hosts.
Verified: the host turned disk encryption on and sent their key to Fleet. Fleet verified with osquery. See instructions for viewing the disk encryption key here.
Verifying: the host acknowledged the MDM command to install the disk encryption profile. Fleet is verifying with osquery and retrieving the disk encryption key.
It may take up to one hour for Fleet to collect and store the disk encryption keys from all hosts.
Action required (pending): the end user must take action to turn disk encryption on or reset their disk encryption key.
Enforcing (pending): the host will receive the MDM command to install the configuration profile when the host comes online.
Removing enforcement (pending): the host will receive the MDM command to remove the disk encryption profile when the host comes online.
Failed: hosts that are failed to enforce disk encryption.
You can click each status to view the list of hosts for that status.
How to view the disk encryption key:
Select a host on the Hosts page.
On the Host details page, select Actions > Show disk encryption key.
When migrating macOS hosts another MDM solution, in order to complete the process of encrypting the hard drive and escrowing the key in Fleet, your end users must take action.
If the host already had disk encryption turned on, the user will need to input their password.
If the host did not already have disk encryption turned on, the user will need to log out or restart their computer.
Share these guided instructions with your end users.
If you notice something we've missed or could be improved on, please follow this link and submit a pull request to the Fleet repo.
Back to top