Skip to main content
All CollectionsIntegrations
JumpCloud MDM Connection Details
JumpCloud MDM Connection Details

This article walks through the details of configuring JumpCloud MDM to connect to Drata.

Ashley Hyman avatar
Written by Ashley Hyman
Updated over a week ago


Having secure devices plays a major role in meeting compliance requirements. We want to support as many Mobile Device Management solutions (MDMs) as possible, in addition to providing our agent. We have heard from many of you that you use JumpCloud's MDM solution. This article goes over how to sync & bring all of your compliance-related information from JumpCloud to Drata.


Before Diving In…

  1. Make sure you have admin access to your company's JumpCloud account.

  2. Your JumpCloud account has access to JumpCloud APIs.

  3. Some of our checks use System Insights endpoints, note that these are not granted on all JumpCloud plans and may need to be enabled. You can check to see if it is enabled on your instance.

  4. The computers you want to monitor have the JumpCloud Agent installed.

  5. We currently support computers. Mobile and tablet devices are not supported.

  6. To monitor policies through JumpCloud on Mac OS devices, the device must be enrolled in JumpCloud MDM.

  7. At this time, Drata’s device compliance checks using the JumpCloud MDM connection confirms the following:

    1. Does the policy of the required name and/or type exist?

    2. Is that policy mapped to the device?

    3. Is that device compliant with that policy?

Current Limitations

  1. Drata has limited ability to read browser extensions through JumpCloud, at this time only Chrome Extensions are being read. Currently, if those are being used as a password manager, that compliance check will fail. Your users will need to use the equivalent installed desktop application. As a JumpCloud admin, ensure that this app shows on the device's Application List. Alternatively, you or your users can upload manual evidence in Drata.

  2. JumpCloud's APIs do not expose installed applications on Linux devices. Your Linux users will need to manually upload Antivirus and Password Manager app or browser extension evidence.

Step 1. Configure JumpCloud Device Policies and Commands

Drata makes use of the following Device Policies in our compliance checks. To learn more about JumpCloud Device Policies, please follow these instructions. During evaluation, Drata will check individual devices for a connected policy or that the device belongs to a Policy Group containing the policy:


  • BitLocker Full Disk Encryption

  • Configure Windows Updates

  • Lock Screen


  • FileVault 2

  • Lock Screen

  • Automatic macOS Updates (under Patch Management for Premium users) or Software Update Preferences (under Device Policies)

    • Note: JumpCloud’s Patch Management feature is not fully supported at this time and is only supported for Automatic macOS Updates.


  • Check Disk Encryption

  • Lock Screen

For other checks, we utilize the JumpCloud Commands functionality to run scripts on the system. These scripts can be found below, and then copy and pasted into your JumpCloud console. We recommend you configure JumpCloud to run these scripts at a set daily interval, and Drata will gather evidence from the latest runs of these commands when we run our daily compliance checks.

Like Policies, these Commands should be attached either directly to devices or to device groups containing every device you want to run compliance checks on.

You can create new Commands starting from here:

To enable us to query the results of these commands, you must use the following titles exactly as below:

  • DrataCollectorLinux


(Linux Shell Script)


if which ufw > /dev/null && ufw status | grep -q "Status: active"; then

graphics=`lspci | grep VGA | head -1`;

if which apt-config > /dev/null && apt-config dump APT::Periodic::Unattended-Upgrade | grep -q 'APT::Periodic::Unattended-Upgrade "1";'; then

echo "{"
echo " \"firewallEnabled\": $firewall,"
echo " \"macAddress\": null,"
echo " \"graphics\": \"$graphics\","
echo " \"autoUpdateEnabled\": $autoUpdate,"
echo " \"gateKeeperEnabled\": null,"
echo " \"fileVaultEnabled\": null,"
echo " \"winServicesList\": null"
echo "}"

Step 2. Configure JumpCloud API

In the next step, you will be setting up an API Token.

To locate your API Key:

  1. Go to the username drop down located in the top-right of the Console.

  2. Retrieve your API key from API Settings.

API Key Considerations

This API key is associated to the currently logged in administrator. Other admins will have different API keys.

In order to revoke access with the current API key, simply reset your API key. This will render all calls using the previous API key inaccessible.

Step 3. Connect JumpCloud MDM to Drata

1. Select "Connections" from the left side navigation menu.

2. Select the 'Available connections' tab and then search for 'JumpCloud MDM' to select the connect button for the JumpCloud MDM integration.

3. Enter the JumpCloud account details and click 'Save & Test Connection.'

Note: This is where you enter the API URL and API token created above in Step 2.

Step 4. Enable JumpCloud MDM and Verify Connection

In the Settings page, select 'Internal Security' to go to the Internal Security page.

Select 'Automated via JumpCloud MDM' and switch off 'Automated via Drata Agent' to disable the Drata agent.

Note: If both remain on, and the Drata agent is installed on an employee computer, the Drata agent will take precedence; meaning, employee compliance checks will come from the agent.

Your JumpCloud MDM setup is complete! Drata will fetch data from JumpCloud on a daily basis once Autopilot completes running.

Did this answer your question?