Server Hardening Checklist

• 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.
•Install the latest service packs and hotfixes
• Enable automatic notification of patch availability.
• Configure Audit policy as described.
• Set minimum password length.
• Enable Password Complexity.
• Configure event Log Settings.
• Disable anonymous SID/Name translation.
• Do not allow Anonymous Enumeration of SAM accounts
• Do not allow Anonymous Enumeration of SAM accounts and shares.
• Disable the guest account.
• Digitally Encrypt of Sign Secure Channel Data (Always).
• Digitally Encrypt Secure Channel Data (When Possible).
• Digitally Sign Secure Channel Data (When Possible).
• Disable the sending of unencrypted password to connect to Third-Party SMB Servers.
• Do not allow everyone permissions to apply to anonymous users.
• 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.
• 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, file system 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.