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 number corresponds to the step number.
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 2012 R2 Benchmark v1.1.0. 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.
Cat II Cat III
Preparation and Installation
If machine is a new install, protect it from hostile network traffic, until the operating system is installed and hardened.
Consider using the Security Configuration Wizard to assist in hardening the host.
Service Packs and Hotfixes
Install the latest service packs and hotfixes from Microsoft.
Enable automatic notification of patch availability.
User Account Policies
Configure the account management audit policy.
Set minimum password length.
Enable password complexity requirements.
|8||Do not store passwords using reversible encryption.||1.1.6||§||!|
|9||Configure account lockout policy.||1.2||§||!||!|
|Event Log Policies|
Configure Event Log settings.
Disable anonymous SID/Name translation. (default)
Do not allow Anonymous Enumeration of SAM accounts (Default)
Do not allow Anonymous Enumeration of SAM accounts and shares.
Disable the guest account. (Default)
Digitally Encrypt or Sign Secure Channel Data (Always). (Default)
Digitally Encrypt Secure Channel Data (When Possible). (Default)
Digitally Sign Secure Channel Data (When Possible). (Default)
Place the University warning banner in the Message Text for Users Attempting to log on.
Disable the sending of unencrypted password to connect to Third-Party SMB Servers. (Default)
Do not allow Everyone permissions to apply to anonymous users. (Default)
Do not allow any named pipes to be accessed anonymously.
Restrict anonymous access to Named Pipes and Shares.
Ensure that no shares can be accessed anonymously.
Choose "Classic" as the sharing and security model for local accounts. (Default)
Do not store LAN Manager hash values
Set LAN Manager Authentication level to NTLMv2 only
|Configure Account Logon audit policy||17.1|
|Configure Account Management audit policy||17.2|
|Configure Logon/Logoff audit policy||17.5|
|Configure Policy Change audit policy||17.7|
|Configure Privilege Use audit policy||17.8|
Additional Security Protection
Disable or uninstall unused services.
Disable or delete unused users.
Configure User Rights to be as secure as possible.
Ensure all volumes are using the NTFS file system.
Use the Internet Connection Firewall or other methods to limit connections to the server.
Configure file system permissions.
Configure registry permissions.
Set the system date/time and configure it to synchronize against campus time servers.
Install and enable anti-virus software.
Install and enable anti-spyware software.
Configure anti-virus software to update daily.
Configure anti-spyware software to update daily.
Configure a screen-saver to lock the console's screen automatically if the host is left unattended.
If the machine is not physically secured against unauthorized tampering, set a BIOS/firmware password to prevent alterations in system startup settings.
Configure the device boot order to prevent unauthorized booting from alternate media.
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.
Install software to check the integrity of critical operating system files.
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.
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.
The Security Configuration Wizard can greatly simplify the hardening of the server. Once the role for the host is defined, the Security Configuration Wizard 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. More information is available at: Security Configuration Wizard.
There are several methods available to assist you in applying patches in a timely fashion:
Microsoft Update Service
Configure Automatic Updates from the Automatic Updates control panel
The audit policy should be configured as follows:
Configuring the minimum password length settings is important only if another method of ensuring compliance with university password standards is not in place.
Configuring the password complexity setting is important only if another method of ensuring compliance with university password standards is not in place.
The university requires the following event log settings instead of those recommended by the CIS Benchmark:
The recommended retention method for all logs is: 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.
Note that if the event log reaches its maximum size and no events older than the number of days you specified exist to be deleted, or if you have disabled overwriting of events, no new events will be logged. This may happen deliberately as an attempt by an attacker to cover his tracks. For critical services working with Cat 1 or other sensitive data, you should use syslog, Splunk, Intrust, or a similar service to ship logs to another device. This helps to ensure that logs are preserved and unaltered in the event of a compromise.
Another option is to configure Windows to rotate event log files automatically when an event log reaches its maximum size as described in the article http://support.microsoft.com/kb/312571 using the the AutoBackupLogFiles registry entry.
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.
Configure user rights to be as secure as possible. Every attempt should be made to remove Guest, Everyone, and ANONYMOUS LOGON from the user rights lists.
Volumes formatted as FAT or FAT32 can be converted to NTFS, by using the convert.exe utility provided by Microsoft. Microsoft has provided instructions on how to perform the conversion. This conversion cannot be reversed.
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.
Be extremely careful, as setting incorrect permissions on system files and folders can render a system unusable.
Be extremely careful, as setting incorrect permissions on registry entries can render a system unusable.
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, such as the university's network time servers.
Download and install Microsoft Forefront Client Security from BevoWare.
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 the installation of a secondary anti-spyware application, such as SpyWare Blaster, EMS Free Surfer, or AdAware. Both SpyWare Blaster and EMS Free Surfer are available from BevoWare.
Spyware Blaster - Enabling auto-update functionality requires the purchase of an additional subscription.
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. Other options such as PGP and GNUPG also exist.
Windows Server 2008 has a feature called Windows Resource Protection which automatically checks certain key files and replaces them if they become corrupted. It is enabled by default.
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.