 |
|
 |
Windows 2003 Server Hardening Checklist
The hardening checklists are based on the comprehensive checklists produced
by CIS. The Information Security Office has distilled the CIS lists down
to the most critical steps for your systems, with a particular focus on configuration
issues that are unique to the computing environment at The University of
Texas at Austin.
How to use the checklist
Print the checklist and check off each item you complete to ensure that you
cover the critical steps for securing your server. The Information
Security Office uses this checklist during risk assessments as part of
the process to verify that servers are secure.
How to read the checklist
Step - The step number in the procedure. If there is a UT
Note for this step, the note # corresponds to the step #.
Check (√) - This is for administrators to check off
when she/he completes this portion.
To Do - Basic instructions on what to do to harden the
respective system
CIS - Reference number in the Center for Internet Security
Windows Server 2003 Benchmark (PDF,
Requires UT EID login.) The CIS document outlines in much greater
detail how to complete each step.
UT Note - The UT Note at the bottom
of the page provides additional detail about the step for the university computing
environment.
Cat I - For systems that include Category-I data, required steps are denoted with the ! symbol.
All steps are recommended.
Cat II/III - For systems that include Category-II or -III data, all steps are recommended, and some are required (denoted
by the !).
Min Std - This column links to the specific requirement
for the university in the Minimum Security Standards for Systems document.
Server Information
| MAC Address | |
| IP Address | |
| Machine Name | |
| Asset Tag | |
| Administrator Name | |
| Date | |
| Preparation and Installation |
| Step |
√ |
To Do |
CIS |
UT Note |
Cat I |
Cat II/III |
Min Std |
| 1 |
|
If machine is a new install, protect it from hostile
network traffic, until the operating system is installed and hardened. |
|
§ |
! |
|
5.1 |
| 2 |
|
Consider using the Security Configuration Wizard to
assist in hardening the host. |
|
§ |
|
|
|
| Service Packs and Hotfixes |
| 3 |
|
Install the latest service packs and hotfixes from
Microsoft. |
|
§ |
! |
! |
5.2 |
| 4 |
|
Enable automatic notification of patch availability. |
|
§ |
! |
! |
5.3 |
| Auditing and Account Policies |
| 5 |
|
Configure Audit policy as described. |
2.2.1 |
|
! |
|
6.1 |
| 6 |
|
Set minimum password length. |
2.2.2.3 |
§ |
! |
|
|
| 7 |
|
Enable Password Complexity. |
2.2.2.4 |
§ |
! |
|
|
| 8 |
|
Configure event Log Settings. |
2.2.4 |
§ |
! |
|
6.1 |
| Security Settings |
| 9 |
|
Disable anonymous SID/Name translation. |
3.1.1 |
|
! |
|
|
| 10 |
|
Do not allow Anonymous Enumeration of SAM Accounts
and Shares. |
3.1.2 |
|
! |
|
|
| 11 |
|
Do not allow Anonymous Enumeration of SAM Accounts
and Shares. |
3.1.3 |
|
! |
|
|
| 12 |
|
Disable the guest account. |
3.2.1.2 |
|
! |
|
5.12 |
| 13 |
|
Digitally Encrypt of Sign Secure Channel Data (Always). |
3.2.1.18 |
|
|
|
5.6 |
| 14 |
|
Digitally Encrypt Secure Channel Data (When Possible). |
3.2.1.19 |
|
! |
|
5.6 |
| 15 |
|
Digitally Sign Secure Channel Data (When Possible). |
3.2.1.20 |
|
! |
|
5.6 |
| 16 |
|
Place the University warning banner in the Message
Text for Users Attempting to log on. |
3.2.1.26 |
§ |
! |
|
5.10 |
| 17 |
|
Disable the sending of unencrypted password to connect
to Third-Party SMB Servers. |
3.2.1.35 |
|
! |
|
5.6 |
| 18 |
|
Do not allow Everyone permissions to apply to anonymous
users. |
3.2.1.41 |
|
! |
|
5.12 |
| 19 |
|
Do not allow any named pipes to be accessed anonymously. |
3.2.1.42 |
|
! |
|
5.12 |
| 20 |
|
Restrict anonymous access to Named Pipes and Shares. |
3.2.1.45 |
|
! |
|
5.12 |
| 21 |
|
Ensure that no shares can be accessed anonymously. |
3.2.1.46 |
|
! |
|
5.12 |
| 22 |
|
Choose "Classic" as the sharing and security
model for local accounts. |
3.2.1.47 |
|
! |
|
5.12 |
| Additional Security Protection |
| 23 |
|
Disable or uninstall unused services. |
4.1 |
§ |
! |
|
5.4 |
| 24 |
|
Disable or delete unused users. |
|
|
! |
|
5.4 |
| 25 |
|
Configure User Rights to be as secure as possible. |
4.2 |
§ |
! |
|
|
| 26 |
|
Ensure all volumes are using the NTFS file system. |
4.3.1 |
§ |
! |
|
|
| 27 |
|
Use the Internet Connection Firewall or other methods
to limit connections to the server. |
4.3.3 |
§ |
! |
|
5.5 |
| 28 |
|
Configure file system permissions. |
4.4.1 |
§ |
! |
|
|
| 29 |
|
Configure registry permissions. |
4.4.2 |
§ |
! |
|
|
| Additional Steps |
| 30 |
|
Set the system date/time and configure it to synchronize
against campus time servers. |
|
§ |
! |
|
|
| 31 |
|
Install and enable anti-virus software. |
|
§ |
! |
! |
3.1 |
| 32 |
|
Install and enable anti-spyware software. |
|
§ |
! |
|
3.2 |
| 33 |
|
Configure anti-virus software to update daily. |
|
§ |
! |
|
3.3 |
| 34 |
|
Configure anti-spyware software to update daily. |
|
§ |
! |
|
3.3 |
| 35 |
|
Configure a screen-saver to lock the console's screen
automatically if the host is left unattended. |
|
§ |
|
|
|
| 36 |
|
If the machine is not physically secured against unauthorized
tampering, set a BIOS/firmware password to prevent alterations in system
startup settings. |
|
|
! |
|
4.1 |
| 37 |
|
Configure the device boot order to prevent unauthorized
booting from alternate media. |
|
|
! |
|
4.1 |
| 38 |
|
Systems will provide secure storage for Category-I data as required by confidentiality, integrity, and availability needs. Security can be provided by means such as, but not limited to, encryption, access controls, filesystem audits, physically securing the storage media, or any combination thereof as deemed appropriate. |
|
§ |
! |
|
5.7 |
| 39 |
|
Install software to check the integrity of critical
operating system files. |
|
§ |
! |
|
|
| 40 |
|
If RDP is utilized, set RDP connection encryption level
to high. |
|
§ |
! |
|
|
UT Note: Addendum
This list provides specific tasks related to the computing environment at The University of Texas at Austin.
| 1 |
If other alternatives are unavailable, this can be accomplished by installing
a SOHO router/firewall in between the network and the host to be protected. |
| 2 |
The Security Configuration Wizard can greatly simplify the hardening
of the server. Once the role for the host is defined, the SCW
can help create a system configuration based specifically on that role.
It does not completely get rid of the need to make other configuration
changes, though.
For more information, please see Security
Configuration Wizard for Windows Server 2003.
|
3 |
There are several methods available to assist you in applying patches
in a timely fashion:
Microsoft Update Service
- This Web-based
application checks your machine to identify
missing patches and allows you to download and install them.
- This service is compatible with Internet Explorer only.
Windows AutoUpdate
ITS offers a Windows
Server Update Services Server for campus use using Microsoft's
own update servers.
Microsoft Baseline Security Analyzer
This is a free host-based application that is available
to download from Microsoft. In
addition to detailing missing patches, this tool also performs checks
on basic security settings and provides information on remediating
any issues found. |
4 |
Configure Automatic Updates from the Automatic
Updates control panel
- On servers, you should choose either “Download
updates for me, but let me choose when to install them,” or “Notify
me but don’t automatically download or install them.”
- ITS offers a Windows
Server Update Services Server for campus use using Microsoft's
own update servers.
|
6 |
Configuring the minimum password length settings is important
only if another method of ensuring compliance with university
password standards is not in place. |
7 |
Configuring the password complexity setting is important only if
another method of ensuring compliance with university
password standards is not in place. |
8 |
The university requires the following event log settings instead of
those recommended by the CIS Benchmark:
- Maximum application log size—50000 KB
- Maximum security log size—100000 KB
- Maximum system log size—50000 KB
- Prevent local guests group from accessing application log—enabled
- Prevent local guests group from accessing security log—enabled
- Prevent local guests group from accessing system log—enabled
- Retention method for application log—Overwrite events
older than 14 days
- Retention method for security log—Overwrite
events older that 14 days
- Retention method for system log—Overwrite events older than
14 days
These are minimum requirements. The most important log here is the
security log. 100 MB is a suggested minimum, but if you have
a high-volume service, make the file as large as necessary to make sure
at least 14 days of security logs are available. You may increase
the number of days that you keep, or you may set the log files to not
overwrite events. |
16 |
The text of the university's official
warning banner can be found
on the ITS Web site. You may add localized information to the banner
as long as the university banner is included. |
23 |
Evaluate the services running on your server and disable any that
are not necessary. Much more detailed information regarding services
is available in the CIS Benchmark document. However, you are not
required to disable exactly the same services that the CIS Benchmark
recommends. In this particular case, it is just a reference guide. |
25 |
Configure user rights to allow to be as secure as possible. You
are not required to make the exact User Rights changes outlined in the
CIS Benchmark. In this case, it is just a reference guide for possible
User Rights settings. Every
attempt should be made to remove Guest, Everyone, and ANONYMOUS LOGON from the
user rights lists. |
26 |
If the operating system was installed using FAT format, it may be
converted to NTFS using the convert utility. Microsoft has provided instructions
for the conversion procedure.
This conversion can not be reversed. |
27 |
IPSec is one method that can limit connections to the server, and
it is another standard method by which communication between servers
can be encrypted.
IPSec configuration can be managed using the IP Security Policies
Snap-In. More
information can be found on the Microsoft site. |
28 |
File system permissions: You are not required
to make the exact file system permissions changes outlined in
the CIS Benchmark. In this case, it is just a reference guide for
possible permissions settings.
Proceed extremely carefully, as
setting incorrect permissions on system files and folders can render
a system unusable. |
29 |
Registry Permissions: You are not required
to make the exact registry permissions changes outlined in the
CIS Benchmark. In this case, it is just a reference guide for possible
permissions settings.
Proceed extremely carefully, as setting incorrect
permissions registry entries can render a system unusable. |
30 |
By default, domain members synchronize their time with domain controllers
using Microsoft's Windows
Time Service. The domain controller should be
configured to synchronize its time with an external time source.
ITS Networking operates two stratum 2 NTPv4 (NTP
version 4) servers for network
time synchronization services for university network administrators. |
31 |
Download and install Symantec AntiVirus from BevoWare.
If you are managing many desktops or servers, consider using the Symantec
System Center, which is also available through BevoWare.
|
32 |
Anti-spyware software is only required to be installed if the server
is used to browse Web sites not specifically related to the administration
of the server.
ITS provides anti-spyware software for no additional charge. At a minimum,
SpyBot Search and Destroy should be installed. We also recommend
that a secondary anti-spyware application should be installed such as SpyWare
Blaster, EMS Free Surfer, or AdAware be installed. Both SpyWare Blaster
and EMS Free Surfer are available from BevoWare. |
33 |
See the ITS Web site for instructions
on scheduling daily updates of Symantec AntiVirus. |
34
|
Spyware Blaster—Enabling auto-update functionality requires the
purchase of an additional subscription
SpyBot Search and Destroy—Automatic update tasks can be created
inside the program itself and are scheduled using the Windows Task Scheduler.
- In the Spybot Application, click on Mode-->Advanced View.
- Click Settings on the left hand side of the window.
- You
should now see an option labeled “Scheduler.” Select that
option.
- Adding the task to update automatically is relatively
straightforward.
|
35
|
- Open the Display Properties control panel.
- Select the Screen Saver tab.
- Select a screen saver from
the list. Although there are several available, consider using a simple
one such as "Blank."
- The value for Wait should
be no more than 30 minutes.
- Select the On resume, password protect option.
|
37
|
Windows provides the Encrypting File System as a built-in mechanism
to allow the encryption of individual users’ files and folders.
Be aware of the caveats involved in the use of EFS before implementing
it for general use, though.
In addition to EFS, other options such as PGP and GNUPG exist. |
38
|
Windows Server 2003 has a feature called Windows File Protection which
automatically checks certain key files and replaces them if they become
corrupted. It is enabled by default.
You can audit in much more in depth using Tripwire. Tripwire
has a charge. The
Tripwire management console can be very helpful for managing more complex installations. |
40
|
This setting is configured using the Terminal Services Configuration
tool. On the General tab of the properties of the RDP connection,
select High from the list next to encryption level. |
|