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

• Microsoft Update checks your machine to identify missing patches and allows you to download and install them.
• This is different than the "Windows Update" that is the default on Windows. Microsoft Update includes updates for many more Microsoft products, such as Office and Forefront Client Security.
• This service is compatible with Internet Explorer only. 

Windows AutoUpdate via WSUS
ITS offers a Windows Server Update Services Server for campus use using Microsoft's own update servers. It includes updates for additional Microsoft products, just like Microsoft Update, and provides additional administrative control for software deployment.

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.

Configure Automatic Updates from the Automatic Updates control panel

• On most 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."
• The campus Windows Server Update Services server can be used as the source of automatic updates.

Configuring the minimum password length settings is important only if another method of ensuring compliance with university password standards is not in place. The Information Resources Use and Security Policy requires passwords be a minimum of 8 characters in length. It is strongly recommended that passwords be at least 14 characters in length (which is also the recommendation of CIS).  Longer passwords (e.g., more than 20 characters) offer much more protection (entropy) in the event a password hash is obtained and an attacker is attempting to crack it.

If this option is enabled, the system will store passwords using a weak form of encryption that is susceptible to compromise. This configuration is disabled by default.

Instead of the CIS recommended values, the account lockout policy should be configured as follows:

• Account lockout duration — 5 minutes
• Account lockout threshold — 5 failed attempts
• Reset account lockout counter — 5 minutes

Any account with this role is permitted to log in to the console. By default, this includes users in the Administrators, Users, and Backup Operators groups. It's unlikely that non-administrative users require this level of access and, in cases where the server is not physically secured, granting this right may facilitate a compromise of the device.

The text of the university's official warning banner can be found on the ISO's web site. You may add localized information to the banner as long as the university banner is included.

The use of Microsoft accounts can be blocked by configuring the group policy object at: 

This setting can be verified by auditing the registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\NoConnectedUser

Logon information for domain accounts can be cached locally to allow users who have previously authenticated to do so again even if a domain controller cannot be contacted. By default 10 accounts will be cached locally, but there is a risk that in the event of a compromise an attacker could locate the cached credentials and use a brute force attack to discover the passwords. Therefore, it is recommended that this value be reduced so that fewer credentials will be placed at risk, and credentials will be cached for shorter periods of time in the case of devices that are logged into frequently by multiple users.

The group policy object below should be set to 4 or fewer logins:

Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Interactive logon: Number of previous logons to cache (in case domain controller is not available)

The Account Logon audit policy logs the results of validation tests of credentials submitted for user account logon requests. The server that is authoritative for the credentials must have this audit policy enabled. For domain member machines, this policy will only log events for local user accounts.

Configure the group policy object below to match the listed audit settings:

• Credential Validation — Success and Failure

Configure the group policy object below to match the listed audit settings:

• Computer Account Management — Success and Failure
• Other Account Management Events — Success and Failures
• Security Group Management — Success and Failure
• User Account Management — Success and Failure

Configure the group policy object below to match the listed audit settings:

• Account Lockout — Success
• Logoff — Success
• Logon — Success and Failure
• Other Logon/Logoff Events — Success and Failure
• Special Logon — Success

Configure the group policy object below to match the listed audit settings:

• Audit Policy Change — Success and Failure
• Authentication Policy Change — Success

Configure the group policy object below to match the listed audit settings:

• Sensitive Privilege Use — Success and Failure

The university requires the following event log settings instead of those recommended by the CIS Benchmark:

• Application: Maximum log size — 32,768 KB
• Security: Maximum log size — 196,608 KB
• Setup: Maximum log size — 32,768 KB
• System: Maximum log size — 32,768 KB

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.

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 AutoBackupLogFiles registry entry.

The ISO maintains a centrally-managed Splunk service that may be leveraged.  Please see the on-boarding form for more details.
 

Some remote administration tools, such as Microsoft Systems Management Server, require remote registry access to managed devices. Disabling remote registry access may cause such services to fail. If remote registry access is not required, it is recommended that the remote registry service be stopped and disabled.

If remote registry access is required, the remotely accessible registry paths should still be configured to be as restrictive as possible. The group policy object below controls which registry paths are available remotely:

This object should be set to allow access only to:

• System\CurrentControlSet\Control\ProductOptions
• System\CurrentControlSet\Control\Server Applications
• Software\Microsoft\Windows NT\CurrentVersion

Further restrictions on the registry paths and subpaths that are remotely accessible can be configured with the group policy object:

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, which is not recommended. At a minimum, SpyBot Search and Destroy should be installed. Consider installing a secondary anti-spyware application, such as SpyWare Blaster, EMS Free Surfer, or AdAware.

An additional measure that can be taken is to install Firefox with the NoScript and uBlock add-ons.

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.

1. In the Spybot Application, click on Mode --> Advanced View.
2. Click Settings on the left hand side of the window.
3. You should now see an option labeled "Scheduler." Select that option.
4. Adding the task to update automatically is relatively straightforward. 
   • Click Add to create a task.
   • Click Edit to edit the task schedule.

   • In the Scheduled Task window that pops up, enter the following In the Run field:

     • C:\Program Files\Spybot - Search & Destroy\SpybotSD.exe" /AUTOUPDATE /TASKBARHIDE /AUTOCLOSE

   • Click the Schedule tab and choose a time for it to update. The duration of the update is very brief, but it is processor intensive, so consider scheduling it to occur during periods of low usage. The task should be scheduled daily.

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.

Another encryption option to consider is whole-disk encryption, which encrypts the entire contents of the drive instead of just specific files and folders. Windows comes with BitLocker for this.

If encryption is being used in conjunction with Category I data, one of the solutions listed in the Approved Encryption Methods (EID required) must be implemented.

Windows 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.

You can audit in much more in depth using Tripwire. Modern versions of Tripwire require the purchase of licenses in order to use it. The Tripwire management console can be very helpful for managing more complex installations.

This setting is configured by group policy object at:

\Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security

This policy object should be configured as below:

• Set client connection encryption level — High
• Require use of specific security layer for remote (RDP) connections — SSL (TLS 1.0)
• Require user authentication for remote connections by using Network Level Authentication — Enabled

1. Open the Display Properties control panel.
2. Select the Screen Saver tab.
3. Select a screen saver from the list. Although there are several available, consider using a simple one such as "Blank."
4. The value for Wait should be no more than 15 minutes.
5. Select the On resume, password protect option.