Jump server: Difference between revisions
add hatnote |
change to redirect hatnote |
||
| Line 1: | Line 1: | ||
{{ |
{{Redirect|Jump box|boxes used in jumping exercises|Plyometrics}} |
||
{{short description|A computer on a network used to access a separate security zone}} |
{{short description|A computer on a network used to access a separate security zone}} |
||
A '''jump server''', '''jump host''' or '''jumpbox''' is a computer on a [[Computer network|network]] used to access and manage devices in a separate security zone. The most common example is managing a host in a [[DMZ (computing)|DMZ]] from trusted networks or computers. |
A '''jump server''', '''jump host''' or '''jumpbox''' is a computer on a [[Computer network|network]] used to access and manage devices in a separate security zone. The most common example is managing a host in a [[DMZ (computing)|DMZ]] from trusted networks or computers. |
||
Revision as of 17:36, 29 August 2019
A jump server, jump host or jumpbox is a computer on a network used to access and manage devices in a separate security zone. The most common example is managing a host in a DMZ from trusted networks or computers.
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 should be tightly controlled and monitored.[citation needed]
Background
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 tunneling became common, jump servers became the de facto method of access.
Implementation
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. 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.
Unix
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 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.
Windows
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]
Security risks
A jump server is a potential risk in a network's design.[2] 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.[3]
See also
References
- ^ "Implementing Secure Administrative Hosts". docs.microsoft.com.
- ^ Grimes, Roger A. (July 26, 2017). "'Jump boxes' and SAWs improve security, if you set them up right". CSO Online.
- ^ Bhargava, Rajat (January 10, 2014). "Is the Jump Box Obsolete?". O'Reilly Radar.
External links
- Wimmer, Peter Kai. "Secure Network Zones" (PDF). ATSEC Information Security. Archived from the original (PDF) on 2016-03-08.
{{cite web}}: Unknown parameter|dead-url=ignored (|url-status=suggested) (help) - Mathis, Roland (2004-09-20). "Installation of a Secure User-Chrooted SSH Jumphost" (PDF). GIAC. Retrieved 2019-06-12.