Jamf Pro
Security tooling · API key / service-account token · Daily
API client (client_credentials). Pulls FileVault disk-encryption coverage and MDM managed-device coverage — the platform's first endpoint-configuration (SC-28/CM-6) evidence from device management.
- Authentication
- API key / service-account token
- Sync cadence
- Daily
- Stale threshold
- Every 2 days
- Category
- Security tooling
Evidence this connector produces
Every sync writes typed evidence rows linked to the controls below. Evidence is immutable once attached to an approved assessment, fingerprinted for de-dup, and surfaced in the control coverage calculation on your dashboard.
How to connect
Create a read-only API role + client in Jamf Pro and paste your instance URL + client credentials.
- 1Create the API role
Jamf Pro → Settings → System → API roles and clients → API Roles → New. Grant privilege: Read Computers.
- 2Create the API client
API Clients → New → assign the role → Enable. Copy the Client ID, then Generate client secret (shown once).
- 3Note your instance URL
Your Jamf Pro URL, e.g. https://acme.jamfcloud.com — paste the full https URL.
Security model
Every connector ships behind the same auditor-grade primitives — not just RBAC config, but architectural enforcement.
Tokens, client secrets, and service-account keys are encrypted under a per-tenant AWS KMS data key. The plaintext is never persisted, never logged, and never leaves the FastAPI process boundary.
Every Connection, ConnectorRun, and emitted Evidence row carries an organization ObjectId. The scheduler never iterates without an org-scoped filter; cross-tenant evidence bleed is impossible at the data layer.
Connect, sync, sync-failure, re-auth, and revoke each write a row to the immutable AuditLog. The full lifecycle is reconstructable for any examiner.
Revoking a connection sets deletedAt and clears the encrypted credential blob, but the historical evidence + sync log stays queryable for the retention window. Auditors can still trace what was attested when.
If this connector hasn't synced in Every 2 days, control coverage degrades automatically and an alert fires. Auditors don't trust stale evidence — neither do we.
We request the minimum read-only scopes needed for the listed evidence. No write scopes, no admin scopes, no scopes outside the documented set.
Ready to connect Jamf Pro?
Connect from Settings → Integrations — typically under 5 minutes. Or talk to us first.