All technologies
JumpServer logo
Privileged access and dataCertified Technology Partner

JumpServer privileged access management (PAM)

PAM: administrators and external contractors reach servers and databases through JumpServer Enterprise, and sessions are recorded.

  • Installed on your own Linux servers
  • SSH, RDP, VNC, databases, Kubernetes
  • Session recordings and command logs
  • Automatic password rotation

Direct contact

We reply to sales enquiries within 24 hours. info@zerolayer.eu

What it does

JumpServer Enterprise is a PAM (privileged access management) system that you install on your own Linux servers, including as a high-availability cluster. Administrators and external contractors stop connecting directly to Linux and Windows servers, databases, Kubernetes or web consoles and go through JumpServer instead, in the browser or from a client. Passwords and SSH keys for those systems sit in an encrypted vault and are changed automatically, every session is recorded, and the commands typed go into a searchable log. Dangerous commands can be blocked or held for approval.

Terminal and desktop in the browser

You open SSH sessions and RDP desktops in the browser, with no plug-ins. You can also use the JumpServer client to reach servers over SSH and RDP and to connect to databases.

Servers, databases and Kubernetes

Linux and network devices over SSH, Windows over RDP, plus VNC, Telnet, MySQL, PostgreSQL, Oracle, SQL Server, Redis and MongoDB databases, Kubernetes pods and web consoles.

Password and SSH key vault

Passwords and SSH keys for server accounts are kept in an encrypted vault. Account discovery scans your servers and shows accounts nobody remembered.

Automatic password rotation

A task changes server account passwords immediately or on a schedule, randomly and to length and complexity rules, with an email notification.

Permissions to servers and accounts

Each person is granted specific servers and accounts, limited by IP address and login hours. Actions are recorded under their name, not under a shared root account.

Command blocking and approval

Rules written as command lists or regular expressions block dangerous commands, hold them until a named person decides, or just raise an alert.

SSH and RDP session recording

Sessions are recorded for playback in the browser. Each shows the commands typed and files transferred, and you can watch live SSH and RDP sessions and terminate them.

Time-limited access requests

Logging in or connecting to a chosen server can require an approved request (ticket). Access can be granted for a limited time only.

MFA, SSO and directory login

Login through LDAP/AD, SSO (OIDC, SAML2, OAuth2), CAS, RADIUS or passkey, with MFA by TOTP code or WebAuthn key.

When it fits

  • Problem

    External contractors log into production servers on shared passwords

    With JumpServer

    Each contractor gets named access to specific servers, and the shared passwords are changed and moved into the vault.

  • Problem

    Several administrators log into servers with the same root account

    With JumpServer

    Each one goes through JumpServer with their own account and MFA, so the recording and command log show exactly who typed what.

  • Problem

    After an outage, nobody knows what was done on the server

    With JumpServer

    You play back the session recording and search the commands typed, instead of piecing events together from memory.

  • Problem

    Someone could type a command on production that wipes data by mistake

    With JumpServer

    A filter rule blocks that command or holds it until a named person approves it.

  • Problem

    An employee leaves or a contract with an external company ends

    With JumpServer

    You disable one JumpServer account, and a password rotation task changes the server passwords that person saw.

How we deploy it

  1. Step 1:

    Map current access

    We establish who connects to what today and run account discovery on your servers, so we also find accounts nobody remembers.

  2. Step 2:

    Installation

    We install JumpServer Enterprise on your Linux servers, as a high-availability cluster where needed, so one server failing does not lock administrators out.

  3. Step 3:

    Permissions and vault

    We build the server and permission model, connect JumpServer to your directory, SSO and MFA, move passwords into the vault and change the ones that were shared around.

  4. Step 4:

    Close direct access

    Direct access is closed system by system. Command rules start by raising alerts only, and blocking is switched on once we know it will not get in the way of work.

  5. Step 5:

    Handover and support

    Your administrators get documentation and training on running the system, recordings and command logs, and our support stays available after go-live.

Let's talk
about security

Email or call us and tell us what you need: an architecture design, a tool rollout, SOC as a Service or a penetration test. Round-the-clock monitoring is part of SOC as a Service.