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.
Beta. This connector was built from Jamf Protect’s documentation and hasn’t been verified against a live account yet. It may return incomplete data or fail in ways we haven’t seen. If something looks wrong, contact support@chartingcyber.com.
At a glance
| Data provided | Devices |
|---|---|
| Authentication | API Client (Client ID + Password) |
| Where to configure | Connectors → Add a Connector → Jamf Protect |
Required permissions
| Credential | Where to find it |
|---|---|
| Client ID / Client Password | Jamf Protect console → Administrative → API Clients |
| Deployment hostname | Your Jamf Protect tenant address, e.g. yourorg.protect.jamfcloud.com |
Setup
- In the Jamf Protect console, go to Administrative → API Clients and create a new API Client.
- Note the Client ID and the generated Password.
- Note your deployment hostname, the subdomain your Jamf Protect console is hosted at.
- In Navigator, go to Connectors → Add a Connector → Jamf Protect.
- Enter your Deployment hostname, Client ID, and Client Password.
- 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, and internal/external IP address.
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.
- This connector was built from Jamf’s published API reference and official example scripts rather than tested against a live tenant. If you notice a field that looks wrong or missing, let us know so it can be corrected against real data.