Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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

We have setup a PC with Windows Server 2003 SP2. It is connected to the internet and runs an SVN server.

Since we are no Windows Server people, we do not know how secure an out-of-the-box Windows 2003 SP2 is. The IP is not public. However if the IP is revealed to public by accident, it can be attacked. We are concerned about somebody getting access to the SVN somehow.

What are the most important security measures on a Windows Server ?

Additionally, are there any ways of getting notified when somebody other than us tries to login to the server ?

share|improve this question

migrated from Feb 19 '10 at 15:04

This question came from our site for computer enthusiasts and power users.

The Security Configuration Wizard is a good start. This will perform the basic lockdown of your system. More than you thought you wanted to know about securing windows 2003 can be found in the Windows Server 2003 Security Compliance Management Toolkit. In particular take a look at Chapter 5: Hardening Infrastructure Servers. This toolkit comes with a workbook and tools that will walk you through securing the system.

Additionally, are there any ways of getting notified when somebody other than us tries to login to the server ?

Yes by editing the local security policy and auditing account logon events. You can choose to audit successes and failures. After that you simply need to schedule and run a script similar to this one that excludes logins from users you like. If you are new to windwos this might initially be beyond your skillset. Watch An Ounce of Prevention: An Introduction to WMI Events (Level 200) for some background on wmi events. Alternatively you could just care about failed logins (since after reading the toolkit you'll see that you can set the list of users that are allowed to login via local security policy), in which case you might simply want to poll the eventlog on a scheduled basis.

share|improve this answer

First things first, Windows server is quite secure by default, but for that extra bit of security, I would start by looking at your edge firewall and locking down everything other than the port SVN uses (outgoing if you can, most people only do incoming).

(I think this is only for R2 and above) Next, take a look at the Baseline security program which should allow you to lock the machine down completely.

share|improve this answer

The most important thing is to get it behind a firewall, even just a NAT router, and only forward the port(s) that actually need to be exposed.

/Edit - just by having a public IP, you can be sure that your machine has already been scanned multiple times. You might want to consider wiping it, rebuilding it behind a firewall, and then making sure that all of the OS updates are applied before you use it again.

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.