About FileVault & Recovery Keys
FileVault is a built-in feature of macOS that encrypts the boot drive. During setup, FileVault generates a Recovery Key, allowing an additional method of access to the drive should all FileVault enabled users’ passwords be forgotten.- Learn more about how FileVault secures your Mac computers and changes login behavior
- Learn how to use the FileVault Recovery Key to reset a user’s password
- Learn about the User Experience with FileVault
About the FileVault Library Item
The FileVault 2 Library Item enforces FileVault disk encryption on enrolled Mac computers. Mac computers are prompted to complete FileVault setup after they restart. To add this Library Item to your Iru Endpoint Library, follow the steps outlined in the Library Overview article.FileVault Configuration Options
Configure FileVault using the steps below. Enforcement and user experience are part of the same flow as the Library Item settings.FileVault enforcement
- Enforce immediately upon next login (Recommended): FileVault is required at the next login. The Enforce during Setup Assistant for Automated Device Enrollment option appears when this is selected.
- Allow user deferral before enforcing (Not Recommended): The Prompt for restart if FileVault is not enabled option is hidden; a User Deferral drop-down appears instead so you can select how many login attempts are allowed before FileVault is enabled.
Enforce during Setup Assistant for Automated Device Enrollment (macOS 14+)
Prompt for restart if FileVault is not enabled

Show user the FileVault recovery key when it is generated
Escrow recovery keys to Iru Endpoint
Automatically rotate keys
Automatically rotate keys after viewing

Enforcement and user experience during Setup Assistant
When you enable Enforce during Setup Assistant for Automated Device Enrollment (macOS 14+), Iru Endpoint attempts to enforce FileVault during Setup Assistant for devices that enroll using Automated Device Enrollment. This selection ignores a FileVault skip screen setting in the Automated Device Enrollment Library item. The end user first sees a FileVault Disk Encryption dialog: the organization has enabled FileVault for the Mac, and the user can turn on FileVault disk encryption and select Continue to encrypt the disk (no restart required). A Skip option may appear depending on configuration.

View FileVault Recovery Keys
The FileVault Recovery Key dialog hides the key until you display it, and Iru logs who viewed the key and when. What happens after a view depends on Automatically rotate keys after viewing in FileVault Configuration Options:- On: Displaying the key starts Rotate keys after viewing (hours). When that time passes, Iru Endpoint rotates the key on the Mac with the RotateFileVaultKey MDM command.
- Off: The key does not rotate after it is viewed. If Automatically rotate keys is on, the key still rotates on that schedule.
GET /api/v1/devices/{device_id}/secrets/filevaultkey) counts as a view and follows the same setting.
Open the FileVault Recovery Key dialog
Navigate to Device Record
Access Device Action Menu
View Recovery Key

When rotation after viewing is on
Display the recovery key

Copy or hide the key

When rotation after viewing is off
Continue past the rotation notice

Display the recovery key

Copy or hide the key

Generate a New FileVault Recovery Key
You can force a Mac to generate a new FileVault recovery key by running the following command in Terminal. Iru Endpoint then captures the new key if the escrow option is enabled.Parameter: Report user accounts with FileVault Recovery Keys escrowed to iCloud
macOS allows users to store recovery keys with their Apple Account through iCloud. This is not recommended for enterprise-owned Mac computers because an unknown party may be able to retrieve the keys. Use this parameter to receive an alert when a recovery key is stored in iCloud. The alert reminds you to work with the user to remove the recovery key from their account.
Encryption Status
With APFS volumes, only the Data volumes will show as Encrypted: Yes in the Volumes section of the Device Details. This is expected behavior.