JumpCloud configuration hardening security checks
Vendor-recommended secure defaults, patch levels and housekeeping settings that drift as tenants grow and admins change.
On JumpCloud, Black Cat runs 3 checks in this area on every scan. Each one below lists its severity, how to fix it, and the compliance controls it satisfies where a control applies. See what access the JumpCloud connector needs.
Checks (3)
severity: high System SSH Password Authentication Enabled fix difficulty: medium #
Disable SSH password authentication on managed systems
- Open JumpCloud Admin Console > Devices and select the flagged system
- Disable "Allow SSH password authentication" and require public-key auth
- Verify users have SSH keys provisioned before enforcing
Satisfies: NIS2 Directive NIS2-21.e.4 DORA (SaaS Security) DORA-9.10
severity: high System SSH Root Login Enabled fix difficulty: easy #
Disable SSH root login on managed systems
- Open JumpCloud Admin Console > Devices and select the flagged system
- Disable "Allow SSH root login"
- Use sudo-based elevation for administrative tasks instead
Satisfies: NIS2 Directive NIS2-21.e.4 DORA (SaaS Security) DORA-9.10
severity: medium Dynamic User Group Without Restriction fix difficulty: medium #
Review dynamic user groups that auto-add members by query
- Open JumpCloud Admin Console > User Groups and select the dynamic group
- Confirm the membership query is scoped and intended
- Restrict over-broad queries that could auto-grant access
Satisfies: NIS2 Directive NIS2-21.e.4 DORA (SaaS Security) DORA-9.10