Bastion Host
What Is a Bastion Host?
A bastion host is a server placed at the boundary of a protected network to control administrative access to internal systems. Instead of allowing all internal servers to be accessible over the internet, an organization gives these connections through a specific bastion host machine. This one specific host takes on the responsibility of safeguarding many other servers and systems.
How Does a Bastion Host Work?
An administrator connects to the bastion host using an approved protocol, usually SSH or RDP. The host verifies login credentials. The administrator then initiates yet another connection to the internal server they need. That second connection depends on the network rules permitting traffic from the bastion host to the target machine. If those rules are too broad, the bastion host becomes a route to systems beyond the administrator’s actual responsibilities. Its security therefore depends on both access control and network configuration, not just the protection of the login itself.
Key Characteristics of Bastion Hosts
- Access to control area: Entry to the administrative area is routed via a known host instead of direct.
- Hardened system: Removal of unneeded software, services, and user accounts to minimize the attack surface.
- Limited connectivity: Firewall rules allow or deny who is allowed to connect from outside and, which internal hosts the host is permitted to access.
- Access records: Authentication logs and session records help administrators trace remote activity.
Benefits of Bastion Hosts
- Less public exposure: Internal servers remain without direct internet-facing management ports, reducing opportunities for unauthorized access.
- Centralized access control: Administrators manage an important part of remote access through one designated system.
- Simpler security reviews: Access records from the bastion host give security teams a central place to investigate administrative connections.
- Limited lateral access: Restricting the host’s network permissions reduces the number of internal systems reachable after a compromise.
Bastion Hosts in Cloud Computing
In a typical cloud architecture, the bastion host resides in a public subnet and the application servers are in private subnets. The administrator can connect to the bastion host and from there open up a separate session to a private instance (the private instance doesn’t require a public IP address in this case). Cloud firewall rules (like security groups) are used to control the sources that can reach the bastion host, and where the host can connect internally. Just having a server sitting in a public subnet isn’t sufficient.
Some balance exists. While the custodian does not expose individual private machines, it exposes itself as a crucial access point. An exploited weak password or an unpatched service on the bastion host could end up compromising the entire system. Some cloud providers also include managed access services that link administrators to private instances.