Field guide 02

Draw the SSH path in plain language.

MobaXterm supports SSH sessions, private-key selection, gateways, and a graphical tunnel builder. A route note explains how your organization intends to use those functions.

Hands annotating a printed SSH route beside a laptop — Never include a private key or password in the route note.

Five statements to write down

01
Origin. The managed Windows endpoint and network prerequisite.
02
Gateway. The jump host, if any, and its operational owner.
03
Destination. The final host, port, service purpose, and responsible team.
04
Authentication. Approved method and key-issuance or identity process—never secret material.
05
Verification. What the operator checks before work begins and after it ends.

Tunnels need purpose and lifetime

Official documentation describes local port forwarding through the tunneling tool. Record the local bind, remote destination, business purpose, expected lifetime, and change owner. A tunnel should not outlive the task simply because its profile remains convenient.

Host-key warnings are decision points

A changed host identity is not a prompt to click through. Your note should direct the operator to the authorized source used to verify the new host key and the escalation path when that source is unavailable.

Client settings are only part of the route

Server SSH configuration, account authorization, key lifecycle, endpoint protection, VPN rules, and network segmentation remain outside the client. Review them with their owners.