Windows 2003 Domain Controller Security Technical Implementation Guide

Checks: C-7883r1_chk

Interview the SA to determine if equipment is located in an access controlled area. Note: Servers will be located in rooms, or locked cabinets, that are accessible only to authorized systems personnel. Authorized user access should be verified at two points (i.e. building access and server room). User workstations containing sensitive data should be in access controlled areas.

Fix: F-31r1_fix

Relocate equipment to a controlled access area.

Checks: C-7885r1_chk

Interview the SA to determine if any shared accounts exist. Any shared account must be documented with the IAO. Documentation should include the reason for the account, who has access to this account, and how the risk of using a shared account (which provides no individual identification and accountability) is mitigated. Note: As an example, a shared account may be permitted for a help desk or a site security personnel machine, if that machine is stand-alone and has no access to the network.

Fix: F-33r1_fix

Remove any shared accounts that do not meet the exception requirements listed.

Checks: C-51979r1_chk

Verify the permissions for the Windows event logs. If the permissions for these files are not as restrictive as the permissions listed below, this is a finding. The event log files "AppEvent.Evt," "SecEvent.Evt," and "SysEvent.Evt" are found in the "%SystemRoot%\SYSTEM32\CONFIG" directory by default. They may have been moved to another folder. Administrators - Read & Execute "Auditors" group - Full Control SYSTEM - Full Control Note: See V-1137 for the Auditors group requirement.

Fix: F-53859r1_fix

Configure the access permissions on the event logs to the following: The event log files "AppEvent.Evt," "SecEvent.Evt," and "SysEvent.Evt" are found in the "%SystemRoot%\SYSTEM32\CONFIG" directory by default. They may have been moved to another folder. Administrators - Read & Execute "Auditors" group - Full Control SYSTEM - Full Control

Checks: C-23r1_chk

If system-level auditing is not enabled, or if the system and data partitions are not installed on NTFS partitions, then mark this as a finding. Open Windows Explorer and use the file and folder properties function to verify that the audit settings on each partition/drive is configured to audit all "failures" for the "Everyone" group. If any partition/drive is not configured to at least the minimum requirement, then this is a finding.

Fix: F-52r1_fix

Configure auditing on each partition/drive to audit all "Failures" for the "Everyone" group.

Checks: C-40667r2_chk

Verify system level auditing of object access is properly configured (see V-6850 “Audit object access”). If this is not configured to audit “Failure”, this requirement is a finding. Verify detailed registry auditing is configured. Run “Regedit”. Navigate to the HKEY_LOCAL_MACHINE\SOFTWARE and HKEY_LOCAL_MACHINE\SYSTEM keys. On the menu bar, select “Edit” then “Permissions”. Click on the “Advanced” button. Select the “Auditing” tab. Verify the following is configured: Type - Fail Name - Everyone Access - Full Control Apply to - This key and subkeys If the “Everyone” group, at a minimum is not being audited for all failures, this is a finding.

Fix: F-28953r1_fix

Configure the HKEY_LOCAL_MACHINE\SOFTWARE and HKEY_LOCAL_MACHINE\SYSTEM keys to audit the Everyone Group for all failures. Audit settings should be propagated to subkeys.

Checks: C-32717r3_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “Interactive Logon: Message text for users attempting to log on” is not set to the following, then this is a finding. You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details. Any OS versions that do not support the full text version must state the following: “I've read & consent to terms in IS user agreem't.” Deviations are not permitted except as authorized by the Deputy Assistant Secretary of Defense for Information and Identity Assurance. The policy referenced configures the following registry value: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \Software\Microsoft\Windows\CurrentVersion\Policies\System\ Value Name: LegalNoticeText Value Type: REG_SZ Value: See message text above

Fix: F-28804r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options ->“Interactive Logon: Message text for users attempting to log on” as outlined in the check.

Checks: C-72r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Event Logs -> Settings for Event Logs. If the value for “Prevent local guests group from accessing application log” is not set to “Enabled”, then this is a finding. If the value for “Prevent local guests group from accessing security log” is not set to “Enabled”, then this is a finding. If the value for “Prevent local guests group from accessing system log” is not set to “Enabled”, then this is a finding.

Fix: F-84r1_fix

Configure the system to prevent guest access to the Event logs.

Checks: C-3200r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Account Policies -> Account Lockout Policy. If the “Account lockout threshold” is "0" or more than three attempts, then this is a finding.

Fix: F-6569r1_fix

Configure the system to lock out an account after three invalid logon attempts.

Checks: C-3203r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Account Policies -> Account Lockout Policy. If the “Reset account lockout counter after” value is less than 60 minutes, then this is a finding.

Fix: F-6570r1_fix

Configure the system to have the lockout counter reset itself after a minimum of 60 minutes.

Checks: C-3205r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Account Policies -> Account Lockout Policy. If the “Account lockout duration” is not set to "0", requiring and administrator to unlock the account, then this is a finding.

Fix: F-6571r1_fix

Configure the system so that the bad logon lockout duration conforms to DoD requirements.

Checks: C-52091r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> User Rights Assignment. Compare the User Rights to the following list. If any groups or accounts are given rights that are not authorized below, this is a finding. Access this computer from the network - Administrators, Authenticated Users, Enterprise Domain Controllers Act as part of the operating system - See separate vulnerability V-1102 Add workstations to domain - Administrators Adjust memory quotas for a process - Administrators, Local Service, Network Service Allow log on locally - Administrators, Backup Operators Allow log on through Terminal Services - (None) Backup files and directories - Administrators, Backup Operators Bypass traverse checking - Authenticated Users Change the system time - Administrators, Local Service Create a pagefile - Administrators Create a token object - (None) Create global objects - Administrators, Service Create permanent shared objects - (None) Debug programs - See separate vulnerability V-18010 Deny access to this computer from the network - See separate vulnerability V-1155 Deny log on as a batch job - See separate vulnerability V-26483 Deny log on as a service - See separate vulnerability V-26484 Deny log on locally - See separate vulnerability V-26485 Deny log on through Terminal Services - See separate vulnerability V-26486 Enable computer and user accounts to be trusted for delegation - Administrators Force shutdown from a remote system - Administrators Generate security audits - Local Service, Network Service Impersonate a client after authentication - Administrators, Service Increase scheduling priority - Administrators Load and unload device drivers - Administrators Lock pages in memory - (None) Log on as a batch job - (None) Log on as a service - Network Service Manage auditing and security log - "Auditor’s" Group (Exchange Enterprise Servers Group on Domain Controllers and Exchange Servers) Modify firmware environment values - Administrators Perform volume maintenance tasks - Administrators Profile single process - Administrators Profile system performance - Administrators Remove computer from docking station - Administrators Replace a process level token - Local Service, Network Service Restore files and directories - Administrators, Backup Operators Shut down the system - Administrators Synchronize directory service data - See separate vulnerability V-12780 Take ownership of files or other objects - Administrators Documentable Explanation: Some applications require one or more of these rights to function. Any exception needs to be documented with the IAO. Acceptable forms of documentation include vendor published documents and application owner confirmation.

Fix: F-53977r1_fix

Configure User Rights as listed below to prevent groups or accounts from having unauthorized rights. Access this computer from the network - Administrators, Authenticated Users, Enterprise Domain Controllers Act as part of the operating system - See separate vulnerability V-1102 Add workstations to domain - Administrators Adjust memory quotas for a process - Administrators, Local Service, Network Service Allow log on locally - Administrators, Backup Operators Allow log on through Terminal Services - (None) Backup files and directories - Administrators, Backup Operators Bypass traverse checking - Authenticated Users Change the system time - Administrators, Local Service Create a pagefile - Administrators Create a token object - (None) Create global objects - Administrators, Service Create permanent shared objects - (None) Debug programs - See separate vulnerability V-18010 Deny access to this computer from the network - See separate vulnerability V-1155 Deny log on as a batch job - See separate vulnerability V-26483 Deny log on as a service - See separate vulnerability V-26484 Deny log on locally - See separate vulnerability V-26485 Deny log on through Terminal Services - See separate vulnerability V-26486 Enable computer and user accounts to be trusted for delegation - Administrators Force shutdown from a remote system - Administrators Generate security audits - Local Service, Network Service Impersonate a client after authentication - Administrators, Service Increase scheduling priority - Administrators Load and unload device drivers - Administrators Lock pages in memory - (None) Log on as a batch job - (None) Log on as a service - Network Service Manage auditing and security log - "Auditor’s" Group (Exchange Enterprise Servers Group on Domain Controllers and Exchange Servers) Modify firmware environment values - Administrators Perform volume maintenance tasks - Administrators Profile single process - Administrators Profile system performance - Administrators Remove computer from docking station - Administrators Replace a process level token - Local Service, Network Service Restore files and directories - Administrators, Backup Operators Shut down the system - Administrators Synchronize directory service data - See separate vulnerability V-12780 Take ownership of files or other objects - Administrators Document any exceptions with the IAO.

Checks: C-3221r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Account Policies -> Password Policy. If the value for the “Maximum password age” is greater than 60 days, then this is a finding. If the value is set to 0 (never expires), then this is a finding.

Fix: F-6573r1_fix

Configure the Maximum Password Age so that it is not "0" and doesn't exceed 60 days.

Checks: C-3223r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Account Policies -> Password Policy. If the value for the “Minimum password age” is less than one day, then this is a finding.

Fix: F-6574r1_fix

Configure the Minimum Password Age so that it is a minimum of "1".

Checks: C-3227r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Account Policies -> Password Policy. If the value for “Enforce password history” is less than 24 passwords, then this is a finding.

Fix: F-6576r1_fix

Configure the system to remember a minimum of "24" used passwords.

Checks: C-394r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “Accounts: Guest account status” is not set to ” Disabled”, then this is a finding.

Fix: F-5759r1_fix

Configure the system to disable the built-in guest Account.

Checks: C-403r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “Accounts: Rename guest account” is not set to a value other than “Guest”, then this is a finding.

Fix: F-5761r1_fix

Configure the system to rename the built-in guest account

Checks: C-411r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “Accounts: Rename administrator account” is not set to a value other than “Administrator”, then this is a finding.

Fix: F-5762r1_fix

Configure the system to rename the built-in administrator account.

Checks: C-505r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Event Log -> Settings for Event logs. If any of the following conditions are true, then this is a finding: For all Server Event logs: if the value for “Retention method for application, security and system logs is not set to “Do not overwrite events (clear log manually)”, then this is a finding. Documentable Explanation: If the machine is configured to write an event log directly to an audit server, the “Retention method for log” for that log does not have to conform to the requirements above. If an alternative auditing methodology is being used to collect and safeguard audit data (e.g. Audit Server), then this check is “Not Applicable”. Document this with the IAO.

Fix: F-5805r1_fix

Configure the system to properly preserve Event Log information.

Checks: C-509r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Event Log -> Settings for Event Logs. If the value for “Maximum application log size” is not set to a minimum of “16384 kilobytes”, then this is a finding. If the value for “Maximum security log size” is not set to a minimum of “81920 kilobytes”, then this is a finding. If the value for “Maximum system log size” is not set to a minimum of “16384 kilobytes”, then this is a finding. Documentable Explanation: If the machine is configured to write an event log directly to an audit server, the “Maximum log size” for that log does not have to conform to the requirements above. This should be documented with the IAO. Note: Microsoft recommends that the combined size of all the event logs (including DNS logs, Directory Services logs, and Replication logs on Servers or Domain Controllers) should not exceed 300 megabytes. Exceeding the recommended value can impact performance.

Fix: F-5808r1_fix

Configure the system to have the required minimum Event log sizes.

Checks: C-513r1_chk

Open the Control Panel Double-click on the “System” applet. Click on the “Advanced” tab. Click the Startup and Recovery “Settings” button. If the drop-down listbox in System Startup shows any operating system other than the current Windows OS, this may be a finding. If all additional operating systems are STIG compliant, then this is not a finding.

Fix: F-5811r1_fix

Configure the system to prevent running non-compliant alternate operating systems.

Checks: C-515r1_chk

In the “Command Prompt” window, enter the following command, and attempt to logon as the user “anonymous:” C:\>ftp 127.0.0.1 (Connected to ftru014538.ncr.disa.mil. 220 ftru014538 Microsoft FTP Service (Version 2.0).) User: anonymous (331 Anonymous access allowed, send identity (e-mail name) as password.) Password: password (230 Anonymous user logged in.) ftp> If the command response indicates that an anonymous FTP login was permitted, then this is a finding. Severity Override: If accounts with administrator privileges are used to access FTP, then this becomes a Category I finding.

Fix: F-5813r1_fix

Configure the system to prevent an installed FTP service from allowing prohibited logons.

Checks: C-518r1_chk

If the any of the registry values don’t exist or are not configured as follows, then this is a finding: Registry Hive: HKEY_CURRENT_USER Subkey: \Software\Policies\Microsoft\Windows\Control Panel\Desktop\ Value Name: ScreenSaveActive Type: REG_SZ Value: 1 Value Name: ScreenSaverIsSecure Type: REG_SZ Value: 1 Value Name: ScreenSaveTimeOut Type: REG_SZ Value: 900 (or less) Documentable Explanation: Terminal servers and applications requiring continuous, real-time screen display (i.e., network management products) require the following and need to be documented with the IAO. -The logon session does not have administrator rights. -The display station (i.e., keyboard, monitor, etc.) is located in a controlled access area.

Fix: F-5816r1_fix

Configure The policy values for User Configuration -> Administrative Templates -> Control Panel -> Display as follows: “Screen Saver” will be set to “Enabled” (“Activate screen saver” on Windows 2000) “Password protect the screen saver” will be set to “Enabled” “Screen Saver timeout” will be set to “Enabled: 900 seconds” (or less)

Checks: C-32952r1_chk

The default ACL settings are adequate when the Security Option “Network access: Let everyone permissions apply to anonymous users” is set to “Disabled” (V-3377) and Power User Group Membership is restricted. If the default ACLs are maintained, the referenced option is set to “Disabled” and Powers Users are restricted, this check should normally be marked “Not a Finding” Specific System files are an exception to this. The following will be configured with only Administrators and System having Full Permissions: \regedit.exe \System32\arp.exe \System32\at.exe \System32\attrib.exe \System32\cacls.exe \System32\debug.exe \System32\edlin.exe \System32\eventcreate.exe \System32\eventtriggers.exe \System32\ftp.exe \System32\nbtstat.exe \System32\net.exe \System32\net1.exe \System32\netsh.exe \System32\netstat.exe \System32\nslookup.exe \System32\ntbackup.exe \System32\rcp.exe \System32\reg.exe \System32\regedt32.exe \System32\regini.exe \System32\regsvr32.exe \System32\rexec.exe \System32\route.exe \System32\rsh.exe \System32\sc.exe \System32\secedit.exe \System32\subst.exe \System32\Systeminfo.exe \System32\telnet.exe \System32\tftp.exe \System32\tlntsvr.exe Documentable Explanation: If an ACL setting prevents a site’s applications from performing properly, the site can modify that specific setting. Settings should only be changed to the minimum necessary for the application to function. Each exception to the recommended settings should be documented and kept on file by the IAO.

Fix: F-29103r1_fix

Maintain the default file ACLs, configure the Security Option: “Network access: Let everyone permissions apply to anonymous users” to “Disabled” (V-3377) and restrict the Power Users group to include no members. Configure permissions on the following so that only Administrators and System have Full (no other permissions assigned to other accounts or groups). \regedit.exe \System32\arp.exe \System32\at.exe \System32\attrib.exe \System32\cacls.exe \System32\debug.exe \System32\edlin.exe \System32\eventcreate.exe \System32\eventtriggers.exe \System32\ftp.exe \System32\nbtstat.exe \System32\net.exe \System32\net1.exe \System32\netsh.exe \System32\netstat.exe \System32\nslookup.exe \System32\ntbackup.exe \System32\rcp.exe \System32\reg.exe \System32\regedt32.exe \System32\regini.exe \System32\regsvr32.exe \System32\rexec.exe \System32\route.exe \System32\rsh.exe \System32\sc.exe \System32\secedit.exe \System32\subst.exe \System32\Systeminfo.exe \System32\telnet.exe \System32\tftp.exe \System32\tlntsvr.exe

Checks: C-32861r1_chk

Verify that password complexity software is installed and enforced that requires a case-sensitive character mix of upper case letters, lower case letters, numbers, and special characters, including at least one of each. The enpasflt password filter is available as an option on the IASE website in the Windows Support Files area (PKI required - http://iase.disa.mil/stigs/os/windows/support_files.html). It should be tested for the particular environment. If it does not function properly or causes issues, the site will be responsible for obtaining other password complexity software to meet the requirements. The current available versions are: Name – Modified Date EnPasFltV2x86.dll – 3/21/2011 EnPasFltV2x64.dll – 3/21/2011 If another product, such as PPE, or a different version of enpasflt is used, the SA should demonstrate that it is configured to enforce the DoD requirements. For the enpasflt password filter to function properly, verify the following: -The appropriate version of the file will be located in %systemroot%\system32. -The Date Modified should be 3/21/2011. -The “Notification Packages” value under registry key “HKLM\System\CurrentControlSet\Control\LSA” must include the file name (e.g., “EnPasFltV2x86”). Severity Override: If no password filter is used, and the security option for “Password must meet complexity requirements” (V0001150/3.028) is set to “Enabled”, then this finding can be downgraded to a Category III, since a less strict complexity algorithm is used. Note: If a password filter is not used, the site is still responsible for requiring full compliance with DoD policy, even though the password complexity setting does not enforce the 4-character type rule.

Fix: F-56r1_fix

Install password complexity software and configure it to enforce the required DoD standards of a case sensitive character mix of upper case letters, lower case letters, numbers, and special characters, including at least one of each. If the enpasflt password filter is used: - Copy the appropriate version to %systemroot%\system32. - Add the file name (e.g., “EnPasFltV2x86”) to the “Notification Packages” value under registry key “HKLM\System\CurrentControlSet\Control\LSA”. -Restart the system.

Checks: C-7886r1_chk

Interview the SA to determine if an Auditors group for controlling the Windows Event Logs has been created. NOTE: The administrator(s) responsible for the installation and maintenance of the individual system(s) must be a member(s) of the Auditors group. This will permit the responsible administrator to enable and configure system auditing, and perform maintenance functions related to the logs. Administrators who are not responsible for maintenance on an individual system will not be included in the Auditors group.

Fix: F-34r1_fix

Create an Auditors group for controlling the Windows Event Logs and assign the necessary rights and access controls.

Checks: C-76r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “MSS: (DisableSavePassword) Prevent the dial-up password from being saved (recommended)” is not set to “Enabled”, then this is a finding. The policy referenced configures the following registry value: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \System\CurrentControlSet\Services\RasMan\Parameters\ Value Name: DisableSavePassword Value Type: REG_DWORD Value: 1

Fix: F-86r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> “MSS: (DisableSavePassword) Prevent the dial-up password from being saved (recommended)” to “Enabled”.

Checks: C-90r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “Microsoft Network Client: Send unencrypted password to connect to third-party SMB servers” is not set to “Disabled”, then this is a finding. The policy referenced configures the following registry value: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \System\CurrentControlSet\Services\LanmanWorkstation\Parameters\ Value Name: EnablePlainTextPassword Value Type: REG_DWORD Value: 0

Fix: F-93r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> “Microsoft Network Client: Send unencrypted password to connect to third-party SMB servers” to “Disabled”.

Checks: C-88r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “Interactive Logon: Do not require CTRL+ALT+DEL” is not set to “Disabled”, then this is a finding. The policy referenced configures the following registry value: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \Software\Microsoft\Windows\CurrentVersion\Policies\System\ Value Name: DisableCAD Value Type: REG_DWORD Value: 0

Fix: F-92r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> “Interactive Logon: Do not require CTRL ALT DEL” to “Disabled”.

Checks: C-27008r1_chk

Servers - Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “Interactive logon: Smart card removal behavior” is not set to “Lock Workstation”, or “Force Logoff”, then this is a finding. The policy referenced configures the following registry value: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \Software\Microsoft\Windows NT\CurrentVersion\Winlogon\ Value Name: SCRemoveOption Value Type: REG_SZ Value: 1 (Lock Workstation) or 2 (Force Logoff) Documentable Explanation: If configuring this on servers causes issues such as terminating users’ remote sessions and the site has a policy in place that any other sessions on the servers such as administrative console logons are manually locked or logged off when unattended or not in use, this would be acceptable. This will be documented with the IAO.

Fix: F-105r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> “Interactive logon: Smart card removal behavior” to “Lock Workstation” or “Force Logoff”.

Checks: C-121r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “Microsoft Network Server: Digitally sign communications (if client agrees)” is not set to “Enabled”, then this is a finding. The policy referenced configures the following registry value: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \System\CurrentControlSet\Services\LanManServer\Parameters\ Value Name: EnableSecuritySignature Value Type: REG_DWORD Value: 1

Fix: F-104r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> “Microsoft Network Server: Digitally sign communications (if Client agrees)” to “Enabled”.

Checks: C-114r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “Domain Member: Digitally encrypt secure channel data (when possible)” is not set to “Enabled”, then this is a finding. The policy referenced configures the following registry value: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \System\CurrentControlSet\Services\Netlogon\Parameters\ Value Name: SealSecureChannel Value Type: REG_DWORD Value: 1 Note: If the value for “Domain Member: Digitally encrypt or sign secure channel data (always)” is set to “Enabled”, then this would not be a finding.

Fix: F-101r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> “Domain Member: Digitally encrypt secure channel data (when possible)” to “Enabled”.

Checks: C-112r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “Domain Member: Digitally sign secure channel data (when possible)” is not set to “Enabled”, then this is a finding. The policy referenced configures the following registry value: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \System\CurrentControlSet\Services\Netlogon\Parameters\ Value Name: SignSecureChannel Value Type: REG_DWORD Value: 1 Note: If the value for “Domain Member: Digitally encrypt or sign secure channel data (always)” is set to “Enabled”, then this would not be a finding.

Fix: F-100r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> “Domain Member: Digitally sign secure channel data (when possible)” to “Enabled”.

Checks: C-4361r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “Microsoft Network Client: Digitally sign communications (if server agrees)” is not set to “Enabled”, then this is a finding. The policy referenced configures the following registry value: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \System\CurrentControlSet\Services\LanmanWorkstation\Parameters\ Value Name: EnableSecuritySignature Value Type: REG_DWORD Value: 1

Fix: F-103r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> “Microsoft Network Client: Digitally sign communications (if server agrees)” to “Enabled”.

Checks: C-51789r1_chk

Review the Backup Operators group in Computer Management and/or Active Directory Users and Computers. If the group contains no accounts, this is not a finding. If the group does contain any accounts, this must be documented as specified below. Documentable Explanation: Any accounts that are members of the Backup Operators group must be documented with the IAO including application accounts. Each Backup Operator will have a separate user account for backing up the system and for performing normal user tasks.

Fix: F-53573r1_fix

Ensure that each member has separate accounts for user tasks and for backup operator functions. Create the necessary documentation that identifies the members of the Backup Operators group.

Checks: C-135r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “Devices: Allowed to Format and Eject Removable Media” is not set to ” Administrators”, then this is a finding. The policy referenced configures the following registry value: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \Software\Microsoft\Windows NT\CurrentVersion\Winlogon Value Name: AllocateDASD Value Type: REG_SZ Value: 0

Fix: F-113r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> “Devices: Allowed to Format and Eject Removable Media” to “Administrators”.

Checks: C-9572r1_chk

Windows 2003/XP/Vista - Use the "Security Configuration and Analysis" snap-in to analyze the system. Expand the “Security Configuration and Analysis” object in the tree window. Expand the “System Services” object and select each applicable disabled Service. (Disabled Services can be identified using the Control Panel’s Services applet. Right click the Service and select Properties Select ‘View Security’ If the ACLs for applicable disabled Services do not restrict permissions to Administrators, ‘full Control’, System ‘full control’, and Interactive ‘Read’, then this is a finding. Note: These are the Windows default settings.

Fix: F-58r1_fix

Create a Custom Security Template using the Security Template MMC Snap-in to set the permissions as required for disabled services. Import the Custom Template into the Security Configuration and Analysis Snap-In and Select Configure Computer Now Or import the Custom Template in to a Group Policy for application. The administrator should have a thorough understanding of these tools before implementing settings with them.

Checks: C-141r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Account Policies -> Password Policy. If the value for “Store password using reversible encryption” is not disabled, then this is a finding.

Fix: F-115r1_fix

Configure the system to prevent passwords from being saved using reverse encryption.

Checks: C-32082r1_chk

1. Analyze the system using the Security Configuration and Analysis snap-in. 2. Expand the Security Configuration and Analysis tree view. 3. Navigate to Local Policies and select Security Options. 4. If the value for “Domain Controller: Allow server operators to schedule tasks” is not set to “Disabled”, then this is a finding.

Fix: F-28439r1_fix

Set the value for “Domain Controller: Allow server operators to schedule tasks” to “Disabled”. The policy referenced configures the following registry value: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \System\CurrentControlSet\Control\LSA\ Value Name: SubmitControl Value Type: REG_DWORD Value: 0

Checks: C-468r1_chk

1. Analyze the system using the Security Configuration and Analysis tool. 2. Expand the Security Configuration and Analysis tree view. 3. Navigate to Account Policies -> Kerberos Policy. 4. If the “Enforce user logon restrictions” is not set to ‘Enabled’, then this is a finding.

Fix: F-5781r1_fix

Set the Kerberos policy option “Enforce user logon restrictions” to ‘Enabled’

Checks: C-39117r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Account Policies -> Kerberos Policy. If the value for “Maximum lifetime for service ticket” is 0 or greater than 600 minutes, this is a finding.

Fix: F-34267r1_fix

Configure the Kerberos policy option “Maximum lifetime for service ticket” to a maximum of 600 minutes, but not 0 which equates to “Ticket doesn’t expire”.

Checks: C-39119r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Account Policies -> Kerberos Policy. If the value for “Maximum lifetime for user ticket” is 0 or greater than 10 hours, this is a finding.

Fix: F-34268r1_fix

Set the Kerberos policy option "Maximum lifetime for user ticket" to a maximum of 10 hours, but not 0 which equates to “Ticket doesn’t expire”.

Checks: C-471r1_chk

1. Analyze the system using the Security Configuration and Analysis. 2. Expand the Security Configuration and Analysis tree view. 3. Navigate to Account Policies -> Kerberos Policy. 4. If the “Maximum lifetime for user ticket renewal” is greater than ‘7’ days, then this is a finding.

Fix: F-5784r1_fix

Configure the Kerberos policy option "Maximum lifetime for user ticket renewal" to a maximum of 7 days or less.

Checks: C-472r1_chk

1. Analyze the system using the Security Configuration and Analysis tool. 2. Expand the Security Configuration and Analysis tree view. 3. Navigate to Account Policies -> Kerberos Policy. 4. If the “Maximum tolerance for computer clock synchronization” is greater than ‘5’ minutes, then this is a finding.

Fix: F-5785r1_fix

Configure the Kerberos policy option Maximum tolerance for computer clock synchronization to a maximum of 5 minutes or less.

Checks: C-7891r1_chk

Interview the SA to determine if the site uses a tool to compare system files (*.exe, *.bat, *.com, *.cmd and *.dll) on servers against a baseline, on a weekly basis. Note: A properly configured HBSS Policy Auditor 5.2 or later, File Integrity Monitor (FIM) module will meet the requirement for file integrity checking. The Asset module within HBSS does not meet this requirement.

Fix: F-42r1_fix

The site should use a tool to compare system files (*.exe, *.bat, *.com, *.cmd and *.dll) on servers against a baseline, on a weekly basis.

Checks: C-29r1_chk

Run the Computer Management Applet. Expand the “System Tools” object in the Tree window. Expand the “Shared Folders” object. Select the “Shares” object. Right click any user-created shares (ignore “Netlogon”, “Sysvol” and administrative shares; the system will prompt you if Properties are selected for administrative shares). Select Properties. Select the Share Permissions tab. If user-created file shares have not been reconfigured to remove ACL permissions from the “Everyone group”, then this is a finding. Note: On Application Servers, if regular users have write or delete permissions to shares containing application binary files (i.e. .exe, .dll, .cmd, etc.) this is a finding. Documentable: If shares created by applications require the "Everyone" group, this should be documented with the IAO.

Fix: F-59r1_fix

Remove permissions from the Everyone group from locally-created file shares and assign them to authorized groups.

Checks: C-7893r1_chk

Interview the SA to determine if there is a host-based Intrusion Detection System on each server. Severity Override: This finding can be downgraded to a Category III, if there is an active JIDS or Firewall protecting the network. Note: If the HIPS component of HBSS is installed and active on the host and the Alerts of blocked activity are being logged and monitored, this will meet the requirement of this finding. Note: A HID device is not required on a system that has the role as the Network Intrusion Device (NID). However, this exception needs to be documented with the site IAO.

Fix: F-43r1_fix

Install a host-based Intrusion Detection System on each server

Checks: C-162r1_chk

The policy value for Computer Configuration -> Administrative Templates -> System -> Logon “Always Wait for the Network at Computer Startup and Logon” will be set to “Enabled”. If the following registry value doesn’t exist or its value is not set to 1, then this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Subkey: \Software\Policies\Microsoft\Windows NT\CurrentVersion\Winlogon\ Value Name: SyncForegroundPolicy Type: REG_DWORD Value: 1

Fix: F-127r1_fix

Configure the system to wait for complete network initialization before allowing a user to log on. This is done by setting the policy value for Computer Configuration -> Administrative Templates -> System -> Logon “Always Wait for the Network at Computer Startup and Logon” to “Enabled”.

Checks: C-546r1_chk

If the following registry value doesn’t exist or its value is not set to 1, then this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Subkey: \Software\Policies\Microsoft\Messenger\Client\ Value Name: PreventRun Type: REG_DWORD Value: 1 Documentable Explanation: If the site has a requirement for Windows Messaging and meets the conditions of the Instant Messaging STIG this needs to be documented with the IAO.

Fix: F-5827r1_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Messenger “Do Not Allow Windows Messenger to be Run” to “Enabled”.

Checks: C-547r1_chk

If the following registry value doesn’t exist or its value is not set to 1, then this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Subkey: \Software\Policies\Microsoft\Messenger\Client\ Value Name: PreventAutoRun Type: REG_DWORD Value: 1 Documentable Explanation: If the site has a requirement for Windows Messaging and meets the conditions of the Instant Messaging STIG this needs to be documented with the IAO.

Fix: F-5828r1_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Messenger “Do Not Automatically Start Windows Messenger Initially” to “Enabled”.

Checks: C-504r1_chk

Using the DUMPSEC utility: Select “Dump Users as Table” from the “Report” menu. Select the available fields in the following sequence, and click on the “Add” button for each entry: UserName SID PswdRequired PswdExpires LastLogonTime AcctDisabled Groups If the HelpAssistant or Support_388945a0 accounts have not been disabled, then this is a finding.

Fix: F-5804r1_fix

Configure the system to disable restricted accounts such as HelpAssistant or Support_388945a0.

Checks: C-167r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “Devices: Allow Undock Without Having to Log On” is not set to ” Disabled”, then this is a finding. The policy referenced configures the following registry value: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \Software\Microsoft\Windows\CurrentVersion\Policies\System Value Name: UndockWithoutLogon Value Type: REG_DWORD Value: 0

Fix: F-130r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> “Devices: Allow Undock Without Having to Log On” to “Disabled”.

Checks: C-502r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “Domain Member: Require Strong (Windows 2000 or Later) Session Key” is not set to “Enabled”, then this is a finding. The policy referenced configures the following registry value: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \System\CurrentControlSet\Services\Netlogon\Parameters\ Value Name: RequireStrongKey Value Type: REG_DWORD Value: 1 Warning: This setting may prevent a system from being joined to a domain if not configured consistently between systems.

Fix: F-5801r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> “Domain Member: Require Strong (Windows 2000 or Later) Session Key” to “Enabled”.

Checks: C-503r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “Interactive logon: Require domain controller authentication to unlock workstation” is not set to “Enabled”, then this is a finding. The policy referenced configures the following registry value: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \Software\Microsoft\Windows NT\CurrentVersion\Winlogon\ Value Name: ForceUnlockLogon Value Type: REG_DWORD Value: 1

Fix: F-5802r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> “Interactive logon: Require domain controller authentication to unlock workstation” to “Enabled”.

Checks: C-171r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “Network access: Do not allow storage of credentials or .NET passports for network authentication” is not set to “Enabled”, then this is a finding. The policy referenced configures the following registry value: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \System\CurrentControlSet\Control\Lsa\ Value Name: DisableDomainCreds Value Type: REG_DWORD Value: 1

Fix: F-132r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> “Network access: Do not allow storage of credentials or .NET passports for network authentication” to “Enabled”.

Checks: C-172r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “Network access: Let everyone permissions apply to anonymous users” is not set to “Disabled”, then this is a finding. The policy referenced configures the following registry value: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \System\CurrentControlSet\Control\Lsa\ Value Name: EveryoneIncludesAnonymous Value Type: REG_DWORD Value: 0

Fix: F-133r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> “Network access: Let everyone permissions apply to anonymous users” to “Disabled”.

Checks: C-174r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “Network access: Sharing and security model for local accounts” is not set to “Classic - local users authenticate as themselves”, then this is a finding. The policy referenced configures the following registry value: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \System\CurrentControlSet\Control\Lsa\ Value Name: ForceGuest Value Type: REG_DWORD Value: 0

Fix: F-134r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> “Network access: Sharing and security model for local accounts” to “Classic - local users authenticate as themselves”.

Checks: C-184r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “Network security: Force logoff when logon hours expire” is not set to “Enabled”, then this is a finding.

Fix: F-142r1_fix

Configure the system to log off users when their allowed logon hours expire.

Checks: C-14464r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “Network security: LDAP client signing requirements” is not set to at least “Negotiate signing”, then this is a finding. The policy referenced configures the following registry value: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \System\CurrentControlSet\Services\LDAP\ Value Name: LDAPClientIntegrity Value Type: REG_DWORD Value: 1

Fix: F-143r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> “Network security: LDAP client signing requirements” to “Negotiate signing” at a minimum.

Checks: C-187r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “Network security: Minimum session security for NTLM SSP based (including secure RPC) clients” is not set to “Require NTLMv2 session security”, ”Require 128-bit encryption”, ”Require Message Integrity”, and ”Require Message Confidentiality”, then this is a finding. The policy referenced configures the following registry value: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \System\CurrentControlSet\Control\Lsa\MSV1_0\ Value Name: NTLMMinClientSec Value Type: REG_DWORD Value: 537395248 Warnings: Microsoft warns that setting these may prevent the client from communicating with legacy servers that do not support them. “Require NTLMv2 session security” will prevent authentication, if the “Network security: LAN Manager Authentication level” is set to permit NTLM or LM authentication. Documentable Explanation: If these settings need to be modified in a mixed Windows environment, the changes should be documented with the IAO.

Fix: F-145r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> “Network security: Minimum session security for NTLM SSP based (including secure RPC) clients” to “Require NTLMv2 session security”, ”Require 128-bit encryption”, ”Require Message Integrity”, and ”Require Message Confidentiality” (all options selected).

Checks: C-202r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing” is not set to “Enabled”, then this is a finding. The policy referenced configures the following registry value: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \System\CurrentControlSet\Control\Lsa\ Value Name: FIPSAlgorithmPolicy Value Type: REG_DWORD Value: 1 Warning: Clients with this setting enabled will not be able to communicate via digitally encrypted or signed protocols with servers that do not support these algorithms. Both the browser and web server must be configured to use TLS, or the browser will not be able to connect to a secure site.

Fix: F-5681r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> “System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing” to “Enabled”.

Checks: C-31r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “System objects: Default owner for object created by members of the Administrators group” is not set to “Object creator”, then this is a finding. The policy referenced configures the following registry value: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \System\CurrentControlSet\Control\Lsa\ Value Name: NoDefaultAdminOwner Value Type: REG_DWORD Value: 1

Fix: F-60r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> “System objects: Default owner for object created by members of the Administrators group” to “Object creator”.

Checks: C-203r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “System Object: Require Case Insensitivity for Non-Windows Subsystems” is not set to “Enabled”, then this is a finding. The policy referenced configures the following registry value: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \System\CurrentControlSet\Control\Session Manager\Kernel\ Value Name: ObCaseInsensitive Value Type: REG_DWORD Value: 1

Fix: F-5682r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> “System Object: Require Case Insensitivity for Non-Windows Subsystems” to “Enabled”.

Checks: C-1738r1_chk

If the following registry value doesn’t exist or its value is not set to 1, then this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Subkey: \Software\Policies\Microsoft\Conferencing\ Value Name: NoRDS Type: REG_DWORD Value: 1

Fix: F-5908r1_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> NetMeeting “Disable remote Desktop Sharing” to “Enabled".

Checks: C-32895r1_chk

If the following registry value doesn’t exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Subkey: \Software\Policies\Microsoft\Windows NT\Terminal Services\ Value Name: fSingleSessionPerUser Type: REG_DWORD Value: 1 Documentable Explanation: If the system has the role as a Terminal/Remote Desktop Server or the site is using remote desktop services for remote administration, this requirement needs to be documented with the IAO.

Fix: F-5918r1_fix

2003 - Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Terminal Services “Restrict Terminal Server users to a Single Remote Session” to “Enabled”.

Checks: C-1801r1_chk

If the following registry value doesn’t exist or its value is not set to 1, then this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Subkey: \Software\Policies\Microsoft\Windows NT\Terminal Services\ Value Name: MaxInstanceCount Type: REG_DWORD Value: 1 Documentable Explanation: If the system has the role as a Terminal Server, or the site is using terminal services for remote administration this requirement needs to be documented with the IAO.

Fix: F-5919r1_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Terminal Services “Limit Number of Connections” to “Enabled”, and the value “TS maximum connections allowed” to no more than “1”.

Checks: C-40665r1_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Subkey: \Software\Policies\Microsoft\Windows NT\Terminal Services\ Value Name: MinEncryptionLevel Type: REG_DWORD Value: 3

Fix: F-5923r2_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Terminal Services -> Encryption and Security “Set Client Connection Encryption Level” to “Enabled” and select “High Level” for the “Encryption Level”.

Checks: C-1899r1_chk

If the following registry value doesn’t exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Subkey: \Software\Policies\Microsoft\Windows NT\Terminal Services\ Value Name: PerSessionTempDir Type: REG_DWORD Value: 1

Fix: F-5925r1_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Terminal Services -> Temporary Folders “Do Not Use Temp Folders per Session” to “Disabled”.

Checks: C-1906r1_chk

If the following registry value doesn’t exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Subkey: \Software\Policies\Microsoft\Windows NT\Terminal Services\ Value Name: DeleteTempDirsOnExit Type: REG_DWORD Value: 1

Fix: F-5928r1_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Terminal Services -> Temporary Folders “Do Not Delete Temp Folder upon Exit” to “Disabled”.

Checks: C-32896r1_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Subkey: \Software\Policies\Microsoft\Windows NT\Terminal Services\ Value Name: MaxDisconnectionTime Type: REG_DWORD Value: 0x0000ea60 (60000)

Fix: F-34274r1_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Terminal Services -> Sessions “Set Time Limit for Disconnected Sessions” to “Enabled”, and the “End a disconnected session” to “1 minute".

Checks: C-39128r1_chk

If the following registry value does not exist or its value is set to 0 or greater than 15 minutes, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Subkey: \Software\Policies\Microsoft\Windows NT\Terminal Services\ Value Name: MaxIdleTime Type: REG_DWORD Value: 0x000dbba0 (900000) or less but not 0

Fix: F-34276r1_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Terminal Services -> Sessions “Set time limit for active but idle Terminal Services sessions” to “Enabled”, and the “Idle session limit” to 15 minutes or less, excluding 0 which equates to “Never”.

Checks: C-1925r1_chk

If the following registry value doesn’t exist or its value is not set to 1, then this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Subkey: \Software\Policies\Microsoft\Windows NT\Terminal Services\ Value Name: fReconnectSame Type: REG_DWORD Value: 1

Fix: F-5933r1_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Terminal Services -> Sessions “Allow Reconnection from Original Client Only” to “Enabled”.

Checks: C-1929r1_chk

If the following registry value doesn’t exist or its value is not set to 1, then this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Subkey: \Software\Policies\Microsoft\Windows NT\Terminal Services\ Value Name: fResetBroken Type: REG_DWORD Value: 1

Fix: F-5936r1_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Terminal Services -> Sessions “Terminate Session When Time Limits are Reached” to “Enabled”.

Checks: C-40666r1_chk

Review the registry. If the following registry value does not exist, this is not a finding (This is the expected result from configuring the policy as outlined in the Fix section). If the following registry value does exist but is not configured as specified, this is a finding. Registry Hive: HKEY_LOCAL_MACHINE Subkey: \Software\Microsoft\Windows\CurrentVersion\Policies\system\ Value Name: DisableBkGndGroupPolicy Type: REG_DWORD Value: 0

Fix: F-5684r1_fix

Configure the system to require Group Policy background refresh by setting the policy value for Computer Configuration -> Administrative Templates -> System -> Group Policy “Turn Off Background Refresh of Group Policy” to “Disabled”.

Checks: C-29882r1_chk

If the following registry value doesn’t exist or is not configured as specified this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Subkey: \Software\Policies\Microsoft\Windows NT\Terminal Services\ Value Name: fAllowUnsolicited Type: REG_DWORD Value: 0

Fix: F-6776r1_fix

Configure the system to prevent unsolicited remote assistance offers by setting the policy value for Computer Configuration -> Administrative Templates -> System -> Remote Assistance “Offer Remote Assistance” to “Disabled”.

Checks: C-57135r1_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Policies\Microsoft\PCHealth\ErrorReporting\ Value Name: DoReport Type: REG_DWORD Value: 1

Fix: F-61461r1_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Internet Communication Management -> Internet Communication settings -> "Turn off Windows Error Reporting" to "Disabled".

Checks: C-220r1_chk

The policy value for Computer Configuration -> Administrative Templates -> System -> Printers “Disallow Installation of Printers Using Kernel-mode Drivers” will be set to “Enabled”. If the following registry value doesn’t exist or its value is not set to 1, then this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Subkey: \Software\Policies\Microsoft\Windows NT\Printers\ Value Name: KMPrintersAreBlocked Type: REG_DWORD Value: 1 Note: This setting will prevent some applications from installing PDF print drivers.

Fix: F-5698r1_fix

Configure the system to prevent it from allowing the installation of kernel-mode drivers by setting the policy value for Computer Configuration -> Administrative Templates -> Printers “Disallow Installation of Printers Using Kernel-mode Drivers” to “Enabled”.

Checks: C-221r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “MSS: (SafeDllSearchMode) Enable Safe DLL search mode (recommended)” is not set to “Enabled”, then this is a finding. The policy referenced configures the following registry value: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \System\CurrentControlSet\Control\Session Manager\ Value Name: SafeDllSearchMode Value Type: REG_DWORD Value: 1

Fix: F-5699r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> “MSS: (SafeDllSearchMode) Enable Safe DLL search mode (recommended)” to “Enabled”.

Checks: C-46902r1_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Subkey: \Software\Policies\Microsoft\WindowsMediaPlayer\ Value Name: DisableAutoupdate Type: REG_DWORD Value: 1

Fix: F-45023r1_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Media Player -> "Prevent Automatic Updates" to "Enabled".

Checks: C-2049r1_chk

If the following registry value doesn’t exist or its value is not set to 1, then this is a finding: Registry Hive: HKEY_Current_User Subkey: \Software\Policies\Microsoft\WindowsMediaPlayer\ Value Name: PreventCodecDownload Type: REG_DWORD Value: 1

Fix: F-5993r1_fix

Configure the policy value for User Configuration -> Administrative Templates -> Windows Components -> Windows Media Player -> Playback “Prevent Codec Download” to “Enabled”.

Checks: C-57133r2_chk

Run "Services.msc". If services listed below are found, that are not disabled, and the site does not have documented exceptions for these, this is a finding. Alerter Application Layer Gateway Service Application Management ASP .NET State Service Certificate Services Client Service for NetWare ClipBook Cluster Service COM+ System Application DHCP Server Distributed Link Tracking Client Distributed Link Tracking Server Distributed Transaction Coordinator Fax Service File Server for Macintosh FTP Publishing Service Help and Support HTTP SSL Human Interface Device Access IAS Jet Database Access IIS Admin Service IMAPI CD-Burning COM Service Indexing Service Infrared Monitor Internet Authentication Service IP Version 6 Helper Service License Logging Service Message Queuing Message Queuing Down Level Clients Message Queuing Triggers Messenger Microsoft POP3 Service MSSQL$UDDI MSSQLServerADHelper .NET Framework Support Service NetMeeting Remote Desktop Sharing Network DDE Network DDE DSDM Network News Transport Protocol (NNTP) Portable Media Serial Number Print Server for Macintosh Print Spooler Remote Access Auto Connection Manager Remote Access Connection Manager Remote Desktop Help Session Manager Remote Installation Remote Server Manager Remote Server Monitor Remote Storage Notification Remote Storage Server Resultant Set of Policy Provider Routing and Remote Access SAP Agent Secondary Logon Shell Hardware Detection Simple Mail Transport Protocol (SMTP) Simple TCP/IP Services Single Instance Storage Groveler SNMP Service SNMP Trap Service Special Administration Console Helper Task Scheduler - See separate vulnerability WINSV-000106/V-30037 TCP/IP Print Server Telephony Telnet Terminal Services Terminal Services Licensing Terminal Services Session Directory Themes Trivial FTP Daemon Uninterruptible Power Supply Upload Manager Virtual Disk Service WebClient Web Element Manager Windows Audio Windows Firewall/Internet Connection Sharing (ICS) Windows Image Acquisition (WIA) Windows Internet Name Service (WINS) Windows Media Services Windows System Resource Manager WinHTTP Web Proxy Auto-Discovery Service Wireless Configuration World Wide Web Publishing Service

Fix: F-6001r1_fix

Configure the system to disable any services that are not required.

Checks: C-3244r2_chk

The site will have a policy that requires servers and other critical systems be reviewed on a daily basis to identify possible security breaches and weakness. This can be accomplished with the use of monitoring software or other utilities for this purpose.

Fix: F-6578r1_fix

Create a site policy that mandates review of audit logs.

Checks: C-222r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “Network security: Minimum session security for NTLM SSP based (including secure RPC) servers” is not set to “Require NTLMv2 session security”, ”Require 128-bit encryption”, ”Require Message Integrity”, and ”Require Message Confidentiality”, then this is a finding. The policy referenced configures the following registry value: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \System\CurrentControlSet\Control\Lsa\MSV1_0\ Value Name: NTLMMinServerSec Value Type: REG_DWORD Value: 537395248 Warnings: Microsoft warns that setting these may prevent the server from communicating with legacy clients that do not support them. Warning: “Require NTLMv2 session security” will prevent authentication, if the “Network security: LAN Manager Authentication level” is set to permit NTLM or LM authentication. Documentable Explanation: If the required settings must be modified to support operation in a mixed Windows environment, then this should be documented with the IAO.

Fix: F-5700r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> “Network security: Minimum session security for NTLM SSP based (including secure RPC) servers” to “Require NTLMv2 session security”, ”Require 128-bit encryption”, ”Require Message Integrity”, and ”Require Message Confidentiality” (all options selected).

Checks: C-35r1_chk

Verify that the site is applying all security-related patches released by Microsoft. Determine the local site method for doing this (e.g., connection to a WSUS server, local procedure, etc.). Severity Override: If any of the patches not installed are Microsoft ‘Critical’, then the category code should be elevated to ‘1’. Note: If a penetration scan has been run on the network, it will report findings if security-related updates are not applied. Then, this check may be marked as “Not Applicable”. Some applications (such as DMS and GCSS) use a system release process to keep systems current. If this is the case, then these systems should be at the current release.

Fix: F-63r1_fix

Apply all Microsoft security-related patches to the Windows system.

Checks: C-51797r3_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for "Domain Controller: LDAP Server signing requirements" is not set to "Require signing", this is a finding. The policy referenced configures the following registry value: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \System\CurrentControlSet\Services\NTDS\Parameters\ Value Name: LDAPServerIntegrity Value Type: REG_DWORD Value: 2 Documentable Explanation: If LDAP Signing is not supported by a client, service or application, this must be documented with the IAO with supporting vendor information.

Fix: F-53591r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Domain controller: LDAP server signing requirements" to "Require signing".

Checks: C-32759r2_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “System cryptography: Force strong key protection for user keys stored in the computer” is not set to “User must enter a password each time they use a key”, this is a finding. The policy referenced configures the following registry value: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \Software\Policies\Microsoft\Cryptography\ Value Name: ForceKeyProtection Value Type: REG_DWORD Value: 2

Fix: F-28834r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> “System cryptography: Force strong key protection for user keys stored in the computer” to “User must enter a password each time they use a key”.

Checks: C-350r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “System Settings: Use Certificate Rules on Windows Executables for Software Restriction Policies” is not set to “Enabled”, then this is a finding. The policy referenced configures the following registry value: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \Software\Policies\Microsoft\Windows\Safer\CodeIdentifiers\ Value Name: AuthenticodeEnabled Value Type: REG_DWORD Value: 1

Fix: F-5742r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> “System Settings: Use Certificate Rules on Windows Executables for Software Restriction Policies” to “Enabled”.

Checks: C-1934r1_chk

If the following registry value doesn’t exist or its value is not set to 1, then this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Subkey: \Software\Policies\Microsoft\Windows NT\Terminal Services\ Value Name: fEncryptRPCTraffic Type: REG_DWORD Value: 1

Fix: F-5938r1_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Terminal Services -> Encryption and Security -> RPC Security Policy “Secure Server (Require Security)” to “Enabled”.

Checks: C-32762r1_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Subkey: Software\Policies\Microsoft\Windows\Group Policy\{35378EAC-683F-11D2-A89A-00C04FBBCFA2} Value Name: NoGPOListChanges Type: REG_DWORD Value: 0

Fix: F-28955r1_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Group Policy “Registry Policy Processing” to “Enabled” and select the option “Process even if the Group Policy objects have not changed”.

Checks: C-40668r1_chk

Open a command prompt. Execute “Dcomcnfg.exe”. In the “Component Services” window, navigate to Component Services -> Computer -> My Computer Right-click “My Computer” and select “Properties”. Select the “Default Properties” tab. If the “Default Authentication Level” is set to “None” or “Call”, this is a finding.

Fix: F-36078r1_fix

Fortify DCOMs default permissions. This should be thoroughly tested to verify DCOM objects continue to function under tightened security. Open a command prompt. Execute “Dcomcnfg.exe”. In the “Component Services” window, navigate to Component Services -> Computer -> My Computer Right-click “My Computer” and select “Properties”. Select the “Default Properties” tab. Select a “Default Authentication Level” other than “None” or “Call”. For sensitive systems, an authentication level of “Packet Privacy” is recommended. Click OK.

Checks: C-3103r1_chk

·Using the Registry Editor, go to the following Registry key: HKLM\Software\Classes\Appid(inherited by all subkeys) Administrators Full SYSTEM Full Users Read ·If any account other than Administrators and System has greater than “read” access, then this would be a finding. ·Select each subkey and verify that it is inheriting the same permissions. ·If any subkey has permissions that are less strict than those above, then this would be a finding.

Fix: F-6513r1_fix

Fortify DCOMs AppId permissions. Any changes should be thoroughly tested so objects continue to function under tightened security. - Open the Registry Editor. - Navigate to HKEY_LOCAL_MACHINE\Software\Classes\Appid. - Select the application that generated this vulnerability. - Set the permissions for standard (non-privileged) user accounts or groups to Read only.

Checks: C-3107r1_chk

·Using the Registry Editor, go to the following Registry key: HKLM\Software\Classes\Appid ·View each subkey in turn and verify that the RunAs value has not been added. ·If any subkey has a RunAs value, then this would be a finding. Note: Windows components that have default Runas values such as Interactive User do not need to be changed. Windows components that have had a Runas value added or changed and non-Windows COM objects added to the system with Runas values need to be reviewed.

Fix: F-6517r1_fix

Remove any RunAs values from DCOM objects in the Registry.

Checks: C-3108r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “Domain Member: Digitally encrypt or sign secure channel data (always)” is not set to “Enabled”, then this is a finding. The policy referenced configures the following registry value: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \System\CurrentControlSet\Services\Netlogon\Parameters\ Value Name: RequireSignOrSeal Value Type: REG_DWORD Value: 1

Fix: F-6518r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> “Domain Member: Digitally encrypt or sign secure channel data (always)” to “Enabled”.

Checks: C-3110r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “Microsoft Network Client: Digitally sign communications (always)” is not set to “Enabled”, then this is a finding. The policy referenced configures the following registry value: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \System\CurrentControlSet\Services\LanmanWorkstation\Parameters\ Value Name: RequireSecuritySignature Value Type: REG_DWORD Value: 1

Fix: F-6519r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> “Microsoft Network Client: Digitally sign communications (always)” to “Enabled”.

Checks: C-3112r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> Security Options. If the value for “Microsoft Network Server: Digitally sign communications (always)” is not set to “Enabled”, then this is a finding. The policy referenced configures the following registry value: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \System\CurrentControlSet\Services\LanManServer\Parameters\ Value Name: RequireSecuritySignature Value Type: REG_DWORD Value: 1

Fix: F-6520r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> “Microsoft Network Server: Digitally sign communications (always)” to “Enabled”.

Checks: C-51793r2_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Account Policies -> Password Policy. If the value for the "Minimum password length" is less than 14 characters, this is a finding.

Fix: F-53585r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Account Policies -> Password Policy -> "Minimum password length" to at least "14" characters.

Checks: C-38498r1_chk

Verify all account passwords expire. The following are exempt from this requirement: Built-in Administrator account Application accounts Domain accounts requiring smart card (CAC) Using the DUMPSEC utility: Select “Dump Users as Table” from the “Report” menu. Select the available fields in the following sequence, and click on the “Add” button for each entry: UserName SID PswdRequired PswdExpires PswdLastSetTime LastLogonTime AcctDisabled Groups If any accounts, other than the exceptions noted, have a “No” in the “PswdExpires” column, then this is a finding. Note: The following command can be used on Windows Active Directory if DumpSec cannot be run: Open a Command Prompt. Enter “Dsquery user -limit 0 | Dsget user -dn -pwdneverexpires”. This will return a list of User Accounts with Yes/No for Pwdneverexpires. If any accounts, other than the exceptions noted, have "Yes", then this is a finding. The results can be directed to a text file by adding “> filename.txt” at the end of the command. Documentable Explanation: Accounts meeting the requirements for allowable exceptions should be documented with the IAO.

Fix: F-6527r1_fix

Configure all information systems to expire passwords.

Checks: C-46040r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Expand the "Local Policies" object and select "Audit Policy". Compare the settings in the Policy window with the following. If system does not audit the events listed below, this is a finding. Audit account logon events - Success, Failure Audit account management - Success, Failure Audit directory service access - Failure Audit logon events - Success, Failure Audit object access - Failure Audit policy change - Success Audit privilege use - Failure Audit system events - Success

Fix: F-43430r2_fix

Configure the system to audit the following categories as outlined. Audit account logon events - Success, Failure Audit account management - Success, Failure Audit directory service access - Failure Audit logon events - Success, Failure Audit object access - Failure Audit policy change - Success Audit privilege use - Failure Audit system events - Success

Checks: C-48685r2_chk

Refer to the AD database location obtained in check V-8316. Note the logical drive (e.g., C:) on which the files are located. Determine if the server is currently providing file sharing services to users with the following command. Enter "net share" at a command prompt. Note the logical drive(s) or file system partition for any site-created data shares. Ignore all system shares (e.g., Windows NETLOGON, SYSVOL, and administrative shares ending in $). User shares that are hidden (ending with $) should not be ignored. If user shares are located on the same logical partition as the directory server data files, this is a finding.

Fix: F-47808r2_fix

Ensure files owned by users are stored on a different logical partition then the directory server data files.

Checks: C-14106r1_chk

This check examines only the Windows Support Tools. If none of the tools are installed, then this check is not applicable. 1. Start Windows Explorer. 2. Right-click the “My Computer” item and select “Search…” 3. Type “Support" in the file name field. 4. Select “Local Hard Drives” in the “Look in:” field. 5. Click the Search [or Search Now] button. 6. Record the location for the “Support Tools” directory. The SA may have installed the Support Tools under an alternate name. If the default directory is not found, ask the SA. 7. If the directory is not found and the SA confirms that the Support Tools are not installed, then this check is not applicable. 8. Using the recorded location, compare the current ACL of the Support Tools directory to the following: Windows Support Tools Permissions: ...\Support Tools :Administrators, SYSTEM :Full Control (F) : [IAO-approved users \ user groups] :Read, Read & Execute, List Folder Contents 9. If the folder permissions are not at least as restrictive as required, then this is a finding.

Fix: F-28705r1_fix

Configure the directory service as follows: Windows Support Tools Permissions: ...\Support Tools :Administrators, SYSTEM :Full Control (F) : [IAO-approved users \ user groups] :Read, Read & Execute, List Folder Contents

Checks: C-48689r3_chk

Determine if a time synchronization tool has been implemented on the Windows domain controller. If the Windows Time Service is used, verify the following registry values. If they are not configured as specified, this is a finding. Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \System\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient\ Value Name: Enabled Type: REG_DWORD Value: 1 Registry Path: \System\CurrentControlSet\Services\W32Time\Parameters\ Value Name: Type Type: REG_SZ Value: NT5DS (preferred), NTP, or Allsync If these Windows checks indicate a finding because the NtpClient is not enabled, determine if an alternate time synchronization tool is installed and enabled. If the Windows Time Service is not enabled and no alternate tool is enabled, this is a finding.

Fix: F-47812r3_fix

Ensure the Windows Time Service is configured as follows or install and enable another time synchronization tool. Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \System\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient\ Value Name: Enabled Type: REG_DWORD Value: 1 Registry Path: \System\CurrentControlSet\Services\W32Time\ Parameters\ Value Name: Type Type: REG_SZ Value: NT5DS (preferred), NTP, or Allsync

Checks: C-48691r2_chk

Run "services.msc" to display the Services console. Determine if any running services are application components. Examples of services indicating the presence of applications are: -DHCP Server for DHCP server -IIS Admin Service for IIS web server -Microsoft Exchange System Attendant for Exchange -MSSQLServer for SQL Server. If any application-related components have the "Started" status, this is a finding. Supplemental Notes: A Domain Name System (DNS) server integrated with the directory server (e.g., AD-integrated DNS) is an acceptable application. However, the DNS server must comply with the DNS STIG security requirements. Some directory servers utilize specialized web servers for administrative functions and databases for data management. These web and database servers are permitted as long as they are dedicated to directory server support and only administrative users have access to them.

Fix: F-47813r2_fix

Remove applications such as web, database, and email from the domain controller.

Checks: C-48694r3_chk

Run "services.msc" to display the Services console. Verify the Startup Type for the following Windows services: - Distributed File System (may be disabled if site is not utilizing) - DNS Client - File Replication Service - Intersite Messaging - Kerberos Key Distribution Center - Net Logon - Windows Time (not required if another time synchronization tool is implemented to start automatically) If the Startup Type for any of these services is not Automatic, this is a finding.

Fix: F-47816r3_fix

Ensure the following services that are critical for directory server operation are configured for automatic startup. - Distributed File System (may be disabled if site is not utilizing) - DNS Client - File Replication Service - Intersite Messaging - Kerberos Key Distribution Center - Net Logon - Windows Time (not required if another time synchronization tool is implemented to start automatically)

Checks: C-11570r1_chk

Interview the SA to determine if a backup administrator account exists and is stored with its password in a secure location.

Fix: F-13548r2_fix

Create and maintain a backup administrator account for emergency situations.

Checks: C-11571r1_chk

Interview the SA or IAM to determine if the site has a policy that requires the default and backup admin passwords to be changed at least annually or when any member of the administrative team leaves the organization.

Fix: F-13549r1_fix

Define a policy for required password changes for the default and backup admin account.

Checks: C-11572r1_chk

Interview the SA to determine the process for archiving audit logs. Audit logs are retained for at least one year; on systems containing sources and methods intelligence (SAMI) logs will be retained for five years.

Fix: F-13550r1_fix

Define a process for archiving audit logs as required.

Checks: C-11593r1_chk

If the following registry value doesn’t exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Subkey: \Software\Policies\Microsoft\Windows NT\Terminal Services\ Value Name: DisablePasswordSaving Type: REG_DWORD Value: 1

Fix: F-15528r1_fix

XP - Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Terminal Services-> Client “Do not allow passwords to be saved” to “Enabled”.

Checks: C-52019r2_chk

Prior to transition, IPv6 must not be installed. The following registry key indicates the IPv6 protocol has been installed. If it exists, this is a finding. Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \System\CurrentControlSet\Services\Tcpip6 See S0-C1-imp-1 of The Department of National Intelligence/Department of Defense (DoD) Internet Protocol version 6 (IPv6) Information Assurance Guidance for Milestone Objective 3 for additional information.

Fix: F-53903r2_fix

Uninstall the IPv6 protocol until a deliberate transition strategy has been implemented.

Checks: C-11762r1_chk

The site should have a local policy to ensure that passwords for application/service accounts are at least 15 characters in length and meet complexity requirements for all passwords. Application/service account passwords manually generated and entered by a system administrator must be changed at least annually or whenever a system administrator that has knowledge of the password leaves the organization. Interview the system administrators on their policy for application/service accounts. If it does not meet the above requirements, this is a finding. Using the DUMPSEC utility: Select “Dump Users as Table” from the “Report” menu. Select the available fields in the following sequence, and click on the “Add” button for each entry: UserName SID PswdRequired PswdExpires PswdLastSetTime LastLogonTime AcctDisabled Groups If any application accounts listed in the Dumpsec user report have a date older than one year in the “PwsdLastSetTime” column, then this is a finding. Note: The following command can be used on Windows 2003/2008 Active Directory if DumpSec cannot be run: Open a Command Prompt. Enter “Dsquery user -limit 0 -o rdn -stalepwd 365”. This will return a list of User Accounts with passwords older the one year.

Fix: F-13613r1_fix

Create application/service account passwords that are at least 15 characters in length and meet complexity requirements. Change application/service account passwords that are manually generated and entered by a system administrator at least annually or whenever an administrator with knowledge of the password leaves the organization.

Checks: C-48702r1_chk

With the assistance of the SA, NSO, or network reviewer as required, review the site network diagram(s) or documentation to determine the level of classification for the network(s) over which replication data is transmitted. Determine the classification level of the Windows domain controller. If the classification level of the Windows domain controller is higher than the level of the networks, review the site network diagram(s) and directory implementation documentation to determine if NSA-approved encryption is used to protect the replication network traffic. If the classification level of the Windows domain controller is higher than the level of the network traversed and NSA-approved encryption is not used, this is a finding.

Fix: F-47823r1_fix

Configure NSA-approved (Type 1) cryptography to protect the directory data in transit for directory service implementations at a classified confidentiality level that transfers replication data through a network cleared to a lower level than the data.

Checks: C-32057r2_chk

Use the following procedure to check a sample of accounts. 1. Open Active Directory Users and Computers. 2. Select the Users node. 3. For each user account sampled, right-click and select Properties. 4. Select the Account tab. 5. View the setting in Account Options area. 6. Verify that the option “Smart card is required for interactive logon” is checked.

Fix: F-28436r2_fix

Configure all user accounts including administrator accounts in Active Directory to enable the option “Smart card is required for interactive logon”.

Checks: C-34533r1_chk

Search for the file FrameworkService.exe (by default in the \Program Files\McAfee\Common Framework\ directory) and check that the version is 4 or above. AND verify that the Service "McAfee Framework Service" is running. If either of these conditions does not exist, then this is a finding.

Fix: F-30040r1_fix

Deploy the McAfee Agent as detailed in the CTO and in accordance with the DoD HBSS STIG.

Checks: C-16140r1_chk

Search all drives for *.p12 and *.pfx files. If any files with these extensions exist, then this is a finding. Documentable Explanation: This does not apply to server-based applications that have a requirement for .p12 certificate files (e.g., Oracle Wallet Manager). Some applications create files with extensions of .p12 that are NOT certificate installation files. Removal from systems of non-certificate installation files are not required. These should be documented with the IAO.

Fix: F-15775r1_fix

Remove any certificate installation files found on a system. Note: This does not apply to server-based applications that have a requirement for .p12 certificate files (e.g., Oracle Wallet Manager)

Checks: C-44722r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> User Rights Assignment. If the following accounts or groups are not defined for the "Deny log on as a batch job" right, this is a finding: Guests Group Support_388945a0

Fix: F-41022r2_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Deny log on as a batch job" to include the following. Guests Group Support_388945a0

Checks: C-44720r2_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> User Rights Assignment. If any accounts or groups are defined for the "Deny log on as a service" right, this is a finding.

Fix: F-41020r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Deny log on as a service" to include no entries (blank).

Checks: C-44718r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> User Rights Assignment. If the following accounts or groups are not defined for the "Deny log on locally" right, this is a finding: Guests Group Support_388945a0

Fix: F-41018r2_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Deny log on locally" to include the following. Guests Group Support_388945a0

Checks: C-44716r1_chk

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Navigate to Local Policies -> User Rights Assignment. If the following accounts or groups are not defined for the "Deny log on through Terminal Services" right, this is a finding: Everyone - If Terminal Services is not used by the organization. Guests - If Terminal Services is used by the organization.

Fix: F-41016r1_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Deny log on through Terminal Services" to include the following. If Terminal Services is not used by the organization, assign the Everyone group this right to prevent all access. If TS is used by the organization, assign the Guests group.

Checks: C-49673r2_chk

Run "Regedit". Navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters". Note the value for "Working Directory", typically "%SystemRoot%\ntfrs". Verify the permissions of the noted location. If the access control permissions of the FRS directory are not at least as restrictive as those below, this is a finding. FRS Directory Permissions: Administrators - Full Control (F) SYSTEM - Full Control (F)

Fix: F-50021r2_fix

Maintain the access control permissions for the FRS directory as outlined below. FRS Directory Permissions: Administrators - Full Control (F) SYSTEM - Full Control (F)

Checks: C-49223r1_chk

Verify the DoD Root CA 2 certificate is installed as a Trusted Root Certification Authority using the Certificates MMC snap-in. Run “MMC” Select “File”, “Add/Remove Snap-in…” Click “Add…” Select “Certificates”, click “Add” Select “Computer account”, click “Next” Select “Local computer: (the computer this console is running on)”, click “Finish” Click “Close” Click “OK” Expand “Certificates” and navigate to “Trusted Root Certification Authorities\Certificates” Search for “DoD Root CA 2” under “Issued To” in the center pane If there is no entry for “DoD Root CA 2” this is a finding. Select DoD Root CA 2 Right click and select “Open” Select the “Details” Tab Scroll to the bottom and select “Thumbprint Algorithm” Verify the Value is “sha1”, If the value for “Thumbprint Algorithm” is not “sha1” this is a finding. Next select “Thumbprint” If the value for the “Thumbprint” field is not “8C:94:1B:34:EA:1E:A6:ED:9A:E2:BC:54:CF:68:72:52:B4:C9:B5:61” this is a finding. The thumbprint referenced applies to NIPRNet, see PKE documentation for other networks.

Fix: F-48783r1_fix

Install the DoD Root CA 2 certificate. The InstallRoot tool is available on IASE at http://iase.disa.mil/pki-pke/function_pages/tools.html.

Checks: C-49165r1_chk

Verify the DoD Root CA 2 certificate issued by DoD Interoperability Root CA 1 is installed on NIPRNet systems as an Untrusted Certificate using the Certificates MMC snap-in. Run “MMC” Select “File”, “Add/Remove Snap-in…” Click “Add…” Select “Certificates”, click “Add” Select “Computer account”, click “Next” Select “Local computer: (the computer this console is running on)”, click “Finish” Click “Close” Click “OK” Expand “Certificates” and navigate to “Untrusted Certificates\Certificates” Search in the right pane for “DoD Root CA 2” under “Issued To” with “DoD Interoperability Root CA 1” as “Issued By” If there is no entry for “DoD Root CA 2”, this is a finding. Select “DoD Root CA 2” Right click and select “Open” Select the “Details” Tab Scroll to the bottom and select “Thumbprint Algorithm” Verify the Value is “sha1”, If the value for “Thumbprint Algorithm” is not “sha1”, this is a finding. Next select “Thumbprint” If the value for the “Thumbprint” field is not “99:c4:94:ec:e4:fc:09:3e:ee:13:c4:d6:5b:1b:1e:01:b9:b5:d4:34”, this is a finding.

Fix: F-48591r1_fix

Install the DoD Interoperability Root CA 1 to DoD Root CA 2 cross certificate on NIPRNet systems only. The FBCA Cross-Certificate Remover tool is available on IASE at http://iase.disa.mil/pki-pke/function_pages/tools.html

Checks: C-48721r1_chk

Verify a supervisor or administrator password is set in the BIOS or system controller. If a password is not configured, this is a finding.

Fix: F-47842r1_fix

Access the system's BIOS or system controller. Configure a supervisor/administrator password.

Checks: C-49488r4_chk

This is applicable to unclassified systems, for other systems this is NA. Verify the "Popular Software" Protection Profile has been implemented. This implements mitigations to protect Internet Explorer, Office programs, and numerous third party applications. If the following registry subkeys do not exist, this is a finding. Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Microsoft\EMET\ The subkeys will include the following: 7z.exe 7zfm.exe 7zg.exe acrobat.exe acrord32.exe chrome.exe communicator.exe excel.exe firefox.exe foxit reader.exe googletalk.exe iexplore.exe infopath.exe itunes.exe java.exe javaw.exe javaws.exe lync.exe mirc.exe msaccess.exe mspup.exe ois.exe opera.exe outlook.exe photoshop.exe pidgen.exe plugin-container.exe powerpnt.exe pptview.exe quicktimeplayer.exe rar.exe realconverter.exe realplay.exe safari.exe skydrive.exe skype.exe thunderbird.exe unrar.exe visio.exe vlc.exe vpreview.exe winamp.exe windowslivewriter.exe winrar.exe winword.exe winzip32.exe winzip64.exe wlmail.exe wlxphotogallery.exe wmplayer.exe wordpad.exe Additional details of the implementation can be viewed with the following. Open a command prompt. Navigate to the EMET installation directory, typically \Program Files\EMET. Execute the following command - "EMET_Conf --list".

Fix: F-49712r3_fix

This is applicable to unclassified systems, for other systems this is NA. Open a command prompt. Navigate to the EMET installation directory, typically \Program Files\EMET. Execute the following command -'EMET_Conf --import "deployment\protection profiles\popular software.xml"' The Enhanced Mitigation Experience Toolkit must be installed on the system to make this setting available.

Checks: C-46266r7_chk

This is applicable to unclassified systems, for other systems this is NA. Open EMET in Programs\Enhanced Mitigation Experience Toolkit. Verify under System Status that Data Execution Prevention (DEP) is configured to "Application Opt Out". Alternately verify in System Properties. Select "System" in Control Panel. Select the "Advanced" tab. Click "Settings" in the "Performance" section. Select the "Data Execution Prevention" tab. Verify "Turn on DEP for all programs and services except those I select:" is selected. If DEP is not configured as specified, this is a finding. Applications that do not function properly due to this setting, and are opted out, must be documented with the ISSO.

Fix: F-43653r7_fix

This is applicable to unclassified systems, for other systems this is NA. Open EMET in Programs\Enhanced Mitigation Experience Toolkit. Configure Data Execution Prevention (DEP) under System Status to "Application Opt Out". The Enhanced Mitigation Experience Toolkit must be installed on the system to make this setting available. Document applications that do not function properly due to this setting, and are opted out, with the ISSO. Alternately configure in System Properties. Select "System" in Control Panel. Select the "Advanced" tab. Click "Settings" in the "Performance" section. Select the "Data Execution Prevention" tab. Select "Turn on DEP for all programs and services except those I select:". Applications that are opted out are configured in the window below this selection.

Checks: C-51819r2_chk

Verify the auditing configuration for group policy objects. Use of the Group Policy Management console is recommended. If it is not installed on a system, group policies must be identified and auditing verified using Active Directory Sites and Services (dssite.msc) and Active Directory Users and Computers (dsa.msc). Open "Group Policy Management". (Available from various menus, or run "gpmc.msc".) Navigate to "Group Policy Objects" in the domain being reviewed (Forest > Domains > Domain). For each Group Policy object: Select the Group Policy Object item in the left pane. Select the Delegation tab in the right pane. Select the Advanced button. Select the Advanced button again and then the Auditing tab. If the audit settings for any Group Policy object are not at least as inclusive as those below, this is a finding. Type - Fail Name - Everyone Access - Full Control Apply to - groupPolicyContainer objects The three Success types listed below are defaults Inherited From the Parent Object. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference, various Properties selections may also exist by default. Type - Success Name - Everyone Access - Special Inherited From - Parent Object Apply to - groupPolicyContainer objects (Access - Special = Permissions: Write All Properties, Modify Permissions) Two instances with the following summary information will be listed. Type - Success Name - Everyone Access - Write Property Inherited From - Parent Object Apply to - Organization Unit objects

Fix: F-53615r1_fix

Configure the audit settings for Group Policy objects to include the following. Type - Fail Name - Everyone Access - Full Control Apply to - groupPolicyContainer objects The three Success types listed below are defaults Inherited From the Parent Object. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference, various Properties selections may also exist by default. Type - Success Name - Everyone Access - Special Inherited From - Parent Object Apply to - groupPolicyContainer objects (Access - Special = Permissions: Write All Properties, Modify Permissions) Two instances with the following summary information will be listed. Type - Success Name - Everyone Access - Write Property Inherited From - Parent Object Apply to - Organization Unit objects

Checks: C-48745r1_chk

Verify the auditing configuration for the Domain object. Open "Active Directory Users and Computers". (Available from various menus or run "dsa.msc".) Ensure Advanced Features is selected in the View menu. Select the domain being reviewed in the left pane. Right click the domain name and select Properties. Select the Security tab. Select the Advanced button and then the Auditing tab. If the audit settings on the Domain object are not at least as inclusive as those below, this is a finding. Type - Fail Name - Everyone Access - Full Control Inherited From - <not inherited> Apply to - This object only The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference, various Properties selections may also exist by default. Two instances with the following summary information will be listed. Type - Success Name - Everyone Access - Write Property Inherited From - <not inherited> Apply to - Special Type - Success Name - Domain Users Access - All Extended Rights Inherited From - <not inherited> Apply to - This object only Type - Success Name - Administrators Access - All Extended Rights Inherited From - <not inherited> Apply to - This object only Type - Success Name - Everyone Access - Special Inherited From - <not inherited> Apply to - This object only (Access - Special = Permissions: Write All Properties, Modify Permissions, Modify Owner)

Fix: F-47930r1_fix

Configure the audit settings for Domain object to include the following. Type - Fail Name - Everyone Access - Full Control Inherited From - <not inherited> Apply to - This object only The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference, various Properties selections may also exist by default. Two instances with the following summary information will be listed. Type - Success Name - Everyone Access - Write Property Inherited From - <not inherited> Apply to - Special Type - Success Name - Domain Users Access - All Extended Rights Inherited From - <not inherited> Apply to - This object only Type - Success Name - Administrators Access - All Extended Rights Inherited From - <not inherited> Apply to - This object only Type - Success Name - Everyone Access - Special Inherited From - <not inherited> Apply to - This object only (Access - Special = Permissions: Write All Properties, Modify Permissions, Modify Owner)

Checks: C-48748r1_chk

Verify the auditing configuration for Infrastructure object. Open "Active Directory Users and Computers". (Available from various menus or run "dsa.msc".) Ensure Advanced Features is selected in the View menu. Select the domain being reviewed in the left pane. Right click the Infrastructure object in the right pane and select Properties. Select the Security tab. Select the Advanced button and then the Auditing tab. If the audit settings on the Infrastructure object are not at least as inclusive as those below, this is a finding. Type - Fail Name - Everyone Access - Full Control Inherited From - &lt;not inherited&gt; The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference, various Properties selections may also exist by default. Type - Success Name - Everyone Access - Special Inherited From - &lt;not inherited&gt; (Access - Special = Permissions: Write All Properties, All Extended Rights, Change Infrastructure Master) Two instances with the following summary information will be listed. Type - Success Name - Everyone Access - Write Property Inherited From - (CN of domain)

Fix: F-47933r2_fix

Configure the audit settings for Infrastructure object to include the following. Type - Fail Name - Everyone Access - Full Control Inherited From - <not inherited> The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference, various Properties selections may also exist by default. Type - Success Name - Everyone Access - Special Inherited From - <not inherited> (Access - Special = Permissions: Write All Properties, All Extended Rights, Change Infrastructure Master) Two instances with the following summary information will be listed. Type - Success Name - Everyone Access - Write Property Inherited From - (CN of domain)

Checks: C-48751r2_chk

Verify the auditing configuration for the Domain Controller OU object. Open "Active Directory Users and Computers". (Available from various menus or run "dsa.msc".) Ensure Advanced Features is selected in the View menu. Select the Domain Controllers OU under the domain being reviewed in the left pane. Right click the Domain Controllers OU object and select Properties. Select the Security tab. Select the Advanced button and then the Auditing tab. If the audit settings on the Domain Controllers OU object are not at least as inclusive as those below, this is a finding. Type - Fail Name - Everyone Access - Full Control Inherited From - &lt;not inherited&gt; Apply to - This object and all child objects The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference, various Properties selections may also exist by default. Type - Success Name - Everyone Access - Special Inherited From - &lt;not inherited&gt; Apply to - This object only (Access - Special = Permissions: all create, delete, and modify permissions) Type - Success Name - Everyone Access - Write All Properties Inherited From - &lt;not inherited&gt; Apply to - This object and all child objects Two instances with the following summary information will be listed. Type - Success Name - Everyone Access - Write Property Inherited From - (CN of domain) Apply to - Organizational Unit objects

Fix: F-47936r2_fix

Configure the audit settings for Domain Controllers OU object to include the following. Type - Fail Name - Everyone Access - Full Control Inherited From - <not inherited> Apply to - This object and all child objects The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference, various Properties selections may also exist by default. Type - Success Name - Everyone Access - Special Inherited From - <not inherited> Apply to - This object only (Access - Special = Permissions: all create, delete, and modify permissions) Type - Success Name - Everyone Access - Write All Properties Inherited From - <not inherited> Apply to - This object and all child objects Two instances with the following summary information will be listed. Type - Success Name - Everyone Access - Write Property Inherited From - (CN of domain) Apply to - Organizational Unit objects

Checks: C-48754r1_chk