JumpCloud’s extensive support for credential management incorporates the industry’s most trusted approaches for both password and secure shell access to server infrastructure. Administrators can model the complexity of the passwords their organization requires, be alerted to impending expiries and brute force lockouts, and govern the credentials used for server access among teams of sysadmins.

Password Complexity

Establish the password policy convention your organization requires to balance security needs with employee convenience. Enforce length, capitalization, special characters, and more in the combinations you desire to deter hackers from their easiest means of gaining access to accounts: weak passwords.

Password Rotation

Enforce the cadence you require your employees to update their passwords. Employees and administrators alike are notified daily as their passwords are leading up to expiry to ensure no loss of access.

SSH Key Management

JumpCloud users can create and manage their own SSH keys within their User Portals for secure access to the server resources they need to login to. JumpCloud admins can see and revoke these keys at any time, while allowing them to be leveraged for Linux server access.

Brute Force Lock Out

Set the number of login attempts an account will tolerate before locking the account down on the system endpoint to deter brute force attacks from gaining access. Administrators and Users alike are instantly notified of these attempts to mitigate a potential security issue.


  • Set Minimum password Length: Set the minimum number of characters the password must be.
  • Set Password Complexity: Increase security by selecting various complexity settings including case and special characters.
  • Enforce Password Originality: Prevent the user from inserting their account username within the password.
  • Define Password Aging rules:
    • Define the number of passwords (up to 5) recently used before the user can reuse a password.
    • Set a number of days for when the password will expire and require the user to create a new password.
    • Provide a time frame during which the system will send the user a reminder email to change their password, as their current password will be expiring. The time frame is set in number of days before the date of expiry.
  • Allow SSH Password Login.
  • Establish SSH + Public Key Authentication requirements.
  • Administrative controls to view, edit or remove SSH keys of sysadmins.


  • Make it exponentially harder for hackers to crack your user’s passwords.
  • Create mechanisms to ensure that users are leveraging unique passwords for their business accounts versus personal accounts.
  • Improve security by ensuring your employees are utilizing passwords that meet or exceed your organization’s security requirement.
  • Allow your employees to completely self-manage their password creation and reset, while administrators govern the complexity.
  • See which user’s passwords fall out of compliance in a simple to use interface.


Check out our support documentation on Security Settings to learn more.