Jump server

From Wikipedia, the free encyclopedia
  (Redirected from Jump Server)
Jump to: navigation, search

A jump server or jump host or jumpbox is a special-purpose computer on a network typically used to manage devices in a separate security zone. The most common example is managing a host in a DMZ from trusted networks or computers.


In the 1990s when co-location facilities became more common there was a need to provide access between dissimilar security zones. The jump server concept emerged to meet this need. The jump server would span the two networks and typically be used in conjunction with a proxy service such as SOCKS to provide access from an administrative desktop to the managed device. As SSH tunnelling became common it became the de facto method of access.


A jump server is a hardened and monitored device that spans two dissimilar security zones and provides a controlled means of access between them. User access is tightly controlled and monitored.


Jump servers are typically placed between a secure zone and a DMZ to provide transparent management of devices on the DMZ once a management session has been established.

Typical implementations[edit]

A typical configuration is a hardened Unix machine configured with SSH and a local firewall. An administrator connects to a target machine in the DMZ by making an SSH connection from the administrator's personal computer to the jump server and then using SSH forwarding to access the target machine.

Using an SSH tunnel to the target host allows the use of insecure protocols to manage servers without creating special firewall rules or exposing the traffic on the inside network.

The jump server acts as a single audit point for traffic and also a single place where user accounts can be managed. A prospective administrator must log into the jump server in order to gain access to the DMZ assets and all access can be logged for later audit.

Security risks[edit]

A jump server is a potential risk in a network's design.[1] There are several ways of improving the security of the jump server, including:

  • Reducing the subnet size (increasing the number of subnets), and securing those VLANs using a firewall or router.
  • Using higher security authentication, such as Multi-factor authentication.
  • Keeping the operating system and software on the jump server up to date.
  • Using ACLs to restrict access to only the people that require it.
  • Do not allow outbound access to the rest of the internet from the jump server.
  • Restrict which programs can be run on the jump server.
  • Enable strong logging.

With the high level of risk that a jump server can represent, a VPN may be a suitable and higher security replacement.[2]

See also[edit]