Two consultants mapping SSH gateway routes with thread on a network drawing — A route record should explain why a hop exists, not merely show that it exists.

What the route atlas records

Origin: Workstation group, network zone, and accountable operator.
Gateway: Jump-host purpose, reachability, authentication boundary, and support owner.
Destination: Host role, approved protocol, port, and expected service behavior.
Forward: Local, remote, or dynamic forwarding intent plus the application that consumes it.

Official behavior, organizational choices

Official MobaXterm documentation describes SSH gateways and a graphical SSH tunneling tool. Those capabilities do not determine which route your organization should authorize. Our work separates product capability from infrastructure policy.

Review sequence

Identify direct and gateway-mediated paths.
Verify DNS, ports, identity dependencies, and system ownership.
Bench-test representative sessions with authorized personnel.
Record expected failures and escalation contacts.
Set a date and owner for the next route review.