JumpCloud Security Review
JumpCloud access comes down to the admin roles, groups and conditional access policies your team set up. We review what your admins actually configured, not JumpCloud’s platform. CREST-certified testers, fixed price from £3,290 for a 2-day single-tenant scope, quoted within 24 hours.
- Unlimited retesting
- Unlimited pre-retesting
- No hidden fees
“I would highly recommend EJN Labs to any organisation seeking reliable, detailed, and well-managed penetration testing services, particularly for government or enterprise-level projects.”
“There wasn’t another company we could find that could deliver what we needed in the timeframe we needed. The client loved it, and we got instant ROI from the engagement.”
JumpCloud ships nine built-in admin roles, from Super Admin to Read Only, each with its own reach into users, devices, commands and billing.
A JumpCloud tenant is only as secure as the roles, policies and commands your admins have configured
JumpCloud’s own documentation lists nine built-in admin roles, from an Administrator with Billing account, which JumpCloud itself flags as a Super Admin holding every privilege in the tenant, down to a Read Only account that can view but never change anything. Which of those roles your admins actually hold, how many people carry the top one, and whether a Command Runner or Help Desk account has drifted past its documented scope is a decision your organisation made, not a JumpCloud default.
Access to the User Portal and every SSO application is controlled by conditional access policies built from device, network, location and operating system conditions, and JumpCloud sets out a fixed precedence: a policy set to deny access always overrides one that allows access with or without MFA. A policy written to relax MFA for a trusted network, or a device condition scoped wider than intended, changes what every user behind it can reach without a single line of code changing.
We test the tenant you actually run: the roles assigned, the groups and conditional access policies built from them, the commands your admins can push to devices, and the directory integrations that connect Microsoft 365, Google Workspace or Active Directory into JumpCloud. We never test JumpCloud’s own platform, in the same way we test client configuration on Intune-managed devices rather than Intune itself.
SCOPE
What we review in a JumpCloud tenant
Admin Roles and Admin MFA
JumpCloud ships nine built-in admin roles, from Administrator with Billing, which JumpCloud itself flags as a Super Admin with every privilege in the tenant, down to Read Only, Billing Only and Asset Manager accounts that can view but not change resources. An admin’s MFA is not separate from the platform: creating an admin from an existing user makes the Admin Portal login inherit whichever MFA factors that user has enrolled, from TOTP to JumpCloud Protect push or a hardware security key. We test how many accounts hold Administrator with Billing, whether every admin login is actually covered by an enrolled MFA factor, and whether a Command Runner or Help Desk account can reach further than its documented scope.
User Groups and Device Groups
Every meaningful grant in JumpCloud, an SSO application, a RADIUS or LDAP resource, a policy or a Command, is bound to a user group or a device group rather than to an individual account, and creating, editing or deleting either type of group is a privilege reserved for the higher admin roles. We test which groups exist, what each one is actually bound to, and whether a group built for a single project, migration or contractor engagement still grants live access nobody has reviewed since.
Conditional Access Policies
A JumpCloud conditional access policy combines device management, disk encryption, IP address, location and operating system conditions against the User Portal, SSO applications or LDAP applications, and JumpCloud is explicit about precedence: a policy set to deny access always overrides one that allows access with or without MFA, and any user not covered by a specific policy falls back to the Default Access Policies. We test what each policy actually does against what it was designed to do, and look for a policy that unintentionally relaxes MFA for a network, device type or location wider than the business intended.
MFA Enforcement for Users
MFA factor types are enabled organisation-wide from the Admin Portal’s MFA Configuration page, and enforcement for standard users is then set through access policies on the User Portal and SSO applications rather than switched on account by account. We test whether MFA is actually enforced everywhere it is meant to be, which factor types are permitted, and what a user without an enrolled factor can still reach during the enrolment and password-reset window JumpCloud provides.
SSO Application Configuration and Access
JumpCloud connects SSO applications over SAML 2.0 or OpenID Connect from a catalogue of pre-built connectors or a custom connector, and JumpCloud is explicit that Just-in-Time provisioning is only available on SAML apps, never OIDC. Whichever protocol is used, a user group only reaches an application once an admin explicitly authorises that group’s access to it, whether provisioning runs through JIT or manually. We test which users and groups are actually authorised against each application, whether JIT’s attribute mapping grants a role the business did not intend, and whether a disconnected or legacy application connector still holds live user or group assignments.
Device Policies and Commands
Commands run PowerShell, Bash or Shell scripts across one or more devices or device groups in parallel, deploying files, installing software or running maintenance, with full stdout, stderr and exit-code auditing of every run; on Windows, commands execute as the NT AUTHORITY\SYSTEM account unless a specific template is used to run in the signed-in user’s context, and a Command Runner account can only run the commands it has explicitly been given access to. We test which admins and Command Runner accounts can trigger which commands against which device groups, and whether a scheduled or templated command carries more privilege than the task it performs needs.
Password Policies
JumpCloud’s password settings, length, complexity, originality, aging and lockout rules, apply across the whole organisation, and the single JumpCloud password they govern controls access not just to the JumpCloud account itself but to every bound resource, including computers and SSO applications. We test the configured policy against your own security standard, whether it is actually enforced for every user rather than a legacy subset, and what a single compromised JumpCloud password can reach across your devices and connected applications.
Directory Integrations with Microsoft 365 and Google Workspace
JumpCloud’s Microsoft 365 directory integration lets you manage M365 users from the JumpCloud Admin Portal, syncing an M365 password to the JumpCloud password the first time a user signs in to their JumpCloud User Portal, and the Google Workspace and Active Directory integrations sync users, groups and passwords in the same direction-dependent way. We test which directory integration is configured, in which sync direction, whether an account disabled in the source directory is actually disabled in JumpCloud, and whether a synced group carries more JumpCloud access than the source directory group was meant to grant.
API Keys and Service Accounts
API access is disabled for every admin by default, and only an Administrator with Billing can turn it on for another admin; once enabled, each admin’s personal key is generated from My API Key in the Admin Portal, with an expiration you set to 30, 60, 90 or up to 365 custom days, or to no expiration for accounts created before 15 July 2024. JumpCloud’s own best-practice guidance recommends rotating that key at least annually, and a rotated key is invalidated immediately, while Service Accounts let an authorised admin issue a separate key scoped to one integration instead of relying on a personal admin key. We test which admins have API access enabled, whether any key still has no expiration set, and what a leaked key can actually read or change against the tenant.
Lifecycle Automation: Onboarding, Offboarding and Suspension
A new starter gets access the moment they are added to the groups, applications and directory integrations that grant it, and suspending a leaver’s account immediately revokes access to every JumpCloud-provided resource; a suspended account cannot unlock itself or reset its own password, and only an admin can reactivate it. Where JumpCloud is synced with Active Directory, disabling or deleting the source account is designed to carry that same suspension or deletion through to JumpCloud and every resource bound to it. We test what a suspended or deleted account can still reach immediately after the change, whether every downstream application and directory actually loses access on the same timeline, and whether a leaver’s device retains a cached credential or an active session.
OUR PROCESS
JumpCloud Security Review: From Scope to Attestation
Scope and Access
We agree which JumpCloud organisation, admin roles and directory integrations are in scope, plus at least one login for each distinct role and privilege tier you use.
Role, Group and Policy Mapping
We map every admin role, user group, device group and conditional access policy against the access it actually grants, alongside your current SSO application and directory integration configuration.
Manual Testing
A CREST-certified tester manually tests admin role boundaries, conditional access policy precedence, MFA enforcement, Commands access and API key exposure, chaining findings where they compound.
Attestation and Retest
You get a technical report with CVSS scores and reproduction steps, a walkthrough call, a free retest once fixes are deployed, and an attestation letter for auditors.
CREDENTIALS
Verified Accreditations Auditors Accept
Every credential below is independently verifiable. UK procurement teams, FCA supervisors, ISO 27001 / SOC 2 auditors, and cyber insurance underwriters all recognise these standards.
GET YOUR QUOTE
Get a CREST JumpCloud pen test quote in 24 hours
A fixed-price quote back in one business day, from a named CREST assessor. No sales pipeline, no chasing.
- CREST and IASME accredited. Testing your auditors and clients already recognise.
- Fast-track testing within 24 hours where required. Free retest of every fix included.
- Live findings via your client portal, not a four-week PDF.
- Fixed price from £3,500 for a single-role, single-app scope, agreed up front. Most engagements run £5,000 and up. No day-rate surprises.
Dan WilcocksonFounder, CelloriUnder NDA Further named references available on a scoping call.
- We reply within one business day with a fixed-price quote from a named CREST assessor.
- You approve the scope and we book a start date, usually within 24 hours.
- Live findings land in your client portal as we test, with a free retest of every fix.
Get your fixed pen test quote in 24 hours
Quote request received
We will reply within one business day with your fixed-price quote from a named CREST assessor.
Your data stays with us. No newsletter signup.
or book a 20-min scoping call first
We reply within one business day. Your data stays with us. No newsletter signup.
COMPLIANCE READY
Reports Mapped to Every Framework
Findings are written so your team can reference the report against each framework without translation work.
ISO 27001:2022
Annex A.8.8 management of technical vulnerabilities plus A.5.15-5.18 and A.8.2-8.5 access control validation.
SOC 2 Type I & II
CC6 logical access, CC7 system operations, CC8 change management evidence.
PCI DSS
Requirement 11.4 application penetration testing across cardholder data environments, including ecommerce penetration testing for online retail platforms.
FCA SYSC
SYSC 4.1.1R, 6.1.1R, 13 mapped to each finding for FCA-regulated firms.
UK GDPR
Article 32 effectiveness testing, customer-data security controls, ICO-acceptable evidence.
Cyber Essentials Plus
Direct certification through our IASME body status, single-vendor delivery.
PRICING
Transparent JumpCloud Security Review Pricing
Pricing depends on the number of roles, integrations and environments in scope. See our pricing page for how we quote.
2 to 3 testing days
Single user role, basic CRUD application, marketing website with auth. Around 5 working days from kickoff to report.
Get a fixed quote3 to 5 testing days
Multi-role SaaS, business application with payment integration. Around 8 to 12 working days from kickoff to report.
Get a fixed quote5 to 7 testing days
Multi-tenant platform, complex authorisation matrix, integration-heavy applications. Around 15 to 20 working days from kickoff to report.
Get a fixed quoteSECTORS
Sectors We Test JumpCloud For
Sector-specific scoping for regulated UK organisations.
Fintech & FCA-Regulated
FCA SYSC, Open Banking FAPI 1.0, PSD2 SCA, payment-flow scrutiny, KYC/AML testing.
Fintech sector pageSaaS Companies
SOC 2 Type I & II evidence, multi-tenant boundaries, role escalation, customer-tenant isolation.
SaaS sector pageLaw Firms
SRA Cyber Standard, privileged data, conveyancing fraud defence, partner-tier procurement.
Law firm sector pageHealthcare
NHS DTAC, DSP Toolkit v6, UK GDPR Article 32, EHR systems, telehealth platforms.
Healthcare sector pageInsurance
FCA / PRA Operational Resilience, cyber underwriting, claims data, broker portals.
Insurance sector pagePublic Sector
CCS / G-Cloud framework, NCSC-aligned, citizen-facing services, PSN-compliance scrutiny.
Public sector pageWHY EJN LABS
What You Get From JumpCloud Security Review
Six concrete differentiators competitors don’t all match.
CREST-Certified Testers, Verifiable
Every test by a CREST-certified pen tester (CRT, CCT APP, CCT INF where applicable). Verify our company status at crest-approved.org.
24-Hour Startup, Where Required
From signed scope to active testing in a single business day for incident response, audit deadlines, or regulator-driven timelines.
Live Findings, Not 4-Week PDFs
Critical issues reported during testing through your client portal. Your team remediates while testing continues.
Audit-Ready Reports
Executive summary plus full technical report with CVSS scores and explicit framework mappings (ISO 27001, SOC 2, PCI DSS, FCA SYSC).
Free Retests, Standard
Verify remediation of every finding before close-out. Letter of attestation for audit submission included. Most competitors charge £1,500-£3,000 per retest.
UK-Based CREST Testers
Every engagement performed by vetted, UK-based CREST-certified testers, matched to your needs, security clearance, and compliance scope.
FAQ
Frequently Asked
What access do you need to test our JumpCloud tenant?
We need at least one account for each distinct admin role in use, ideally a Read Only or Manager account rather than an Administrator with Billing login, plus a small number of standard user accounts covering different groups and applications. Read access to your current admin roles, conditional access policies and directory integrations speeds up scoping, but is not required to start.
Will testing touch our live data?
Testing focuses on roles, groups, conditional access policies, commands, password settings and directory sync configuration, rather than the content of user mailboxes or files held in connected applications. Where proving a finding needs a test account or a sample command, we agree the exact scope with you first and remove anything we create once testing is complete.
Is this hosted on our infrastructure or JumpCloud’s?
JumpCloud is a cloud directory platform, so there is nothing for you to host. The engagement is scoped to the tenant configuration you control, admin roles, groups, conditional access policies, commands and directory integrations, not to JumpCloud’s own platform.
How long does a JumpCloud security review take?
A single tenant with a typical set of admin roles, SSO applications and one directory integration sits in our 2-day single-tenant scope, with a report usually landing around 5 working days after kickoff. A tenant running several directory integrations, a large device fleet under Commands, or more than a handful of conditional access policies extends that scope.
What is out of scope for a single-tenant review?
Testing JumpCloud’s own platform, infrastructure or agent software is never in scope, and we do not run denial-of-service testing against any JumpCloud service. A connected application that JumpCloud provides SSO into is scoped and quoted as its own engagement rather than bundled into the tenant review.
Does JumpCloud have a customer penetration-testing policy we need to follow?
JumpCloud publishes a Vulnerability Disclosure Policy covering its own platform, agent and sync endpoints, and its terms of service prohibit unauthorised penetration testing of that platform. That policy is written for researchers testing JumpCloud’s infrastructure, not for a customer reviewing their own tenant’s configuration, so we confirm JumpCloud’s current terms and any account-specific conditions during scoping.
Do you need our source code or admin access?
No. There is no source code in a JumpCloud tenant. We test with the role accounts and access you provide, and we do not need standing Administrator with Billing access beyond what is needed to verify a specific finding during the engagement.
Are your testers CREST certified?
Yes. Every JumpCloud engagement is carried out by UK-based, CREST-certified testers, and your report and attestation letter are recognised by auditors and insurers accordingly.
20+ CREST-accredited testing services in one place
Web, mobile, API, cloud, AI, infrastructure, red team. Pick the test that fits your environment.
Get a fixed price for your JumpCloud tenant
JumpCloud access comes down to the admin roles, groups and conditional access policies your team set up. We review what your admins actually configured, not JumpCloud’s platform. CREST-certified testers, fixed price from £3,290 for a 2-day single-tenant scope, quoted within 24 hours.
