Add the JumpCloud Agent to an Allow List

Next-generation antivirus products aren't just relying on signature and heuristic-based detection anymore; they are using some focused artificial intelligence to identify unusual behaviors.

Because the JumpCloud agent executes background tasks that could be flagged as unusual, this could be flagged by your antivirus vendor; however, this is how the agent works by design, and is not malicious. Antivirus software may flag the JumpCloud agent at any time, even if it hasn’t happened previously. 

It's recommended to add the JumpCloud installation folder as well as the JumpCloud agent application for Mac, Windows, and Linux systems to an allowlist. If the JumpCloud agent or scripts run by the agent are flagged as suspicious after you have added the JumpCloud agent to your allowlist, we recommend contacting your antivirus vendor.

Note:

If you are using JumpCloud Remote Assist, see Understanding the Remote Assist Agent for endpoint security exclusions.

Finding the Allowlist Folder and Application

Windows:

  • C:\Program Files\JumpCloud
    • jumpcloud-agent.exe and jumpcloud-agent-updater.exe in the above directory
  • C:\Program Files\JumpCloud\jumpcloud-user-agent
    • jumpcloud-user-agent.exe in the above directory

Mac:

  • /opt/jc
  • /opt/jc_user_ro
  • /Library/LaunchDaemons
    • com.jumpcloud.darwin-agent​.plist in the above directory
  • /Library/LaunchAgents
    • com.jumpcloud.user-agent.plist in the above directory

Linux:

  • /opt/jc
  • /opt/jc_user_ro
  • /etc/pam.d/jcprotect
  • /etc/pam.d/jcprotect-prompt
  • (64-bit only) /lib/x86_64-linux-gnu/security/pam_jc_push_mfa.so
  • (64-bit only) /lib/x86_64-linux-gnu/security/pam_jc_session_check.so
  • (64-bit only) /lib/x86_64-linux-gnu/security/jc_localgrpc.so
  • (32-bit only) /lib/i386-linux-gnu/security/pam_jc_push_mfa.so
  • (32-bit only) /lib/i386-linux-gnu/security/pam_jc_session_check.so
  • (32-bit only) /lib/i386-linux-gnu/security/jc_localgrpc.so

Understanding JumpCloud’s Allowlisted Login Items

With macOS 13 Ventura, end users have the ability to switch off persistent software, such as the JumpCloud Agent. Ventura also introduces the concept of allowlisted Login Items, which is a list of third-party apps that users are allowed to log into with Mobile Device Management (MDM). 

JumpCloud uses an allowlist so that these Login Items can use JumpCloud’s MDM:

  • Apple’s code-signing identity for apps signed by our team ID. For example, N985MXSH86.
  • JumpCloud Launch Daemons and Launch Agents that are labeled as com.jumpcloud. You can see what is running on your device by reviewing the /Library/LaunchDaemons directory and the /Library/LaunchAgents directory. For example:

com.jumpcloud.agent-updater.plist
com.jumpcloud.darwin-agent.plist
com.jumpcloud.macos-update-notifications.plist
com.jumpcloud.Nudge.plist
com.jumpcloud.jcagent-tray.plist
com.jumpcloud.user-agent.plist

If you are not using JumpCloud’s MDM, but you are using another MDM vendor, you can use JumpCloud’s Mac Manged Login Items Policy to allowlist Login Items for your macOS devices. For more detail and instructions, see Create a Mac Managed Login Items Policy.

Still Have Questions?

If you cannot find an answer to your question in our FAQ, you can always contact us.

Submit a Case