Kandji¶
Device management (MDM). Device posture and enrollment events from your Kandji fleet.
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 device posture events: compliance state, on-device threats, and enrollment / management-state changes. That feed powers detections such as critical non-compliance, an on-device threat, MDM tampering (a device going unmanaged), an enrollment burst, and a stale / missing device.
It is read-only. SheerSight cannot push MDM commands, change policy, or wipe a device.
What you'll need¶
- A Kandji administrator who can create an API token.
- Your Kandji API host (region-specific, of the form
https://<subdomain>.api.kandji.io). - Your dedicated instance enrolled.
Create the read-only credential¶
- In Kandji, open Settings -> Access -> API Token and create a token (create a dedicated one for SheerSight so it can be rotated independently).
- Scope it to device / posture read only. It must not be able to send MDM commands or change policy.
- Copy the token, and note your API host (
https://<subdomain>.api.kandji.io).
Menu location
Kandji occasionally revises its settings layout. The token lives under the API area of Settings / Access. If your console differs, look for "API Token" under access settings.
Connect it in SheerSight¶
Self-serve connect is not live for Kandji 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 token | The token from step 1. |
Region host
Kandji's API host is specific to your tenant's region. Tell us your
https://<subdomain>.api.kandji.io host when you connect so the collector uses it.
Verify¶
Once we have enabled it and you have connected the card:
- The relayed credentials entry moves from pending to applied.
- The Kandji source badge moves from not connected to live.
- Device posture events begin appearing, and matching detections start firing.
Troubleshooting¶
- Authentication fails. Confirm the token is current and that the API host matches your tenant's region.
- No events. Confirm the token has device / posture read visibility.
What SheerSight can and cannot do¶
The token is read-only for device posture. SheerSight cannot push MDM commands, change compliance policy, remediate, or wipe a device. It only reads posture events.