Protect Servers Using Bastion Hosts And Isolated Cloud Networks

Filed in Product & Development by Brandon Philips | November 27, 2012 3:30 pm

We know that the public internet can be a scary place for servers. Log files of servers attached to public addresses show regular port scans and URL snooping and are a constant reminder that your hosts are one misconfiguration away from catastrophe.

To help you avoid disaster and thwart potential threats, we’ve created a handy guide to walk you through the creation of bastion hosts and isolated cloud networks.

What’s a bastion host? It’s a choke point that only offers authorized users access to the hosts behind it. It’s like a gatekeeper: it won’t let anyone in who isn’t on the guest list.

And with Rackspace Cloud Networks[1], you can create Rackspace Cloud Servers[2] that do not have a public IP and attach only to an isolated Class A, B or C network that only your Cloud Servers can talk to.

This increases the security of your infrastructure servers and adds an extra layer of defense.

For a deep, technical dive into protecting your infrastructure servers with bastion hosts and isolated cloud networks, check out our guide on the Rackspace DevOps blog[3].

And, remember, Cloud Networks is currently being rolled out to Rackspace customers. You may already have access, and if you don’t, you can request access now[4].

Endnotes:
  1. Rackspace Cloud Networks: http://docs.rackspace.com/servers/api/v2/cn-gettingstarted/content/ch_overview.html
  2. Rackspace Cloud Servers: http://www.rackspace.com/cloud/public/servers/
  3. our guide on the Rackspace DevOps blog: http://devops.rackspace.com/640/protect-your-infrastructure
  4. request access now: https://www.iwantcloudnetworks.com/

Source URL: http://www.rackspace.com/blog/protect-servers-using-bastion-hosts-and-isolated-cloud-networks/