Hardening Windows W2K Server

This document is intended as a starting checklist to harden Windows 2000 Server and IIS for security vulnerabilities. This checklist is designed for those that are extremely familiar with Windows and IIS, as explanations for the checklist actions are not included. It is strongly recommend that you visit the Microsoft Security and Privacy page, at http://www.microsoft.com/security/default.asp, for specific information about each step and the reason behind each action.


Registry Changes


Control Panel Changes

Control Panel\System/Advanced\Startup and Recovery Control Panel\ Administrative Tools\Local Security Policy\Account Policies\Password Policy\ Control Panel\ Administrative Tools\Local Security Policy\Account Policies
\Account Lockout Policy Control Panel\ Administrative Tools\Local Security Policy\Local Policies\Audit Policy Control Panel\ Administrative Tools\Local Security Policy\Local Policies\Security Options Control Panel\Network and Dial-up Connections\applicable connections\Properties\General Control Panel\Network and Dial-up Connections\applicable connections\Properties\General\, select Internet Protocol
(TCP/IP), select Properties, select Advanced\Wins Control Panel\Network and Dial-up Connections\applicable connections\Properties\General\, select Internet Protocol
(TCP/IP), select Properties, select Advanced\Options\TCP/IP filtering Control Panel\ Administrative Tools\Computer Management\Local Users and Groups\Users

Services

Configure the following Windows Services to start automatically: Configure the following Windows Services to start manually Disable the following Windows Services:

General Changes

For the Everyone Group that was renamed Remove all rights for the Everyone group, that was renamed, from following
c:\winnt\system32 files IIS Display Properties Install remote control program if desired Install Firewall software Install AntiVirus program Web Content Vulnerability Scan
NOTE: Other security steps may be required based on you system, architecture, and specific needs!

Site and server security requires daily procedures to insure a proper defense. Security patched must be applied upon release, and the system and firewall logs need to be reviewed daily to track activity and intrusion attempts.

About the Author

Lew Newlin is CTO of Information Solutions, Inc. that operates SiteRecon.com. SiteRecon specializes in security, email monitoring, and web site monitoring for Internet service providers and businesses.