Skip to main content
The Ops Playbook

Kandji vs Jamf Pro for FileVault: How Each Escrows, Shows and Rotates Mac Recovery Keys

How does Kandji compare to Jamf for FileVault? Where each escrows the Mac recovery key, who can view it, how views are logged and how keys rotate.

Kandji vs Jamf Pro for FileVault: How Each Escrows, Shows and Rotates Mac Recovery Keys
KBY Technologies11 min readTier L115 min

Jamf Pro and Kandji (now Iru Endpoint) both rely on the same macOS mechanism: the Mac generates one personal recovery key (PRK) per encrypted volume, encrypts it with a certificate from the device management service and returns it for escrow. The differences that matter in operation are when the key reaches the console, who can see it, what records the view and how the key is rotated afterwards. Jamf Pro escrows a PRK from a configuration profile at the Mac’s next inventory update, logs each view in the computer’s audit history and rotates keys through a policy. Iru Endpoint escrows from its FileVault Library Item, logs who viewed the key and can rotate it automatically on a schedule or a set number of hours after someone views it. The constraint that applies to both: a key only reaches the console after FileVault is on and the escrow setting is in place, so a Mac encrypted before enrolment has no escrowed key until it generates a new one.

#How FileVault keys are usually handled today

In many fleets FileVault was switched on by whatever was easiest at the time. Some Macs were encrypted by their users before enrolment, a few were set up with a temporary provisioning account, and the key is assumed to be in the MDM because the disk reports as encrypted. Nobody checks until the service desk needs a key for a locked Mac and finds the record empty.

In a Kandji and Jamf Pro comparison, FileVault usually gets one line: both enforce it, both escrow keys. True, and not much use. The difference shows up when someone has to view a key, read it to a user and then make sure it stops working.

Apple describes the mechanism underneath: the service gives the Mac a certificate, the Mac encrypts the PRK in a CMS envelope and returns it in the security information query. There is one PRK per encrypted volume, and the service can rotate it, for example after it has been used to unlock a volume. Each vendor builds viewing, logging and rotation on top of that.

#A better way to compare FileVault in Jamf Pro and Kandji

Compare the two on the key’s life cycle, stage by stage, as each vendor documents it.

FileVault enforcement and recovery key handling in Jamf Pro and Kandji (Iru Endpoint)
StageJamf ProKandji (Iru Endpoint)
Where FileVault is setA configuration profile (Security & Privacy payload, FileVault) or a disk encryption configuration deployed by a policy. Use only one method per Mac.The FileVault Library Item, assigned to a Blueprint.
When enforcement startsProfile: prompt at login or logout once installed. Force Enable In Setup Assistant needs the profile in a PreStage enrollment and macOS 14.0 or later.Enforce immediately upon next login (recommended) or Allow user deferral. Optional enforcement during Setup Assistant for Automated Device Enrollment on macOS 14 or later.
When the key is escrowedProfile: at the next inventory update. Policy: immediately, by the Jamf binary.Sent to Iru Endpoint when Escrow recovery keys to Iru Endpoint is on.
Mac already encrypted at enrolmentGenerate a new PRK with fdesetup changerecovery -personal (or a tool such as Escrow Buddy), then run an inventory update.The agent prompts the user to authenticate and regenerate the key so it can be escrowed.
Who can view a keyUsers with the View Disk Encryption Recovery Key privilege.Team members, from the device record’s Device Action Menu or the Enterprise API.
Record of each viewHistory > Audit Logs on the computer record; server-side in the jss_audit table.Iru logs who viewed the key and when.
RotationA policy with the Disk Encryption payload set to Issue New Recovery Key. On macOS 26 or later, installing or updating the escrow profile while a bootstrap token is present rotates the PRK.Automatically rotate keys every set number of days, and rotate a set number of hours after viewing, using the RotateFileVaultKey MDM command.

So Jamf Pro offers more ways to switch FileVault on but leaves rotation after a view to a policy someone runs, as Jamf recommends. Iru keeps enforcement, escrow and rotation in one Library Item and can rotate a viewed key by itself. If you are deciding whether to stay on Kandji or move, the Kandji to Iru upgrade or Jamf Pro migration decision covers the wider choice, and this comparison is one input to it.

The flow below shows what happens after a support engineer views a key in each product, because that is where the two diverge most.

Rendering diagram...

#Setting up FileVault on one pilot Mac in each product

Use two test Macs, one enrolled in each product, with a test user. Record the current profile scope in Jamf Pro and the current Blueprint in Iru first; those notes are your rollback.

  1. Check the Mac before any change. In Terminal on each pilot Mac, run sudo fdesetup list -extended to see which users can unlock the disk, and sudo profiles status -type bootstraptoken to see whether the MDM supports a bootstrap token and whether one is escrowed. Expected evidence: the end user’s account is listed by fdesetup. Stop if the only listed user is a temporary or management account; Jamf warns that deleting the only FileVault enabled user leaves a disk that cannot be unlocked, and such a Mac must be wiped.
  2. Jamf Pro: create the profile. Go to Computers > Configuration profiles > New. In the Security & Privacy payload, click FileVault, include Enable FileVault, set Event to prompt FileVault enablement to At Login, choose Personal recovery key and select Escrow Personal Recovery Key. Scope the profile to the pilot Mac only and save. Do not also scope a disk encryption policy to it. Expected evidence: the profile shows as installed on the Mac, and the user is prompted at the next login. Rollback: remove the Mac from the profile’s scope and restore the scope you recorded.
  3. Jamf Pro: confirm escrow. The key is escrowed at the next inventory update, so after the user has logged in and FileVault is on, run sudo /usr/local/bin/jamf recon on the Mac to send one now. Then open the computer’s Inventory tab, select Disk Encryption and click Show Key. Stop if no key is shown; see the mistakes below.
  4. Iru: configure the Library Item. Add a FileVault Library Item, set FileVault enforcement to Enforce immediately upon next login, clear Show user the FileVault recovery key when it is generated if your policy is not to show keys to users, turn on Escrow recovery keys to Iru Endpoint, and set Automatically rotate keys and Automatically rotate keys after viewing with the days and hours you want. Assign it only to the pilot Blueprint. Expected evidence: after a restart the user is prompted to complete FileVault setup. Rollback: move the pilot Mac back to its recorded Blueprint.
  5. Iru: confirm escrow. On the device record, open the Device Action Menu and select View FileVault2 recovery key. With rotation after viewing on, displaying the key starts the timer, so do this deliberately and plan for a new key afterwards.

If a pilot Mac was already encrypted before enrolment, both vendors document the same manual fix: a user with a secure token runs sudo fdesetup changerecovery -personal while the escrow setting is in place. Jamf requires the escrow profile to be installed first and an inventory update afterwards; Iru captures the new key when escrow is on, and its agent normally prompts for this by itself.

Detailed close-up of a MacBook Pro keyboard showing the keys and backlight.
Photo by Moritz Kindler on Pexels

#Who can change FileVault settings and see keys

A recovery key unlocks the whole disk, so treat viewing one as privileged access.

  • In Jamf Pro, grant View Disk Encryption Recovery Key only to the support roles that unlock Macs. The Disk Encryption Configurations and Disk Encryption Institutional Configurations privileges control who can create or change configurations; keep them with the engineers who own FileVault policy.
  • Prefer personal recovery keys. Jamf notes that institutional keys can unlock many Macs, have more limited functionality on Apple silicon, and are no longer recommended by Apple for institutional management.
  • Decide whether users should see their key. Iru shows it by default; turning that off leaves the escrowed copy as the only one.
  • Keep users’ keys out of personal iCloud accounts on company Macs. Iru has a parameter that alerts when a key is stored in iCloud, so you can work with the user to remove it.
  • Never make the Jamf Pro management account, or a provisioning account you later delete, the first FileVault enabled user.

#Verifying escrow on the pilot Macs

These checks only read state.

  1. Run sudo fdesetup list -extended again. Pass: the end user is listed as able to unlock the disk.
  2. In Jamf Pro, Show Key on the pilot computer’s Disk Encryption inventory and confirm that History > Audit Logs records the view. Pass: a key is shown and the view appears in the log.
  3. In Iru, view the key once and confirm the log entry. With rotation after viewing on, check after the configured hours that a different key is shown. Pass: the view is logged and the key has changed.
  4. In Iru device details, check Volumes. Only the APFS Data volume reports Encrypted: Yes, which Iru documents as expected.

#What goes wrong with FileVault escrow

  • No key in the console for a Mac that is encrypted. FileVault was turned on before the escrow setting reached the Mac, or before enrolment. Generate a new PRK as above. In Jamf Pro, also check that the escrow profile is installed and run an inventory update.
  • Two Jamf Pro methods on one Mac. A profile and a disk encryption policy are both scoped. Jamf says this can produce unexpected behaviour; remove one.
  • Jamf Pro rotation policy never completes. Jamf requires either a valid PRK stored in Jamf Pro or a FileVault enabled user with a secure token. Run sudo fdesetup list -extended to see which users can unlock the disk; if none of them can sign in to approve the change, escalate rather than create accounts, because only a FileVault enabled user can enable others.
  • Iru rotation stalls on users with old passwords. With Automatically rotate keys on and a Passcode profile setting Maximum Passcode Age, an expired password must be changed before the key can rotate and be escrowed.
  • Users keep putting off encryption. Iru’s Allow user deferral setting is marked not recommended; deferred enablement in Apple’s model also waits for a login or logout. Use immediate enforcement for company Macs.
A close-up of a hand typing on a silver laptop with a Russian keyboard layout, showcasing modern technology.
Photo by cottonbro studio on Pexels

#Backing out the pilot

Backing out means restoring the scope you recorded, not decrypting the Mac. In Jamf Pro, take the pilot Mac out of the FileVault profile’s scope and restore the original scope. In Iru, return the Mac to its recorded Blueprint. First confirm the current key through your normal secure process, because a rotation may have replaced the key you saw earlier. Do not turn FileVault off to undo a pilot; the disk should stay encrypted throughout. Confirm afterwards with sudo fdesetup list -extended that the same users can still unlock the disk.

#What to track after rollout

  • The share of encrypted Macs with a key that can be shown in the console, checked each week until it stops changing and then each month.
  • Every key view, and whether a new key followed it. In Iru this should be automatic when rotation after viewing is on; in Jamf Pro, each view in the audit log should have a matching Issue New Recovery Key run.
  • Macs where the only FileVault enabled user is not the person who uses the Mac.
  • Rotation failures, which in Iru usually trace back to expired passwords.

Add these to the side-by-side Kandji and Jamf Pro pilot scoring as a FileVault row. Update enforcement is a separate comparison, covered in Kandji Managed OS against Jamf Pro Blueprints.

#Before you switch FileVault management to the new MDM

  • Each pilot Mac shows a key in the console, and the view is logged.
  • The end user, not a temporary or management account, is a FileVault enabled user.
  • Only one Jamf Pro method targets each Mac.
  • Viewing rights are limited to the roles that unlock Macs.
  • You know how a viewed key becomes a new key: an Iru setting or a Jamf Pro policy that someone owns.
  • Macs encrypted before enrolment have a plan to generate and escrow a new PRK.
  • The recorded scopes and Blueprints are kept so you can back out.

About this page

Credited to

Dates

Published

Sources

This page lists no external sources.

Corrections

No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.

Reader Interaction

Comments

Add a thoughtful note on Kandji vs Jamf Pro for FileVault: How Each Escrows, Shows and Rotates Mac Recovery Keys. Comments are checked for spam and held for moderation before appearing.

Loading comments...

Discover more

Was this useful?

Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.

Operate smarter, with fewer recurring tickets.

Receive new operational playbooks, incident-prevention guidance, automation scripts and recovery runbooks.