Both methods let an SSH client reach a remote host through an intermediate jump server. ProxyJump is the simpler modern option, using a direct jump specification in the client config or command line. ProxyCommand is older and more manual, using an explicit command to tunnel the connection through the bastion. For most practitioners, ProxyJump is easier to standardise.
How ProxyJump and ProxyCommand differ in practice
ProxyJump is the cleaner abstraction. It tells the SSH client to hop through one or more jump hosts using a built-in mechanism, so the bastion path is easy to read, reuse, and standardise across SSH key and certificate management patterns. ProxyCommand is lower-level and more flexible, because you define the exact command SSH should run to build the tunnel.
That difference matters when you are maintaining access at scale. ProxyJump usually produces simpler client configuration and fewer moving parts, while ProxyCommand remains useful when you need custom routing, compatibility with older clients, or extra logic around the connection path. In both cases, the bastion is still an intermediary trust boundary, not a control that removes the need for host hardening.
When to prefer one over the other
For most teams, ProxyJump is the default choice because it is easier to read, audit, and document in a shared SSH config. It reduces the chance of configuration drift, especially when operators need the same bastion path for many targets or when the jump chain is short and predictable. If your requirement is simply "connect via bastion," ProxyJump is usually the least error-prone option.
ProxyCommand is the better fit when the connection needs more than a straightforward hop. Common cases include conditional command execution, non-standard transports, compatibility with older OpenSSH behaviour, or environments where the bastion workflow is embedded inside an existing wrapper script. The trade-off is that the connection logic becomes less transparent and easier to misconfigure.
What this means for bastion security and operations
The SSH feature you choose does not change the core risk model of bastion access. A bastion is still a high-value choke point, so exposure depends more on key handling, host authentication, session logging, and who is allowed to use the path than on whether the client uses ProxyJump or ProxyCommand. A useful operational habit is to treat the jump host as part of the access control surface, not as a convenience detail.
ProxyJump can make standardisation easier, which helps when you want a single approved pattern for bastion use and SSH certificate management. ProxyCommand can still be perfectly valid, but teams should be deliberate about why they are carrying the extra complexity and whether the same outcome can be achieved with a simpler built-in jump specification.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 and CIS Controls v8 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | SSH bastion access depends on key and credential lifecycle control. |
| Recommendation — Manage SSH keys and related authenticators through controlled issuance, rotation, and revocation. | ||
| CIS Controls v8 | CIS-5 — Account Management | Bastion access is governed through account and key administration across jump paths. |
| Recommendation — Restrict and review accounts that can use bastion access paths. | ||
| ISO/IEC 27001:2022 | A.5.15 — Access Control | SSH jump-host design is an access-control decision about who may reach targets through a bastion. |
| Recommendation — Define and enforce approved remote-access paths through the bastion. | ||
Practitioner Guidance
What to verify: Confirm that the chosen method still preserves clear bastion ownership, host key verification, and a consistent audit trail. If operators cannot explain the connection path from client to target in one sentence, the configuration is usually too opaque.
Decision rule: Use ProxyJump for standard jump-host access unless you need custom connection logic, legacy compatibility, or a wrapper that ProxyJump cannot express cleanly. Reserve ProxyCommand for cases where the added flexibility is materially useful, not just familiar.
Common mistake: Treating the syntax choice as the security control. The real control points are who can reach the bastion, what keys or certificates they hold, and whether sessions are observable once they pass through the jump host.
Practitioner takeaway: Prefer the simplest SSH path that your environment can standardise, because readability and consistency make bastion access easier to govern than clever connection logic does.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 2, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org