Endpoint ManagementJamf Pro

Jamf Pro

Configure the Jamf Pro Endpoint Management integration with RAD Security to ingest device inventory and compliance findings, and trigger device remediation.

This guide walks you through integrating Jamf Pro with RAD Security to ingest managed-device inventory and device compliance findings, and to trigger remediation on a device from RAD.

Jamf Pro is an Apple device management platform. RAD Security connects to the Jamf Pro API using OAuth 2.0 client credentials (an API role and client) and pulls device inventory and compliance posture on a scheduled basis to correlate them with your runtime, cloud, and Kubernetes security data.

Read-only ingestion, with one write action: RAD only reads device inventory and compliance from Jamf Pro. The single exception is device remediation — RAD can trigger a remediation action on a device through Jamf Pro. That action is RBAC-gated (requires tenant write permission) and recorded as an OCSF Device Control Finding.

Prerequisites

Before you begin, ensure you have:

  • A Jamf Pro instance with administrator access
  • Permission to create an API role and API client in Jamf Pro
  • Your Jamf Pro URL (your instance base URL)
  • Access to a RAD Security workspace with integration permissions

Understanding Integration Components


Step 1: Create an API Role and Client in Jamf Pro

Sign in to Jamf Pro

Log in to your Jamf Pro instance with an administrator account.

Create an API Role

Go to Settings → System → API roles and clients → API Roles and create a new role. Grant the privileges required to read inventory and compliance (and remediation privileges if you will use device remediation).

Create an API Client

On the API Clients tab, create a new client, assign the API role you created, and enable it. Note the Client ID.

Generate a Client Secret

Generate a Client Secret for the API client and copy its value.

Copy the Client Secret immediately — it is shown only once at generation time. Store it securely in a password manager or secrets vault.

Note Your Jamf Pro URL

Record your Jamf Pro URL (your instance base URL, for example https://yourcompany.jamfcloud.com).

Exact console navigation, privilege names, and labels may vary across Jamf Pro versions. See the Jamf Pro documentation for current steps to create API roles and clients.


Configure in RAD Security

Navigate to your RAD Security workspace and configure the Jamf Pro integration with the following parameters:

Required Parameters

ParameterRequiredDescription
Client IDYesOAuth 2.0 Client ID of the Jamf Pro API client
Client SecretYesOAuth 2.0 Client Secret generated for the API client
Jamf Pro URLYesBase URL of your Jamf Pro instance

Verify Integration

Check Connection Status

  1. Navigate to Data Sources > Integrations > Endpoint Management in RAD Security
  2. Locate your Jamf Pro integration
  3. Verify the connection status shows as Connected

Your Jamf Pro integration is now configured! RAD Security will ingest device inventory and compliance findings from Jamf Pro on a scheduled basis.

What Data is Synced

Use Cases

Compliance Management Track device compliance gaps from discovery through remediation across your Jamf-managed Apple fleet.

Asset Visibility Use managed-device inventory to understand your endpoint estate and reduce attack surface.

Threat Response Trigger Jamf Pro remediation on a non-compliant or compromised device directly from RAD.

RADBot Prioritization Leverage RADBot to prioritize Jamf Pro device findings by real-world impact.

Troubleshooting

Security Best Practices

Dedicated API Client Use a dedicated API client and role for the RAD integration rather than sharing one with other tools.

Least Privilege Grant the API role only the privileges required for inventory, compliance, and remediation.

Rotate Credentials Rotate the client secret periodically according to your security policy.

Secure Secret Storage Store the client secret in a secrets vault. Never commit it to version control.

Additional Resources

Next Steps