Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a new Windows 2008 server box coming online in a co-hosted environment. It will host web applications with sql back-end.

What is the best way to secure it?

It will run IIS7 and SQL 2005. The SQL install will only allow Windows authentication. Automatic updates will be enabled.

Should I close certain ports?

I want some sort of protection against DOS attacks and malicious users.

share|improve this question
up vote 1 down vote accepted

As long as you keep on top of the security updates and have a paranoid approach to your firewall you will be fine.

  • Lock down connections to specific IP's if possible
  • Only open what you need and firewall them off to specific applications or services.
  • Have ultra-secure passwords.

If you really feel like being paranoid move RDP away from 3389 and move it to another port.

share|improve this answer

The best way? After you've got things installed, configured, and running, run the Security Configuration Wizard.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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