devguard - Your Compliance Platform
PlatformSolutionsFrameworksDevelopersPricing
devguard

One workspace for your whole ISMS — Swiss-hosted, one control set, mapped to every framework you run.

All systems operational
Product
PlatformFeaturesSolutionsFrameworksPricing
Developers
API & CLIIntegrationsDocumentationChangelogSwiss hosting
Company
AboutBlogCompare
© 2026 devguard AG. All rights reserved.
Terms of servicePrivacy policySite noticeTrust centerLLM info
Swiss Made Software
Integrations · Identity

JumpCloud
compliance checks, automated

Read-only checks on JumpCloud confirm the directory is reachable and that the number of organization administrators stays within the bound you set.

The checks

What devguard checks in JumpCloud

2 read-only checks, run on a schedule. Each failure becomes a finding linked to a control — every check is listed, none are “coming soon”.

JumpCloud directory is reachable

Connectivity check: fails if the API key cannot read the system-users directory.

directory-reachable

info

Organization admin count is within the approved limit

Access-review check: fails if the number of JumpCloud organization administrators exceeds the approved maximum. The administrators listing is read in a single request bounded to 100 rows; because the approved maximum is far below that bound, any excess admin is seen and the check cannot pass falsely.

admin-count-limited

medium

Bring your current platform's test list — we'll map it against these checks, gap by gap

How it connects

Connected by you, scoped by you

Setup is minutes, not a migration project — and every step stays on your side

01

Create a read-only credential

Create the credential in JumpCloud with the minimum read scope, paste it into devguard, and the connection is live. The integration page in the product spells out the exact permissions.

02

Checks run on a schedule

The first run starts right after connecting, then repeats on a schedule. Results are timestamped, so your evidence has a history, not a snapshot.

03

Evidence lands on the control

Passing results attach as evidence to the controls they support; failures become findings you triage. When the audit comes, the proof is already connected.

Related

More from your stack

Open any page for its full check register.

Read-only, revocable, Swiss-hosted

You create and scope every credential yourself, and you can revoke it at any time. Checks only read; results and evidence are stored in Switzerland and stay exportable.

FAQ

Questions about JumpCloud

Is the JumpCloud access read-only?

Yes. The checks authenticate with a credential you create and scope yourself, and only ever read configuration. devguard holds no write access to JumpCloud and remediates nothing silently.

What happens when a check fails?

A failed check becomes a finding linked to the control it supports, with the evidence attached. You decide the treatment — nothing pages your engineers and nothing is auto-remediated.

Where do the results live?

Checks run from Swiss infrastructure, and results and evidence are stored in Switzerland. Everything is exportable — your evidence stays yours.

Connect JumpCloud and see the evidence land

20 minutes on how you run certification today. Bring your current test or control list and we'll map it against these checks — honestly, gap by gap.

Book a conversation
Book a conversation
Bitwarden
4 checks
Google Workspace
4 checks
Microsoft Entra ID
3 checks
Okta
4 checks
See all integrations
Book a conversation
Sign in
Start for free
Book a conversation
Start for free