Jump server

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-based tunneling became common, jump servers became the de facto method of access.

Jump servers are often placed between a secure zone and a DMZ to provide transparent management of devices on the DMZ once a management session has been established. 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.

A typical configuration is a hardened Unix (or Unix-like) 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 SSH port forwarding or an SSH-based 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.

A typical configuration is a Windows server running Remote Desktop Services that administrators connect to, this isolates the secure infrastructure from the configuration of the administrator's workstation.^[1] It is also possible to enable OpenSSH server on Windows 10 (build 1809 and later) and Windows Server editions 2019 & 2022.^[2]

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

• Properly subnetting / segmenting the network,^[4] and securing VLANs using a firewall^[5] or router.
• Using higher security authentication, such as multi-factor authentication.^[5]
• Keeping the operating system and software on the jump server up to date.^[6]
• Using ACLs to restrict access.^[7]
• Not allowing outbound access to the rest of the internet from the jump server.^[8]
• Restricting which programs can be run on the jump server.^[9]
• Enabling strong logging for monitoring and alerting of suspicious activity.^[6]

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

In 2015, a compromised jump server allowed attackers access to over 21.5 million records in one of the largest breaches of government data in the history of the United States.^[11]

• Bastion host
• Proxy server

• Wimmer, Peter Kai. "Secure Network Zones" (PDF). ATSEC Information Security. Archived from the original (PDF) on 2016-03-08.
• Mathis, Roland (2004-09-20). "Installation of a Secure User-Chrooted SSH Jumphost" (PDF). GIAC. Retrieved 2019-06-12.