01
Create a read-only credential
Create the credential in Jamf Pro with the minimum read scope, paste it into devguard, and the connection is live. The integration page in the product spells out the exact permissions.
devguard reads your Jamf Pro instance and verifies disk encryption device by device: FileVault enforced and recovery keys escrowed, across the whole Mac fleet.
3 read-only checks, run on a schedule. Each failure becomes a finding linked to a control — every check is listed, none are “coming soon”.
Connectivity check: confirms the minted bearer token reads computer inventory (HTTP 200). A non-200 (e.g. 401/403) indicates a bad credential, wrong instance, or an API role without computer-read permission.
api-reachable
Disk-encryption check for one managed computer: fails if FileVault 2 is not enabled on the supplied Jamf computer ID.
device-filevault-enabled
Recovery-key escrow check for one managed computer: fails if the individual FileVault recovery key Jamf holds is not in the VALID state (encryption is not recoverable).
device-recovery-key-valid
Bring your current platform's test list — we'll map it against these checks, gap by gap
Setup is minutes, not a migration project — and every step stays on your side
Create the credential in Jamf Pro with the minimum read scope, paste it into devguard, and the connection is live. The integration page in the product spells out the exact permissions.
The first run starts right after connecting, then repeats on a schedule. Results are timestamped, so your evidence has a history, not a snapshot.
Passing results attach as evidence to the controls they support; failures become findings you triage. When the audit comes, the proof is already connected.
Open any page for its full check register.
You create and scope every credential yourself, and you can revoke it at any time. Checks only read; results and evidence are stored in Switzerland and stay exportable.
Yes. The checks authenticate with a credential you create and scope yourself, and only ever read configuration. devguard holds no write access to Jamf Pro and remediates nothing silently.
A failed check becomes a finding linked to the control it supports, with the evidence attached. You decide the treatment — nothing pages your engineers and nothing is auto-remediated.
Checks run from Swiss infrastructure, and results and evidence are stored in Switzerland. Everything is exportable — your evidence stays yours.
20 minutes on how you run certification today. Bring your current test or control list and we'll map it against these checks — honestly, gap by gap.