The login screen faded, and with it the thought of ever giving out blanket SSH access again. Security doesn’t have to mean giving someone the keys to everything. Not when you can control access at the command level. Not when you can replace the old bastion host model with something sharper, faster, safer.
Bastion hosts were once the default choice to secure remote access. They put a server in the middle, forced traffic through it, and kept logs. But they also created friction, overhead, and a broad attack surface. Granting full shell access often gave more power than was needed. Command whitelisting changes the game by limiting actions to exactly what’s required—nothing more.
An alternative to the bastion host approach removes the jump box, stops SSH tunnels from becoming blind spots, and enforces least privilege from the first packet. Every command runs through policy. Every action is recorded. You decide who runs what, and when. Users never touch a shell they don’t need. Attackers never pivot to a system they can’t reach.