Home / Knowledge hub / Bastion host
Knowledge hub
Bastion host
A single hardened server that is the only way in for administrators.
What it means
A bastion host is a server placed at the edge of a private network whose only job is to let administrators in. Everyone who needs to reach internal machines goes through it, and the internal machines accept connections from nothing else.
Because there is one entrance, you can harden it heavily, watch it closely and log everything that passes through. It runs almost nothing else. The idea is to guard a single door well rather than leave many doors lightly guarded.
Why it matters
Without one, each internal server may expose its own admin port to the internet, such as SSH or remote desktop. Automated scanners find those within hours, and every extra open port is another password to guess or another unpatched service.
A bastion also gives you a clear record of who reached what and when, which helps with audit trails and with proving least privilege. If it is poorly kept, though, it becomes a single high-value target, because it leads everywhere.
How it shows up
You meet it as the jump server in a cloud network: sit in a public subnet, allow admin connections only from known addresses, and forward onwards to private machines. Many teams now use managed session services instead, which remove the always-on public server.
The usual faults are shared accounts, password sign-in instead of keys, stale software, wide-open source address ranges and no multi-factor authentication. Also check that internal servers truly refuse direct admin connections, and that logs from the bastion are kept elsewhere.
Questions people ask
Bastion host, answered
Is a bastion host the same as a VPN?
No. A VPN puts your device onto the private network. A bastion is a single server you connect to and then hop from. Some teams use both, others pick one.
Is a bastion host still needed in the cloud?
Often not in its classic form. Providers offer session managers that give admin access without an open inbound port. The goal, one controlled and logged entrance, stays the same.
What should a bastion host run?
As little as possible. No web apps, no shared tools, no developer files. Keep it patched, restrict who can sign in, and ship its logs off the machine.
Should the bastion be in a public subnet?
The classic design says yes, so administrators can reach it. If you do that, limit inbound access to known addresses and require keys plus a second factor.
What is the biggest risk?
Compromise of the bastion itself, since it is trusted by everything behind it. Treat its access as the most sensitive access you have.
Sources
Where this comes from
Related
Terms that sit next to this one
Virtual private cloud
A private, isolated network space inside a public cloud account.
Privileged access management
Tight control and recording of accounts that hold powerful admin rights.
Just-in-time access
Granting elevated access only when needed, and removing it soon after.
VPN
An encrypted tunnel that links a device or office network to another network.
Least privilege
Giving every person and service the minimum access the job requires.
Is there only one way in?
We test what an outsider can reach on your application and report only what we exploited, with the evidence. Ask us to run it on one of your applications.
Or start with a $199 pilot on one application: thirty days, success criteria agreed before day one, credited against the annual if you convert.