Identity
Kill JumpCloud security risks.
Saasment tests user state, admin roles, MFA, and device-to-user bindings in JumpCloud.
The kill
Drop the role. Require MFA. Unbind the device. Revoke the key.
The test uses the admin API. The kill is a role, MFA, or key change.
Connect in minutes
An admin creates an API key.
Five risks the test looks for
- A suspended user still has an admin role.
- MFA is not required for admins.
- A command-runner role is broader than the job.
- A departed user is still bound to a device.
- An API key belongs to a former admin.
What does Saasment test in JumpCloud?
Saasment tests user state, admin roles, MFA, and device-to-user bindings in JumpCloud.
What does the kill do in JumpCloud?
Drop the role. Require MFA. Unbind the device. Revoke the key. The test uses the admin API. The kill is a role, MFA, or key change.
Will a JumpCloud test break the account?
The test is scoped to JumpCloud. The kill waits until the test has proved the risk. You can roll that kill back. The log stays.
How do I connect JumpCloud?
An admin creates an API key. It takes minutes. There is no call.