They woke up to find their bastion host had been breached.
The logs were incomplete. The audit trail was gone. The incident report read like a silent crime scene. What was supposed to protect them had become the weakest link. That morning, the team agreed: never again.
For years, bastion hosts have been the standard gateway into private infrastructure. They’re familiar, simple, and trusted. But they also create a single point of failure, carry heavy maintenance overhead, and require constant patching. Their attack surface is well-known. Their credentials, if stolen, grant direct access to production. In a remote-first, cloud-native world, the bastion model is fragile.
A secure future means removing permanent network entry points. It means adopting ephemeral, on-demand access with full visibility and governance coded into the deployment process. Security must be provisioned and revoked automatically, not left to manual steps. This is where the idea of Bastion Host Replacement as Security-as-Code comes in.
Security-as-Code treats access control, authentication rules, and authorization policies as part of your infrastructure definition. It integrates with CI/CD pipelines, IaC tools, and identity providers. There is no static tunnel or server always listening. Session-based access spins up when needed, tied to user identity, logged with every command, and torn down right after use.