Skip to main content

Jamf Protect

Jamf Protect connects your protected macOS device inventory into Navigator. This is a separate Jamf product from Jamf Pro, with its own credentials and its own connector.

At a glance

Data providedDevices
AuthenticationAPI Client (Client ID + Password)
Where to configureConnectors → Add a Connector → Jamf Protect

Required permissions

CredentialWhere to find it
Client ID / Client PasswordJamf Protect console → Administrative → API Clients
Deployment hostnameYour Jamf Protect tenant address, e.g. yourorg.protect.jamfcloud.com. Enter just the hostname: no https:// and no trailing slash.

The API Client needs a role that can read computers. Assign Jamf’s built-in Read Only role. A role limited to the minimum Jamf suggests for an API client (read-only access to Plans, API Clients and Downloads) does not include reading computers: the connector signs in, but its request is refused with “Not Authorized: Inadequate Role Permissions”. If you see that message, check the API Client’s role.

Setup

  1. In the Jamf Protect console, go to Administrative → API Clients and create a new API Client.
  2. Note the Client ID and the generated Password.
  3. Note your deployment hostname, the subdomain your Jamf Protect console is hosted at.
  4. In Navigator, go to Connectors → Add a Connector → Jamf Protect.
  5. Enter your Deployment hostname (hostname only), Client ID, and Client Password.
  6. Save. Navigator validates the credentials and enqueues a first sync immediately.

Vendor documentation

Jamf’s own API introduction: Meet the Jamf Protect API.

What data this connector provides

  • Devices: every device protected by Jamf Protect, including hostname, serial number, model, operating system version, internal/external IP address, and the time of its last check-in (its last activity time).

Every device reported by this connector is treated as having agent-based coverage, since Jamf Protect itself is an installed agent.

Jamf Protect’s own security alerts (for example, malicious process execution or suspicious file activity) aren’t imported. These are behavioral detections, not vulnerability data, so they don’t fit Navigator’s asset-vulnerability model.

Known limitations

  • No MAC address is available for devices from this connector.