Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Possible Duplicate:
Is iLO safe enough to be hung on the WAN

This might be a dumb question but DRAC/ILO both have HTTP server interfaces.

If I were trolling IP's port 80 on and I came across such a page I'd know it to be a high value target in the sense that if I can crack it, I can take control of the server to some extent (potentially installing another OS).

Other than changing the port, what are the best practices for securing DRAC/ILO on public Internet facing machines?

share|improve this question

marked as duplicate by Lucas Kauffman, Chopper3, ewwhite, EEAA, Wesley Apr 11 '12 at 0:06

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

3 Answers 3

up vote 6 down vote accepted

They both accept uploading your own SSL certificates, so that's the first thing I would do. If you've got enough of these servers, chances are you have your own certificate server and you have its certificate installed as a trusted publisher.

Mind you, all that does is ensure that the ILO/iDrac you're connecting to is yours and you're not being redirected to a honeypot.

The other thing we do to protect them is to not have them facing the public internet. We have all our iDracs on a seperate vlan, which is accessible only after connecting to a VPN. This means a few things:

  1. The VPN goes down and you better have another method of getting onto the devices
  2. You're not "wasting" a public IP address on the drac
  3. Nobody who is not on the VPN can access the device

That said, we do have one client who has put their iDrac on a public IP. If you're going to go down that path:

  1. Restrict the IP addresses at the firewall infront of the iDrac/ILO if you can. Sometimes this is hard to do if you don't know where you're going to be, but if you know you're never going to be in say, China, then that's a good place to start. Whitelisting IPs that belong to the countries you're going to be access it from can block a large amount of malicious traffic.
  2. Change the default password, for gods sake. Use something like KeePass or similar and generate a 64-character password. Have a look at this blog post if you want to know more about why this is important. It's actually about hashing, but the point is the same. If you only take one thing away from it, it's that if there's a vulnerability in the device and they manage to grab a copy of the user database, an 8-character basic password can be cracked in 4 hours without even trying.
share|improve this answer

You don't put them on the internet. Use VPN's.

share|improve this answer

The best common practice is to actually keep the DRAC/iLO port off your externally routed networks. You would generally have a management network utilizing RFC1918 private IP space and not routed through your external edge routers. There is no need to access the DRAC/iLO from external IP addresses so private IP space is the best way to keep them from prying eyes of would-be hackers. If you need to be able to access them remotely then you would have a VPN solution with access to the DRAC/iLO management network once you were connected to the VPN from a remote source.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.