Jump host

How it works

The client proxies the SFTP channel through the jump host. Keys for both hops are required. A file copied to the jump host and left there is a second copy you did not inventory.

An admin pulls a 2 GB log from a private host via a bastion. The command streams through. A previous habit of copying to the bastion disk left logs on a shared admin box. They stop staging there.

How it differs

A jump host is not the file server. It should not store the payload.

A jump host open to the Internet with password login is a front door.

Use keys and restrict source addresses.

On the ticket

• The practical close is a log line: time, actor, byte count, result.
• Without that line the transfer is a story.
• With it, the next person can see whether this door did what the ticket claimed.
• If the path is shared, say so in the partner profile so a later change does not silently pick a different limit, key, or region.
• On a real ticket, write down the door, the byte count, and the clock.
• For jump host, that means naming the host or bucket, the expected size, and the time the other side must have a complete file.
• A progress bar is not that record.
• A 200 response that arrives before the complete call is not that record.
• If a retry is allowed, say how many and whether it resumes.
• If a person must approve the send, name the person.
• Partners who receive jump host files should match on hash or size before they import.
• A same-length corrupt file passes a size check and fails a hash.
• Keep the published hash off the only channel an attacker can edit, or treat it as a corruption check rather than a substitution check.
• When the path changes, new key, new region, new cap, update the profile the same day so the next run does not use a stale limit.