ServerPronto Dedicated Servers
       ServerPronto Home   ServerPronto University     
ServerPronto University  

Best Practices for Dedicated Servers: Securing Your Server


December 4th, 2006

Freedom, by definition, demands responsibility.

In dedicated server land, you enjoy abundant freedom. You’re free to run the OS and software that best meets your needs (as long as that software doesn’t violate your provider’s acceptable use policies). You’re free to have as many IP addresses and domains as you’d like. And you’re free to choose the bandwidth allotment that your traffic demands.
 

Of course, along with that flexibility and power comes the duty to protect your turf. Here are a few best practices that will help your server remain free – and safe:
 

  1. Patch, Patch, Patch
    Why leave the door wide open for a hacker? Keep an eye out for patches for all your software and apply them regularly and diligently. Apache web server patches are announced at http://httpd.apache.org/security_report.html, and you can find patches and more for Microsoft’s IIS at http://www.microsoft.com/WindowsServer2003/iis/default.mspx.
    If you’re using Windows, visit http://update.microsoft.com often to check for both critical and optional OS and software patches. Or, better yet, turn on automatic updates. Many Linux distributions also feature an automatic update feature. But, if the one you’re using does not, check the distro’s website. The same goes for all your applications, particularly your software firewall.
  2. Work Within a Secure Shell
    Whenever you update and maintain your website, be sure to do so using SSH/SCP so that your login information is encrypted. Encryption is a simple, yet powerful, best practice that will could eliminate a myriad of problems.
  3. Practice Good Password Hygiene
    Cheekymonkey is not a good password! Hackers love passwords that contain dictionary words. Make their lives a lot harder by choosing passwords that are at least six characters long, use a mixture of upper and lowercase letters, and include numbers and other allowable characters.
  4. Close Your Ports
    You’ll need port 80 for HTTP access and port 22 to use SSH/SCP, and, if your site provides secure transactions for e-commerce and the like, you’ll also need to open port 443. Beyond these essential gateways, however, examine your needs very carefully and close down any ports you won’t need.
  5. Inoculate Your Server Against Viruses
    In today’s security climate, it should go without saying, yet security researchers continue to report amazement into how often this safe computing practice is ignored. Be sure to use an antivirus program that provides frequent definition updates.
  6. Don’t Forget Physical Security
    With all the cyber-threats that loom, it’s easy to forget that one of the easiest ways to compromise a server is to have physical access to it. While most data centers are reasonably secure, it pays to see if your provider’s facilities are housed in reinforced structures with adequate security.

Discussions of server security can – and do – fill entire books, but these tips provide a good start and will help you provide your users a safe and secure Web environment.

Š



Entry Filed under: Dedicated Server Best Practices,Dedicated Server Security

 

4 Comments Add your own

  • 1. Tufan Deveci  |  May 10th, 2007 at 2:44 pm

    i am using cool Debian/GNU Linux OS on dedicated servers and
    securing by default close ssh port access to hosts and knockd software help my access ssh connection before trying to connect example host port,port2,port3 the after knockd iptables rule create to allow my internet ip access to server ssh access.

  • 2. coRank&hellip  |  May 16th, 2007 at 12:59 am

    ServerPronto University Blog

    The ServerPronto University Blog offers tips on subjects like migrating to a dedicated server and how to make the most of dedicated server resources.

  • 3. pascal  |  May 19th, 2007 at 4:09 am

    Setting up a firewall for windows on a deticated server is highly risky because after installing and rebooting the firewall by default blocks all network traffic. So you cannot even maintain your server anymore via telnet or terminal services. I’m seaching for a solution on this.

  • 4. Tufan Deveci  |  May 31st, 2007 at 7:05 am

    pascal,

    if u use the w2k or w2k3 server os and use rdp (remote desktop protocol);
    you setting up a firewall for windows on a dedicated server and make the fw.bat file
    before add windows startup shortcut run fw.bat file after reboot server,

    fw.bat content this;

    netsh firewall add portopening tcp 3389 rdp

    u try this solition

Leave a Comment

hidden
Comment:

Some HTML allowed:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Trackback this post  |  Subscribe to the comments via RSS Feed

 
Infolink ServerPronto Infolink Review Our Guarantee Why Choose ServerPronto? Why Choose ServerPronto? Review Our Guarantee Home About Why Choose ServerPronto? Compare Packages Frequently Asked Questions (FAQ) Order Now!