What is JumpCloud integration?
Our JumpCloud integration allows you to sync devices-related information from your JumpCloud account and automates compliance checks and evidence collection (for example, hard drive encryption enforcement) using JumpCloud's REST APIs.
Important: For macOS devices managed through JumpCloud, Secureframe’s native antivirus check uses the JumpCloud Gatekeeper policy. It does not evaluate the XProtect version shown in the JumpCloud device view. A question-mark antivirus status means Secureframe cannot verify that policy data. It does not mean XProtect is disabled.
How to connect?
Follow the steps under "Generating a New API Key" to get a copy of your API Key which is required to set up a connection in Secureframe's JumpCloud connection form.
Navigate to Integrations>AVAILABLE INTEGRATIONS>JumpCloud
Permissions, Fields, Controls, and Automated Tests
Click the provided link or navigate to the “Integration” page.
Select the “Available” tab.
Search for the integration.
Click “View Details”.
Frequently Asked Questions (FAQ)
Does the JumpCloud integration support user related syncs?
The JumpCloud integration does not support user related syncs. To pull this information, a JumpCloud SCIM connection will need to be created. You may read more about SCIM Provisioning here.
Why does a Mac show an XProtect version in JumpCloud while Secureframe shows a question-mark antivirus status?
For macOS devices managed through JumpCloud, Secureframe’s native antivirus check uses the JumpCloud Gatekeeper policy configuration. It does not evaluate the XProtect version shown in the JumpCloud device view.
A question-mark antivirus status means Secureframe cannot verify the required antivirus-policy data for that device. It does not mean XProtect is disabled.
To resolve it, confirm that a Gatekeeper policy exists in JumpCloud, that it is assigned to the affected device or to a device group that contains it, and that users cannot override the policy. Then run a new JumpCloud sync in Secureframe so the policy data is re-evaluated.
If the Gatekeeper policy is assigned and enabled and the antivirus status still does not populate after a sync, contact Secureframe Support with screenshots of the policy settings and the policy assignment page.
Why do firewall and screen lock show as failing in Secureframe when the JumpCloud policies are assigned and compliant?
For devices managed through JumpCloud, Secureframe reads firewall and screen lock status from JumpCloud System Insights and the policies assigned to the device. If JumpCloud does not return full System Insights data for a device, Secureframe cannot verify these two checks, so they show as failing even when the policies are assigned and compliant in JumpCloud.
This most often happens when a device comes back online after a long period of inactivity. JumpCloud keeps System Insights data for 90 days and removes data for devices that have not reported within that time. A returning device may not report full System Insights data until its local cache is cleared. See JumpCloud’s System Insights documentation.
To resolve it, delete the file /opt/jc/systemInsightsCache.json on the affected Mac, then restart the JumpCloud agent. Wait up to 60 minutes for JumpCloud to receive a full System Insights report, then run a new JumpCloud sync in Secureframe.
If firewall and screen lock still show as failing after the sync, contact Secureframe Support with screenshots of the policy settings and the policy assignment page.