JumpCloud¶
Device management (MDM) and identity. Directory and device posture events from JumpCloud.
Status: available on request - self-serve connect is not live yet
The collector and detections for this source are built and run in our lab, but switching it on from the console is not live yet, so connecting it there will not start collection. Ask for it through Integrate -> Request an integration, or email support@sheersafe.com, and we enable it on your dedicated instance. The steps below are accurate, so a credential you create now is the one it will use.
What SheerSight reads¶
SheerSight reads two JumpCloud feeds:
- System Insights (device posture), and
- Directory Insights (directory and SSO events).
That feed powers detections such as critical non-compliance, an on-device threat, MDM tampering, an enrollment burst, and a stale / missing device.
It is read-only. SheerSight cannot modify directory objects or push commands.
What you'll need¶
- A JumpCloud administrator who can create an API key.
- Your dedicated instance enrolled.
Create the read-only credential¶
- In the JumpCloud admin console, open your account / API settings and create an API key (create a dedicated one for SheerSight).
- Ensure the key can read System Insights and Directory Insights, and nothing more. It must not be able to modify directory objects or push commands.
- Copy the API key.
Least privilege
Read on the two Insights surfaces is all that is needed. The key cannot create, change, or delete directory objects, and it cannot run commands.
Connect it in SheerSight¶
Self-serve connect is not live for JumpCloud yet. Ask us to enable it through Integrate -> Request an integration. Once it is on for your instance, you paste these values on its card in Integrate -> Sources and press Connect, exactly as for the live sources - the secret is encrypted in your browser and we never see it:
| Field | Value |
|---|---|
| API key | The key from step 1. |
Verify¶
Once we have enabled it and you have connected the card:
- The relayed credentials entry moves from pending to applied.
- The JumpCloud source badge moves from not connected to live.
- System Insights and Directory Insights events begin appearing, and matching detections start firing.
Troubleshooting¶
- Some events missing. SheerSight reads both System Insights and Directory Insights; confirm the key can read both.
- Authentication fails. Regenerate the key and reconnect.
What SheerSight can and cannot do¶
The key is read-only for the two Insights surfaces. SheerSight cannot modify directory objects, change policy, or push commands. It only reads posture and directory events.