Main menu
Definition

Jump host

A jump host is a hardened server you connect through to reach systems on a protected network. Learn how jump hosts work, how they compare with bastion hosts, and how to use one with SSH and RDP.

DTDevolutions Team·November 12, 2026·3 min read

What is a jump host?

A jump host is a hardened server that administrators connect to first, and from which they open sessions to systems they can't reach directly. It acts as the single, controlled doorway between a trusted network and a protected one, such as a production network, a data center segment, or a customer environment.

How does a jump host work?

  1. Firewall rules allow admin traffic into the protected network only from the jump host.
  2. The administrator opens a session to the jump host, usually over RDP or SSH.
  3. From there, they connect onward to the target system.
  4. Because every privileged session passes through one machine, it can be hardened, monitored, and logged closely.

Jump host vs. bastion host vs. jump box

Term What it usually emphasizes
Jump host / jump server A stepping stone for admin sessions into a protected network.
Jump box The same idea, often a dedicated workstation or VM.
Bastion host A hardened, often internet-facing server built to withstand attack.

SSH and RDP through a jump host

OpenSSH supports jump hosts natively with the -J (ProxyJump) option, for example ssh -J admin@jump.example.com admin@10.0.0.20. To make it permanent, add a ProxyJump line for the target host in ~/.ssh/config.

For RDP, Remote Desktop Manager has a jump feature that opens the target session from inside an RDP session to the jump host. It talks to Devolutions Agent on the jump host, and Remote Desktop Manager on the jump host opens the final session. The jump host entry must be an RDP entry, Devolutions Agent needs its RDP Extension, and jumps don't bypass Microsoft's two-concurrent-session RDP licensing limit.

Follow the step-by-step setup in our documentation: Configure a jump host.

Why do jump hosts matter?

A jump host narrows the path into sensitive systems, but it is only as safe as the access to it. Harden and patch it, require multi-factor authentication, keep credentials off it by injecting them into sessions, log every session, and grant access just in time. Some teams replace a classic jump host with a gateway: Devolutions Gateway provides just-in-time access to resources in segmented networks without a traditional VPN.

Frequently asked questions

What is a jump host?

A jump host is a hardened server that administrators connect to first, and from which they open sessions to systems on a protected network that they can't reach directly.

What is the difference between a jump host and a bastion host?

The terms are often used interchangeably. Bastion host sometimes stresses the hardened, internet-facing role, while jump host stresses its use as a stepping stone for admin sessions.

How do I connect through a jump host with SSH?

With OpenSSH, use the -J (ProxyJump) option, for example ssh -J admin@jump.example.com admin@10.0.0.20, or set ProxyJump for the target host in your SSH config file.

Open sessions through a jump host from one place

Launch RDP and SSH sessions, jumps included, from a single remote connection manager.

Explore Remote Desktop Manager

Related terms

Privileged session

A temporary privileged access to critical assets.

Read now →

Remote connection management

Organizing and securely sharing remote connections among users.

Read now →

Credential injection

Secure input of credentials into a session without revealing them to the user.

Read now →