Microsoft Windows Server 2012/2012 R2 Domain Controller Security Technical Implementation Guide

Version

WN12-00-000001

Vuln IDs

V-226029
V-1070

Rule IDs

SV-226029r794397_rule
SV-52838

Inadequate physical protection can undermine all other security precautions utilized to protect the system. This can jeopardize the confidentiality, availability, and integrity of the system. Physical security is the first line of protection of any system.

Checks: C-27731r475410_chk

Verify servers are located in controlled access areas that are accessible only to authorized personnel. If systems are not adequately protected, this is a finding.

Fix: F-27719r475411_fix

Ensure servers are located in secure, access-controlled areas.

b

Users with administrative privilege must be documented.

CM-6 - Medium - CCI-000366 - V-226030 - SV-226030r794369_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-00-000004

Vuln IDs

V-226030
V-36658

Rule IDs

SV-226030r794369_rule
SV-51575

Administrative accounts may perform any action on a system. Users with administrative accounts must be documented to ensure those with this level of access are clearly identified.

Checks: C-27732r475413_chk

Review the necessary documentation that identifies the members of the Administrators group. If a list of all users belonging to the Administrators group is not maintained with the ISSO, this is a finding.

Fix: F-27720r475414_fix

Create the necessary documentation that identifies the members of the Administrators group.

c

Users with Administrative privileges must have separate accounts for administrative duties and normal operational tasks.

CM-6 - High - CCI-000366 - V-226031 - SV-226031r794370_rule

RMF Control

CM-6

Severity

H

CCI

Version

WN12-00-000005

Vuln IDs

V-226031
V-36659

Rule IDs

SV-226031r794370_rule
SV-51576

Using a privileged account to perform routine functions makes the computer vulnerable to malicious software inadvertently introduced during a session that has been granted full privileges.

Checks: C-27733r475416_chk

Verify each user with administrative privileges has been assigned a unique administrative account separate from their standard user account. If users with administrative privileges do not have separate accounts for administrative functions and standard user functions, this is a finding.

Fix: F-27721r475417_fix

Ensure each user with administrative privileges has a separate account for user duties and one for privileged duties.

b

Policy must require that system administrators (SAs) be trained for the operating systems used by systems under their control.

CM-6 - Medium - CCI-000366 - V-226032 - SV-226032r794371_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-00-000006

Vuln IDs

V-226032
V-36666

Rule IDs

SV-226032r794371_rule
SV-51577

If SAs are assigned to systems running operating systems for which they have no training, these systems are at additional risk of unintentional misconfiguration that may result in vulnerabilities or decreased availability of the system.

Checks: C-27734r475419_chk

Determine whether the site has a policy that requires SAs be trained for all operating systems running on systems under their control. If the site does not have a policy requiring SAs be trained for all operating systems under their control, this is a finding.

Fix: F-27722r475420_fix

Establish site policy that requires SAs be trained for all operating systems running on systems under their control.

b

Windows 2012/2012 R2 password for the built-in Administrator account must be changed at least annually or when a member of the administrative team leaves the organization.

CM-6 - Medium - CCI-000366 - V-226033 - SV-226033r794811_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-00-000007

Vuln IDs

V-226033
V-14225

Rule IDs

SV-226033r794811_rule
SV-52942

The longer a password is in use, the greater the opportunity for someone to gain unauthorized knowledge of the password. The password for the built-in Administrator account must be changed at least annually or when any member of the administrative team leaves the organization. It is highly recommended to use Microsoft's Local Administrator Password Solution (LAPS). Domain-joined systems can configure this to occur more frequently. LAPS will change the password every "30" days by default. The AO still has the overall authority to use another equivalent capability to accomplish the check.

Checks: C-27735r475422_chk

Review the password last set date for the built-in Administrator account. Domain controllers: Open "Windows PowerShell". Enter "Get-ADUser -Filter * -Properties SID, PasswordLastSet | Where SID -Like "*-500" | FL Name, SID, PasswordLastSet". If the "PasswordLastSet" date is greater than one year old, this is a finding. Member servers and standalone systems: Open "Windows PowerShell" or "Command Prompt". Enter 'Net User [account name] | Find /i "Password Last Set"', where [account name] is the name of the built-in administrator account. (The name of the built-in Administrator account must be changed to something other than "Administrator" per STIG requirements.) If the "PasswordLastSet" date is greater than one year old, this is a finding.

Fix: F-27723r794810_fix

Change the built-in Administrator account password at least annually or whenever an administrator leaves the organization. More frequent changes are recommended. It is highly recommended to use Microsoft's LAPS, which may be used on domain-joined member servers to accomplish this.

c

Administrative accounts must not be used with applications that access the Internet, such as web browsers, or with potential Internet sources, such as email.

CM-6 - High - CCI-000366 - V-226034 - SV-226034r794692_rule

RMF Control

CM-6

Severity

H

CCI

Version

WN12-00-000008

Vuln IDs

V-226034
V-36451

Rule IDs

SV-226034r794692_rule
SV-51578

Using applications that access the Internet or have potential Internet sources using administrative privileges exposes a system to compromise. If a flaw in an application is exploited while running as a privileged user, the entire system could be compromised. Web browsers and email are common attack vectors for introducing malicious code and must not be run with an administrative account. Since administrative accounts may generally change or work around technical restrictions for running a web browser or other applications, it is essential that policy requires administrative accounts to not access the Internet or use applications, such as email. The policy should define specific exceptions for local service administration. These exceptions may include HTTP(S)-based tools that are used for the administration of the local system, services, or attached devices. Technical means such as application whitelisting can be used to enforce the policy to ensure compliance.

Checks: C-27736r475425_chk

Determine whether administrative accounts are prevented from using applications that access the Internet, such as web browsers, or with potential Internet sources, such as email, except as necessary for local service administration. The organization must have a policy that prohibits administrative accounts from using applications that access the Internet, such as web browsers, or with potential Internet sources, such as email, except as necessary for local service administration. The policy should define specific exceptions for local service administration. These exceptions may include HTTP(S)-based tools that are used for the administration of the local system, services, or attached devices. Technical measures such as the removal of applications or application whitelisting must be used where feasible to prevent the use of applications that access the Internet. If accounts with administrative privileges are not prevented from using applications that access the Internet or with potential Internet sources, this is a finding.

Fix: F-27724r794691_fix

Establish and enforce a policy that prohibits administrative accounts from using applications that access the Internet, such as web browsers, or with potential Internet sources, such as email. Define specific exceptions for local service administration. These exceptions may include HTTP(S)-based tools that are used for the administration of the local system, services, or attached devices. Implement technical measures where feasible such as removal of applications or use of application whitelisting to restrict the use of applications that can access the Internet.

b

Members of the Backup Operators group must be documented.

CM-6 - Medium - CCI-000366 - V-226035 - SV-226035r794374_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-00-000009-01

Vuln IDs

V-226035
V-1168

Rule IDs

SV-226035r794374_rule
SV-52156

Backup Operators are able to read and write to any file in the system, regardless of the rights assigned to it. Backup and restore rights permit users to circumvent the file access restrictions present on NTFS disk drives for backup and restore purposes. Visibility of members of the Backup Operators group must be maintained.

Checks: C-27737r475428_chk

If no accounts are members of the Backup Operators group, this is NA. Any accounts that are members of the Backup Operators group, including application accounts, must be documented with the ISSO. If documentation of accounts that are members of the Backup Operators group is not maintained this is a finding.

Fix: F-27725r475429_fix

Create the necessary documentation that identifies the members of the Backup Operators group.

b

Members of the Backup Operators group must have separate accounts for backup duties and normal operational tasks.

CM-6 - Medium - CCI-000366 - V-226036 - SV-226036r794375_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-00-000009-02

Vuln IDs

V-226036
V-40198

Rule IDs

SV-226036r794375_rule
SV-52157

Backup Operators are able to read and write to any file in the system, regardless of the rights assigned to it. Backup and restore rights permit users to circumvent the file access restrictions present on NTFS disk drives for backup and restore purposes. Members of the Backup Operators group must have separate logon accounts for performing backup duties.

Checks: C-27738r475431_chk

If no accounts are members of the Backup Operators group, this is NA. Verify users with accounts in the Backup Operators group have a separate user account for backup functions and for performing normal user tasks. If users with accounts in the Backup Operators group do not have separate accounts for backup functions and standard user functions, this is a finding.

Fix: F-27726r475432_fix

Ensure each member of the Backup Operators group has separate accounts for backup functions and standard user functions.

b

Policy must require application account passwords be at least 15 characters in length.

IA-5 - Medium - CCI-000205 - V-226037 - SV-226037r794297_rule

RMF Control

IA-5

Severity

M

CCI

CCI-000205

Version

WN12-00-000010

Vuln IDs

V-226037
V-36661

Rule IDs

SV-226037r794297_rule
SV-51579

Application/service account passwords must be of sufficient length to prevent being easily cracked. Application/service accounts that are manually managed must have passwords at least 15 characters in length.

Checks: C-27739r475434_chk

Verify the site has a policy to ensure passwords for manually managed application/service accounts are at least 15 characters in length. If such a policy does not exist or has not been implemented, this is a finding.

Fix: F-27727r475435_fix

Establish a site policy that requires application/service account passwords that are manually managed to be at least 15 characters in length. Ensure the policy is enforced.

b

Windows 2012/2012 R2 manually managed application account passwords must be changed at least annually or when a system administrator with knowledge of the password leaves the organization.

CM-6 - Medium - CCI-000366 - V-226038 - SV-226038r794376_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-00-000011

Vuln IDs

V-226038
V-36662

Rule IDs

SV-226038r794376_rule
SV-51580

Setting application accounts to expire may cause applications to stop functioning. However, not changing them on a regular basis exposes them to attack. If managed service accounts are used, this alleviates the need to manually change application account passwords.

Checks: C-27740r475437_chk

Determine if manually managed application/service accounts exist. If none exist, this is NA. If passwords for manually managed application/service accounts are not changed at least annually or when an administrator with knowledge of the password leaves the organization, this is a finding. Identify manually managed application/service accounts. To determine the date a password was last changed: Domain controllers: Open "Windows PowerShell". Enter "Get-ADUser -Identity [application account name] -Properties PasswordLastSet | FL Name, PasswordLastSet", where [application account name] is the name of the manually managed application/service account. If the "PasswordLastSet" date is more than one year old, this is a finding. Member servers and standalone systems: Open "Windows PowerShell" or "Command Prompt". Enter 'Net User [application account name] | Find /i "Password Last Set"', where [application account name] is the name of the manually managed application/service account. If the "Password Last Set" date is more than one year old, this is a finding.

Fix: F-27728r475438_fix

Change passwords for manually managed application/service accounts at least annually or when an administrator with knowledge of the password leaves the organization. It is recommended that system-managed service accounts be used where possible.

b

Shared user accounts must not be permitted on the system.

IA-2 - Medium - CCI-000764 - V-226039 - SV-226039r794694_rule

RMF Control

IA-2

Severity

M

CCI

CCI-000764

Version

WN12-00-000012

Vuln IDs

V-226039
V-1072

Rule IDs

SV-226039r794694_rule
SV-52839

Shared accounts (accounts where two or more people log in with the same user identification) do not provide adequate identification and authentication. There is no way to provide for nonrepudiation or individual accountability for system access and resource usage.

Checks: C-27741r475440_chk

Determine whether any shared accounts exist. If no shared accounts exist, this is NA. Shared accounts, such as required by an application, may be approved by the organization. This must be documented with the ISSO. Documentation must include the reason for the account, who has access to the account, and how the risk of using the shared account is mitigated to include monitoring account activity. If unapproved shared accounts exist, this is a finding.

Fix: F-27729r794693_fix

Remove unapproved shared accounts from the system. Document required shared accounts with the ISSO. Documentation must include the reason for the account, who has access to the account, and how the risk of using the shared account is mitigated, to include monitoring account activity.

a

Security configuration tools or equivalent processes must be used to configure and maintain platforms for security compliance.

CM-6 - Low - CCI-000366 - V-226040 - SV-226040r794377_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN12-00-000013

Vuln IDs

V-226040
V-1128

Rule IDs

SV-226040r794377_rule
SV-52859

Security configuration tools such as Group Policies and Security Templates allow system administrators to consolidate security-related system settings into a single configuration file. These settings can then be applied consistently to any number of Windows machines.

Checks: C-27742r475443_chk

Verify security configuration tools or equivalent processes are being used to configure Windows systems to meet security requirements. If security configuration tools or equivalent processes are not used, this is a finding. Security configuration tools that are integrated into Windows, such as Group Policies and Security Templates, may be used to configure platforms for security compliance. If an alternate method is used to configure a system (e.g., manually using the DISA Windows Security STIGs, etc.) and the same configured result is achieved, this is acceptable.

Fix: F-27730r475444_fix

Implement a process using security configuration tools or the equivalent to configure Windows systems to meet security requirements.

a

System-level information must be backed up in accordance with local recovery time and recovery point objectives.

CM-6 - Low - CCI-000366 - V-226041 - SV-226041r794378_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN12-00-000014

Vuln IDs

V-226041
V-1076

Rule IDs

SV-226041r794378_rule
SV-52841

Operating system backup is a critical step in maintaining data assurance and availability. System-level information includes system-state information, operating system and application software, and licenses. Backups must be consistent with organizational recovery time and recovery point objectives.

Checks: C-27743r475446_chk

Determine whether system-level information is backed up in accordance with local recovery time and recovery point objectives. If system-level information is not backed up in accordance with local recovery time and recovery point objectives, this is a finding.

Fix: F-27731r475447_fix

Implement system-level information backups in accordance with local recovery time and recovery point objectives.

a

User-level information must be backed up in accordance with local recovery time and recovery point objectives.

CM-6 - Low - CCI-000366 - V-226042 - SV-226042r794312_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN12-00-000015

Vuln IDs

V-226042
V-36733

Rule IDs

SV-226042r794312_rule
SV-51581

Operating system backup is a critical step in maintaining data assurance and availability. User-level information is data generated by information system and/or application users. Backups shall be consistent with organizational recovery time and recovery point objectives.

Checks: C-27744r475449_chk

Determine whether user-level information is backed up in accordance with local recovery time and recovery point objectives. If user-level information is not backed up in accordance with local recovery time and recovery point objectives, this is a finding.

Fix: F-27732r475450_fix

Implement user-level information backups in accordance with local recovery time and recovery point objectives.

a

Backups of system-level information must be protected.

CM-6 - Low - CCI-000366 - V-226043 - SV-226043r794313_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN12-00-000016

Vuln IDs

V-226043
V-40172

Rule IDs

SV-226043r794313_rule
SV-52130

A system backup will usually include sensitive information such as user accounts that could be used in an attack. As a valuable system resource, the system backup must be protected and stored in a physically secure location.

Checks: C-27745r475452_chk

Determine if system-level information backups are protected from destruction and stored in a physically secure location. If they are not, this is a finding.

Fix: F-27733r475453_fix

Ensure system-level information backups are stored in a secure location and protected from destruction.

a

System-related documentation must be backed up in accordance with local recovery time and recovery point objectives.

CM-6 - Low - CCI-000366 - V-226044 - SV-226044r794314_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN12-00-000017

Vuln IDs

V-226044
V-40173

Rule IDs

SV-226044r794314_rule
SV-52131

Operating system backup is a critical step in maintaining data assurance and availability. Information system and security-related documentation contains information pertaining to system configuration and security settings. Backups shall be consistent with organizational recovery time and recovery point objectives.

Checks: C-27746r475455_chk

Determine whether system-related documentation is backed up in accordance with local recovery time and recovery point objectives. If system-related documentation is not backed up in accordance with local recovery time and recovery point objectives, this is a finding.

Fix: F-27734r475456_fix

Back up system-related documentation in accordance with local recovery time and recovery point objectives.

b

The operating system must employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs.

CM-7 - Medium - CCI-001774 - V-226045 - SV-226045r794696_rule

RMF Control

CM-7

Severity

M

CCI

CCI-001774

Version

WN12-00-000018

Vuln IDs

V-226045
V-57637

Rule IDs

SV-226045r794696_rule
SV-72047

Utilizing a whitelist provides a configuration management method for allowing the execution of only authorized software. Using only authorized software decreases risk by limiting the number of potential vulnerabilities. The organization must identify authorized software programs and only permit execution of authorized software. The process used to identify software programs that are authorized to execute on organizational information systems is commonly referred to as whitelisting.

Checks: C-27747r475458_chk

This is applicable to unclassified systems; for other systems this is NA. Verify the operating system employs a deny-all, permit-by-exception policy to allow the execution of authorized software programs. If an application whitelisting program is not in use on the system, this is a finding. Configuration of whitelisting applications will vary by the program. AppLocker is a whitelisting application built into Windows Server 2012. A deny-by-default implementation is initiated by enabling any AppLocker rules within a category, only allowing what is specified by defined rules. If AppLocker is used, perform the following to view the configuration of AppLocker: Open PowerShell. If the AppLocker PowerShell module has not been previously imported, execute the following first: Import-Module AppLocker Execute the following command, substituting [c:\temp\file.xml] with a location and file name appropriate for the system: Get-AppLockerPolicy -Effective -XML > c:\temp\file.xml This will produce an xml file with the effective settings that can be viewed in a browser or opened in a program such as Excel for review. Implementation guidance for AppLocker is available in the NSA paper "Application Whitelisting using Microsoft AppLocker" at the following link: https://www.iad.gov/iad/library/ia-guidance/tech-briefs/application-whitelisting-using-microsoft-applocker.cfm

Fix: F-27735r794695_fix

Configure an application whitelisting program to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs. Configuration of whitelisting applications will vary by the program. AppLocker is a whitelisting application built into Windows Server 2012. If AppLocker is used, it is configured through group policy in Computer Configuration >> Windows Settings >> Security Settings >> Application Control Policies >> AppLocker. Implementation guidance for AppLocker is available in the NSA paper "Application Whitelisting using Microsoft AppLocker" at the following link: https://www.iad.gov/iad/library/ia-guidance/tech-briefs/application-whitelisting-using-microsoft-applocker.cfm

b

Protection methods such as TLS, encrypted VPNs, or IPSEC must be implemented if the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process.

SC-8 - Medium - CCI-002420 - V-226046 - SV-226046r794407_rule

RMF Control

SC-8

Severity

M

CCI

CCI-002420

Version

WN12-00-000019

Vuln IDs

V-226046
V-57641

Rule IDs

SV-226046r794407_rule
SV-72051

Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. Ensuring the confidentiality of transmitted information requires the operating system to take measures in preparing information for transmission. This can be accomplished via access control and encryption. Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. When transmitting data, operating systems need to support transmission protection mechanisms such as TLS, encrypted VPNs, or IPSEC.

Checks: C-27748r475461_chk

If the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process, verify protection methods such as TLS, encrypted VPNs, or IPSEC have been implemented. If protection methods have not been implemented, this is a finding.

Fix: F-27736r794697_fix

Configure protection methods such as TLS, encrypted VPNs, or IPSEC when the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process to maintain the confidentiality and integrity.

b

Systems requiring data at rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.

SC-28 - Medium - CCI-001199 - V-226047 - SV-226047r794315_rule

RMF Control

SC-28

Severity

M

CCI

CCI-001199

Version

WN12-00-000020

Vuln IDs

V-226047
V-57645

Rule IDs

SV-226047r794315_rule
SV-72055

This requirement addresses protection of user-generated data, as well as operating system-specific configuration data. Organizations may choose to employ different mechanisms to achieve confidentiality and integrity protections, as appropriate, in accordance with the security category and/or classification of the information. Selection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields).

Checks: C-27749r475464_chk

Verify systems that require additional protections due to factors such as inadequate physical protection or sensitivity of the data employ encryption to protect the confidentiality and integrity of all information at rest. If it does not, this is a finding.

Fix: F-27737r475465_fix

Configure systems that require additional protections due to factors such as inadequate physical protection or sensitivity of the data to employ encryption to protect the confidentiality and integrity of all information at rest.

c

The Windows 2012 / 2012 R2 system must use an anti-virus program.

CM-6 - High - CCI-000366 - V-226048 - SV-226048r794379_rule

RMF Control

CM-6

Severity

H

CCI

Version

WN12-00-000100

Vuln IDs

V-226048
V-1074

Rule IDs

SV-226048r794379_rule
SV-52103

Malicious software can establish a base on individual desktops and servers. Employing an automated mechanism to detect this type of software will aid in elimination of the software from the operating system.

Checks: C-27750r475467_chk

Verify an anti-virus solution is installed on the system. The anti-virus solution may be bundled with an approved host-based security solution. If there is no anti-virus solution installed on the system, this is a finding.

Fix: F-27738r475468_fix

Install an anti-virus solution on the system.

b

The Server Message Block (SMB) v1 protocol must be disabled on Windows 2012 R2.

CM-7 - Medium - CCI-000381 - V-226049 - SV-226049r794699_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-00-000160

Vuln IDs

V-226049
V-73805

Rule IDs

SV-226049r794699_rule
SV-88471

SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks as well as not being FIPS compliant. Disabling SMBv1 support may prevent access to file or print sharing resources with systems or devices that only support SMBv1. File shares and print services hosted on Windows Server 2003 are an example, however Windows Server 2003 is no longer a supported operating system. Some older network attached devices may only support SMBv1.

Checks: C-27751r475470_chk

This requirement applies to Windows 2012 R2, it is NA for Windows 2012 (see V-73519 and V-73523 for 2012 requirements). Different methods are available to disable SMBv1 on Windows 2012 R2. This is the preferred method, however if V-73519 and V-73523 are configured, this is NA. Run "Windows PowerShell" with elevated privileges (run as administrator). Enter the following: Get-WindowsOptionalFeature -Online | Where FeatureName -eq SMB1Protocol If "State : Enabled" is returned, this is a finding. Alternately: Search for "Features". Select "Turn Windows features on or off". If "SMB 1.0/CIFS File Sharing Support" is selected, this is a finding.

Fix: F-27739r794698_fix

Run "Windows PowerShell" with elevated privileges (run as administrator). Enter the following: Disable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol Alternately: Search for "Features". Select "Turn Windows features on or off". De-select "SMB 1.0/CIFS File Sharing Support". The system must be restarted for the changes to take effect.

b

The Server Message Block (SMB) v1 protocol must be disabled on the SMB server.

CM-7 - Medium - CCI-000381 - V-226050 - SV-226050r794701_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-00-000170

Vuln IDs

V-226050
V-73519

Rule IDs

SV-226050r794701_rule
SV-88193

SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks as well as not being FIPS compliant. Disabling SMBv1 support may prevent access to file or print sharing resources with systems or devices that only support SMBv1. File shares and print services hosted on Windows Server 2003 are an example, however Windows Server 2003 is no longer a supported operating system. Some older network attached devices may only support SMBv1.

Checks: C-27752r475473_chk

This requirement specifically applies to Windows 2012 but can also be used for Windows 2012 R2. Different methods are available to disable SMBv1 on Windows 2012 R2, if V-73805 is configured on Windows 2012 R2, this is NA. 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: \SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\ Value Name: SMB1 Type: REG_DWORD Value: 0x00000000 (0)

Fix: F-27740r794700_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> "Configure SMBv1 Server" to "Disabled". The system must be restarted for the change to take effect. This policy setting requires the installation of the SecGuide custom templates included with the STIG package. "SecGuide.admx" and "SecGuide.adml" must be copied to the \Windows\PolicyDefinitions and \Windows\PolicyDefinitions\en-US directories respectively.

b

The Server Message Block (SMB) v1 protocol must be disabled on the SMB client.

CM-7 - Medium - CCI-000381 - V-226051 - SV-226051r794766_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-00-000180

Vuln IDs

V-226051
V-73523

Rule IDs

SV-226051r794766_rule
SV-88205

SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks as well as not being FIPS compliant. Disabling SMBv1 support may prevent access to file or print sharing resources with systems or devices that only support SMBv1. File shares and print services hosted on Windows Server 2003 are an example, however Windows Server 2003 is no longer a supported operating system. Some older network attached devices may only support SMBv1.

Checks: C-27753r475476_chk

This requirement specifically applies to Windows 2012 but can also be used for Windows 2012 R2. Different methods are available to disable SMBv1 on Windows 2012 R2, if V-73805 is configured on Windows 2012 R2, this is NA. If the following registry value is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Services\mrxsmb10\ Value Name: Start Type: REG_DWORD Value: 0x00000004 (4) If the following registry value includes MRxSmb10, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanWorkstation\ Value Name: DependOnService Type: REG_MULTI_SZ Value: Default values after removing MRxSmb10 include the following, which are not a finding: Bowser MRxSmb20 NSI

Fix: F-27741r794765_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> "Configure SMBv1 client driver" to "Enabled" with "Disable driver (recommended)" selected for "Configure MrxSmb10 driver". Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> "Configure SMBv1 client (extra setting needed for pre-Win8.1/2012R2)" to "Enabled" with the following three lines of text entered for "Configure LanmanWorkstation Dependencies": Bowser MRxSmb20 NSI The system must be restarted for the changes to take effect. These policy settings requires the installation of the SecGuide custom templates included with the STIG package. "SecGuide.admx" and "SecGuide.adml" must be copied to the \Windows\PolicyDefinitions and \Windows\PolicyDefinitions\en-US directories respectively.

b

Orphaned security identifiers (SIDs) must be removed from user rights on Windows 2012 / 2012 R2.

CM-6 - Medium - CCI-000366 - V-226052 - SV-226052r794380_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-00-000190

Vuln IDs

V-226052
V-75915

Rule IDs

SV-226052r794380_rule
SV-90603

Accounts or groups given rights on a system may show up as unresolved SIDs for various reasons including deletion of the accounts or groups. If the account or group objects are reanimated, there is a potential they may still have rights no longer intended. Valid domain accounts or groups may also show up as unresolved SIDs if a connection to the domain cannot be established for some reason.

Checks: C-27754r475479_chk

Review the effective User Rights setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. Review each User Right listed for any unresolved SIDs to determine whether they are valid, such as due to being temporarily disconnected from the domain. (Unresolved SIDs have the format of "*S-1-…".) If any unresolved SIDs exist and are not for currently valid accounts or groups, this is a finding.

Fix: F-27742r475480_fix

Remove any unresolved SIDs found in User Rights assignments and determined to not be for currently valid accounts or groups by removing the accounts or groups from the appropriate group policy.

b

Windows PowerShell must be updated to a version that supports script block logging on Windows 2012/2012 R2.

CM-6 - Medium - CCI-000366 - V-226053 - SV-226053r794790_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-00-000200

Vuln IDs

V-226053
V-80473

Rule IDs

SV-226053r794790_rule
SV-95179

Later versions of Windows PowerShell provide additional security and advanced logging features that can provide greater detail when malware has been run on a system. PowerShell 5.x includes the advanced logging features. PowerShell 4.0 with the addition of patch KB3000850 on Windows 2012 R2 or KB3119938 on Windows 2012 adds advanced logging features. PowerShell is updated with the installation of the corresponding version of the Windows Management Framework (WMF). Updating to a later PowerShell version may have compatibility issues with some applications. The following links should be reviewed and updates tested before applying to a production environment. WMF 4.0: Review the System Requirements under the download link - https://www.microsoft.com/en-us/download/details.aspx?id=40855 WMF 5.0: https://docs.microsoft.com/en-us/powershell/wmf/5.0/productincompat WMF 5.1: https://docs.microsoft.com/en-us/powershell/wmf/5.1/productincompat

Checks: C-27755r475482_chk

Open "Windows PowerShell". Enter "$PSVersionTable". If the value for "PSVersion" is not 4.0 or 5.x, this is a finding. Windows 2012 R2 includes PowerShell 4.0 by default. Windows 2012 must be updated. If PowerShell 4.0 is used, the required patch for script block logging will be verified with the requirement to have that enabled.

Fix: F-27743r794789_fix

Update Windows PowerShell to version 4.0 or 5.x. Windows 2012 R2 includes PowerShell 4.0 by default. It may be updated with the installation of Windows Management Framework (WMF) 5.0 or 5.1. Windows 2012 requires the installation of WMF 4.0, 5.0, or 5.1. Updating to a later PowerShell version may have compatibility issues with some applications. The following links should be reviewed and updates tested before applying to a production environment. WMF 4.0: Review the System Requirements under the download link - https://www.microsoft.com/en-us/download/details.aspx?id=40855 WMF 5.0: https://docs.microsoft.com/en-us/powershell/wmf/5.0/productincompat WMF 5.1: https://docs.microsoft.com/en-us/powershell/wmf/5.1/productincompat

b

PowerShell script block logging must be enabled on Windows 2012/2012 R2.

AU-3 - Medium - CCI-000135 - V-226054 - SV-226054r794758_rule

RMF Control

AU-3

Severity

M

CCI

CCI-000135

Version

WN12-00-000210

Vuln IDs

V-226054
V-80475

Rule IDs

SV-226054r794758_rule
SV-95183

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Enabling PowerShell script block logging will record detailed information from the processing of PowerShell commands and scripts. This can provide additional detail when malware has run on a system. PowerShell 5.x supports script block logging. PowerShell 4.0 with the addition of patch KB3000850 on Windows 2012 R2 or KB3119938 on Windows 2012 adds support for script block logging. Satisfies: SRG-OS-000042-GPOS-00021

Checks: C-27756r475485_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\Windows\PowerShell\ScriptBlockLogging\ Value Name: EnableScriptBlockLogging Value Type: REG_DWORD Value: 0x00000001 (1) PowerShell 4.0 requires the installation of patch KB3000850 on Windows 2012 R2 or KB3119938 on Windows 2012. If the patch is not installed on systems with PowerShell 4.0, this is a finding. PowerShell 5.x does not require the installation of an additional patch.

Fix: F-27744r794757_fix

Configure the following registry value as specified. Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging\ Value Name: EnableScriptBlockLogging Value Type: REG_DWORD Value: 0x00000001 (1) Administrative templates from later versions of Windows include a group policy setting for this. Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows PowerShell >> "Turn on PowerShell Script Block Logging" to "Enabled". Install patch KB3000850 on Windows 2012 R2 or KB3119938 on Windows 2012 on systems with PowerShell 4.0. PowerShell 5.x does not require the installation of an additional patch.

b

Windows PowerShell 2.0 must not be installed on Windows 2012/2012 R2.

CM-7 - Medium - CCI-000381 - V-226055 - SV-226055r794768_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-00-000220

Vuln IDs

V-226055
V-80477

Rule IDs

SV-226055r794768_rule
SV-95185

Windows PowerShell versions 4.0 (with a patch) and 5.x add advanced logging features that can provide additional detail when malware has been run on a system. Ensuring Windows PowerShell 2.0 is not installed as well mitigates against a downgrade attack that evades the advanced logging features of later Windows PowerShell versions.

Checks: C-27757r475488_chk

Windows PowerShell 2.0 is not installed by default. Open "Windows PowerShell". Enter "Get-WindowsFeature -Name PowerShell-v2". If "Installed State" is "Installed", this is a finding. An Installed State of "Available" or "Removed" is not a finding.

Fix: F-27745r794767_fix

Windows PowerShell 2.0 is not installed by default. Uninstall it if it has been installed. Open "Windows PowerShell". Enter "Uninstall-WindowsFeature -Name PowerShell-v2". Alternately: Use the "Remove Roles and Features Wizard" and deselect "Windows PowerShell 2.0 Engine" under "Windows PowerShell".

b

Windows 2012 account lockout duration must be configured to 15 minutes or greater.

AC-7 - Medium - CCI-002238 - V-226056 - SV-226056r794778_rule

RMF Control

AC-7

Severity

M

CCI

CCI-002238

Version

WN12-AC-000001

Vuln IDs

V-226056
V-1099

Rule IDs

SV-226056r794778_rule
SV-52850

The account lockout feature, when enabled, prevents brute-force password attacks on the system. This parameter specifies the period of time that an account will remain locked after the specified number of failed logon attempts.

Checks: C-27758r475491_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy. If the "Account lockout duration" is less than "15" minutes (excluding "0"), this is a finding. Configuring this to "0", requiring an administrator to unlock the account, is more restrictive and is not a finding.

Fix: F-27746r794777_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy >> "Account lockout duration" to "15" minutes or greater. A value of "0" is also acceptable, requiring an administrator to unlock the account.

b

The number of allowed bad logon attempts must meet minimum requirements.

AC-7 - Medium - CCI-000044 - V-226057 - SV-226057r794277_rule

RMF Control

AC-7

Severity

M

CCI

CCI-000044

Version

WN12-AC-000002

Vuln IDs

V-226057
V-1097

Rule IDs

SV-226057r794277_rule
SV-52848

The account lockout feature, when enabled, prevents brute-force password attacks on the system. The higher this value is, the less effective the account lockout feature will be in protecting the local system. The number of bad logon attempts must be reasonably small to minimize the possibility of a successful password attack, while allowing for honest errors made during a normal user logon.

Checks: C-27759r475494_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy -> Computer Configuration -> Windows Settings -> Security Settings -> Account Policies -> Account Lockout Policy. If the "Account lockout threshold" is "0" or more than "3" attempts, this is a finding.

Fix: F-27747r475495_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Account Policies -> Account Lockout Policy -> "Account lockout threshold" to "3" or less invalid logon attempts (excluding "0" which is unacceptable).

b

The reset period for the account lockout counter must be configured to 15 minutes or greater on Windows 2012.

AC-7 - Medium - CCI-000044 - V-226058 - SV-226058r794278_rule

RMF Control

AC-7

Severity

M

CCI

CCI-000044

Version

WN12-AC-000003

Vuln IDs

V-226058
V-1098

Rule IDs

SV-226058r794278_rule
SV-52849

The account lockout feature, when enabled, prevents brute-force password attacks on the system. This parameter specifies the period of time that must pass after failed logon attempts before the counter is reset to "0". The smaller this value is, the less effective the account lockout feature will be in protecting the local system.

Checks: C-27760r475497_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy. If the "Reset account lockout counter after" value is less than "15" minutes, this is a finding.

Fix: F-27748r475498_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy >> "Reset account lockout counter after" to at least "15" minutes.

b

The password history must be configured to 24 passwords remembered.

IA-5 - Medium - CCI-000200 - V-226059 - SV-226059r794296_rule

RMF Control

IA-5

Severity

M

CCI

CCI-000200

Version

WN12-AC-000004

Vuln IDs

V-226059
V-1107

Rule IDs

SV-226059r794296_rule
SV-52853

A system is more vulnerable to unauthorized access when system users recycle the same password several times without being required to change to a unique password on a regularly scheduled basis. This enables users to effectively negate the purpose of mandating periodic password changes. The default value is 24 for Windows domain systems. DoD has decided this is the appropriate value for all Windows systems.

Checks: C-27761r475500_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. If the value for "Enforce password history" is less than "24" passwords remembered, this is a finding.

Fix: F-27749r475501_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Enforce password history" to "24" passwords remembered.

b

The maximum password age must meet requirements.

IA-5 - Medium - CCI-000199 - V-226060 - SV-226060r794295_rule

RMF Control

IA-5

Severity

M

CCI

CCI-000199

Version

WN12-AC-000005

Vuln IDs

V-226060
V-1104

Rule IDs

SV-226060r794295_rule
SV-52851

The longer a password is in use, the greater the opportunity for someone to gain unauthorized knowledge of the passwords. Scheduled changing of passwords hinders the ability of unauthorized system users to crack passwords and gain access to a system.

Checks: C-27762r475503_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy -> Computer Configuration -> Windows Settings -> Security Settings -> Account Policies -> Password Policy. If the value for the "Maximum password age" is greater than "60" days, this is a finding. If the value is set to "0" (never expires), this is a finding.

Fix: F-27750r475504_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Account Policies -> Password Policy -> "Maximum password age" to "60" days or less (excluding "0" which is unacceptable).

b

The minimum password age must meet requirements.

IA-5 - Medium - CCI-000198 - V-226061 - SV-226061r794294_rule

RMF Control

IA-5

Severity

M

CCI

CCI-000198

Version

WN12-AC-000006

Vuln IDs

V-226061
V-1105

Rule IDs

SV-226061r794294_rule
SV-52852

Permitting passwords to be changed in immediate succession within the same day allows users to cycle passwords through their history database. This enables users to effectively negate the purpose of mandating periodic password changes.

Checks: C-27763r475506_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy -> Computer Configuration -> Windows Settings -> Security Settings -> Account Policies -> Password Policy. If the value for the "Minimum password age" is set to "0" days ("Password can be changed immediately."), this is a finding.

Fix: F-27751r475507_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Account Policies -> Password Policy -> "Minimum password age" to at least "1" day.

b

Passwords must, at a minimum, be 14 characters.

IA-5 - Medium - CCI-000205 - V-226062 - SV-226062r794298_rule

RMF Control

IA-5

Severity

M

CCI

CCI-000205

Version

WN12-AC-000007

Vuln IDs

V-226062
V-6836

Rule IDs

SV-226062r794298_rule
SV-52938

Information systems not protected with strong password schemes (including passwords of minimum length) provide the opportunity for anyone to crack the password, thus gaining access to the system and compromising the device, information, or the local network.

Checks: C-27764r475509_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy -> Computer Configuration -> Windows Settings -> Security Settings -> Account Policies -> Password Policy. If the value for the "Minimum password length," is less than "14" characters, this is a finding.

Fix: F-27752r475510_fix

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

b

The built-in Windows password complexity policy must be enabled.

IA-5 - Medium - CCI-000192 - V-226063 - SV-226063r794292_rule

RMF Control

IA-5

Severity

M

CCI

CCI-000192

Version

WN12-AC-000008

Vuln IDs

V-226063
V-1150

Rule IDs

SV-226063r794292_rule
SV-52863

The use of complex passwords increases their strength against attack. The built-in Windows password complexity policy requires passwords to contain at least 3 of the 4 types of characters (numbers, upper- and lower-case letters, and special characters), as well as preventing the inclusion of user names or parts of.

Checks: C-27765r475512_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. If the value for "Password must meet complexity requirements" is not set to "Enabled", this is a finding. Note: If an external password filter is in use that enforces all 4 character types and requires this setting be set to "Disabled", this would not be considered a finding. If this setting does not affect the use of an external password filter, it must be enabled for fallback purposes.

Fix: F-27753r475513_fix

Configure the policy value for Computer Configuration >> Windows Settings -> Security Settings >> Account Policies >> Password Policy >> "Password must meet complexity requirements" to "Enabled".

c

Reversible password encryption must be disabled.

IA-5 - High - CCI-000196 - V-226064 - SV-226064r794293_rule

RMF Control

IA-5

Severity

H

CCI

CCI-000196

Version

WN12-AC-000009

Vuln IDs

V-226064
V-2372

Rule IDs

SV-226064r794293_rule
SV-52880

Storing passwords using reversible encryption is essentially the same as storing clear-text versions of the passwords. For this reason, this policy must never be enabled.

Checks: C-27766r475515_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy -> Computer Configuration -> Windows Settings -> Security Settings -> Account Policies -> Password Policy. If the value for "Store password using reversible encryption" is not set to "Disabled", this is a finding.

Fix: F-27754r475516_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Account Policies -> Password Policy -> "Store password using reversible encryption" to "Disabled".

b

Kerberos user logon restrictions must be enforced.

CM-6 - Medium - CCI-000366 - V-226065 - SV-226065r794383_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-AC-000010-DC

Vuln IDs

V-226065
V-2376

Rule IDs

SV-226065r794383_rule
SV-51160

This policy setting determines whether the Kerberos Key Distribution Center (KDC) validates every request for a session ticket against the user rights policy of the target computer. The policy is enabled by default which is the most secure setting for validating access to target resources is not circumvented.

Checks: C-27767r475518_chk

Verify the following is configured in the Default Domain Policy. Open "Group Policy Management". Navigate to "Group Policy Objects" in the Domain being reviewed (Forest > Domains > Domain). Right click on the "Default Domain Policy". Select Edit. Navigate to Computer Configuration > Policies > Windows Settings > Security Settings > Account Policies > Kerberos Policy. If the "Enforce user logon restrictions" is not set to "Enabled", this is a finding.

Fix: F-27755r475519_fix

Configure the policy value in the Default Domain Policy for Computer Configuration -> Policies -> Windows Settings -> Security Settings -> Account Policies -> Kerberos Policy -> "Enforce user logon restrictions" to "Enabled".

b

The Kerberos service ticket maximum lifetime must be limited to 600 minutes or less.

CM-6 - Medium - CCI-000366 - V-226066 - SV-226066r794792_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-AC-000011-DC

Vuln IDs

V-226066
V-2377

Rule IDs

SV-226066r794792_rule
SV-51162

This setting determines the maximum amount of time (in minutes) that a granted session ticket can be used to access a particular service. Session tickets are used only to authenticate new connections with servers. Ongoing operations are not interrupted if the session ticket used to authenticate the connection expires during the connection.

Checks: C-27768r475521_chk

Verify the following is configured in the Default Domain Policy. Open "Group Policy Management". Navigate to "Group Policy Objects" in the Domain being reviewed (Forest > Domains > Domain). Right click on the "Default Domain Policy". Select Edit. Navigate to Computer Configuration > Policies > Windows Settings > Security Settings > 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-27756r794791_fix

Configure the policy value in the Default Domain Policy for Computer Configuration -> Policies -> Windows Settings -> Security Settings -> Account Policies -> Kerberos Policy -> "Maximum lifetime for service ticket" to a maximum of 600 minutes, but not 0, which equates to "Ticket doesn't expire".

b

The Kerberos user ticket lifetime must be limited to 10 hours or less.

CM-6 - Medium - CCI-000366 - V-226067 - SV-226067r794794_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-AC-000012-DC

Vuln IDs

V-226067
V-2378

Rule IDs

SV-226067r794794_rule
SV-51164

In Kerberos, there are 2 types of tickets: Ticket Granting Tickets (TGTs) and Service Tickets. Kerberos tickets have a limited lifetime so the time an attacker has to implement an attack is limited. This policy controls how long TGTs can be renewed. With Kerberos, the user's initial authentication to the domain controller results in a TGT which is then used to request Service Tickets to resources. Upon startup, each computer gets a TGT before requesting a service ticket to the domain controller and any other computers it needs to access. For services that startup under a specified user account, users must always get a TGT first, then get Service Tickets to all computers and services accessed.

Checks: C-27769r475524_chk

Verify the following is configured in the Default Domain Policy. Open "Group Policy Management". Navigate to "Group Policy Objects" in the Domain being reviewed (Forest > Domains > Domain). Right click on the "Default Domain Policy". Select Edit. Navigate to Computer Configuration > Policies > Windows Settings > Security Settings > 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-27757r794793_fix

Configure the policy value in the Default Domain Policy for Computer Configuration -> Policies -> Windows Settings -> Security Settings -> Account Policies -> Kerberos Policy -> "Maximum lifetime for user ticket" to a maximum of 10 hours, but not 0, which equates to "Ticket doesn't expire".

b

The Kerberos policy user ticket renewal maximum lifetime must be limited to 7 days or less.

CM-6 - Medium - CCI-000366 - V-226068 - SV-226068r794388_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-AC-000013-DC

Vuln IDs

V-226068
V-2379

Rule IDs

SV-226068r794388_rule
SV-51166

This setting determines the period of time (in days) during which a user's TGT may be renewed. This security configuration limits the amount of time an attacker has to crack the TGT and gain access.

Checks: C-27770r475527_chk

Verify the following is configured in the Default Domain Policy. Open "Group Policy Management". Navigate to "Group Policy Objects" in the Domain being reviewed (Forest > Domains > Domain). Right click on the "Default Domain Policy". Select Edit. Navigate to Computer Configuration > Policies > Windows Settings > Security Settings > Account Policies > Kerberos Policy. If the "Maximum lifetime for user ticket renewal" is greater than 7 days, this is a finding.

Fix: F-27758r475528_fix

Configure the policy value in the Default Domain Policy for Computer Configuration -> Policies -> Windows Settings -> Security Settings -> Account Policies -> Kerberos Policy -> "Maximum lifetime for user ticket renewal" to a maximum of 7 days or less.

b

The computer clock synchronization tolerance must be limited to 5 minutes or less.

IA-2 - Medium - CCI-001941 - V-226069 - SV-226069r794309_rule

RMF Control

IA-2

Severity

M

CCI

CCI-001941

Version

WN12-AC-000014-DC

Vuln IDs

V-226069
V-2380

Rule IDs

SV-226069r794309_rule
SV-51168

This setting determines the maximum time difference (in minutes) that Kerberos will tolerate between the time on a client's clock and the time on a server's clock while still considering the two clocks synchronous. In order to prevent replay attacks, Kerberos uses timestamps as part of its protocol definition. For timestamps to work properly, the clocks of the client and the server need to be in sync as much as possible.

Checks: C-27771r475530_chk

Verify the following is configured in the Default Domain Policy. Open "Group Policy Management". Navigate to "Group Policy Objects" in the Domain being reviewed (Forest > Domains > Domain). Right click on the "Default Domain Policy". Select Edit. Navigate to Computer Configuration > Policies > Windows Settings > Security Settings > Account Policies > Kerberos Policy. If the "Maximum tolerance for computer clock synchronization" is greater than 5 minutes, this is a finding.

Fix: F-27759r475531_fix

Configure the policy value in the Default Domain Policy for Computer Configuration -> Windows Settings -> Security Settings -> Account Policies -> Kerberos Policy -> "Maximum tolerance for computer clock synchronization" to a maximum of 5 minutes or less.

c

Active Directory data files must have proper access control permissions.

AC-6 - High - CCI-002235 - V-226070 - SV-226070r794318_rule

RMF Control

AC-6

Severity

H

CCI

Version

WN12-AD-000001-DC

Vuln IDs

V-226070
V-8316

Rule IDs

SV-226070r794318_rule
SV-51175

Improper access permissions for directory data related files could allow unauthorized users to read, modify, or delete directory data or audit trails.

Checks: C-27772r475533_chk

Verify the permissions on the content of the NTDS directory. Open the registry editor (regedit). Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS\Parameters. Note the directory locations in the values for: Database log files path DSA Database file By default they will be \Windows\NTDS. If the locations are different, the following will need to be run for each. Open an elevated command prompt (Win+x, Command Prompt (Admin)). Navigate to the NTDS directory (\Windows\NTDS by default). Run "icacls *.*". If the permissions on each file are not at least as restrictive as the following, this is a finding. NT AUTHORITY\SYSTEM:(I)(F) BUILTIN\Administrators:(I)(F) (I) - permission inherited from parent container (F) - full access Do not use File Explorer to attempt to view permissions of the NTDS folder. Accessing the folder through File Explorer will change the permissions on the folder.

Fix: F-27760r475534_fix

Ensure the permissions on NTDS database and log files are at least as restrictive as the following: NT AUTHORITY\SYSTEM:(I)(F) BUILTIN\Administrators:(I)(F) (I) - permission inherited from parent container (F) - full access

c

The Active Directory SYSVOL directory must have the proper access control permissions.

AC-6 - High - CCI-002235 - V-226071 - SV-226071r794770_rule

RMF Control

AC-6

Severity

H

CCI

Version

WN12-AD-000002-DC

Vuln IDs

V-226071
V-39331

Rule IDs

SV-226071r794770_rule
SV-51176

Improper access permissions for directory data files could allow unauthorized users to read, modify, or delete directory data. The SYSVOL directory contains public files (to the domain) such as policies and logon scripts. Data in shared subdirectories are replicated to all domain controllers in a domain.

Checks: C-27773r794319_chk

Verify the permissions on the SYSVOL directory. Open a command prompt. Run "net share". Make note of the directory location of the SYSVOL share. By default this will be \Windows\SYSVOL\sysvol. For this requirement, permissions will be verified at the first SYSVOL directory level. Alternately, use Icacls.exe to view the permissions of the SYSVOL directory. Open a command prompt. Run "icacls c:\Windows\SYSVOL The following results should be displayed: NT AUTHORITY\Authenticated Users:(RX) NT AUTHORITY\Authenticated Users:(OI)(CI)(IO)(GR,GE) BUILTIN\Server Operators:(RX) BUILTIN\Server Operators:(OI)(CI)(IO)(GR,GE) BUILTIN\Administrators:(M,WDAC,WO) BUILTIN\Administrators:(OI)(CI)(IO)(F) NT AUTHORITY\SYSTEM:(F) NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(F) BUILTIN\Administrators:(M,WDAC,WO) CREATOR OWNER:(OI)(CI)(IO)(F) (RX) - Read & execute Run "icacls /help" to view definitions of other permission codes. If the above results are not displayed, this is a finding.

Fix: F-27761r794769_fix

Ensure the permissions on SYSVOL directory do not allow greater than read & execute for standard user accounts or groups. The defaults below meet this requirement. Type - Allow Principal - Authenticated Users Access - Read & execute Inherited from - None Applies to - This folder, subfolder and files Type - Allow Principal - Server Operators Access - Read & execute Inherited from - None Applies to - This folder, subfolder and files Type - Allow Principal - Administrators Access - Special Inherited from - None Applies to - This folder only (Access - Special - Basic Permissions: all selected except Full control) Type - Allow Principal - CREATOR OWNER Access - Full control Inherited from - None Applies to - Subfolders and files only Type - Allow Principal - Administrators Access - Full control Inherited from - None Applies to - Subfolders and files only Type - Allow Principal - SYSTEM Access - Full control Inherited from - None Applies to - This folder, subfolders and files

c

Active Directory Group Policy objects must have proper access control permissions.

AC-6 - High - CCI-002235 - V-226072 - SV-226072r794772_rule

RMF Control

AC-6

Severity

H

CCI

Version

WN12-AD-000003-DC

Vuln IDs

V-226072
V-33673

Rule IDs

SV-226072r794772_rule
SV-51177

When directory service database objects do not have appropriate access control permissions, it may be possible for malicious users to create, read, update, or delete the objects and degrade or destroy the integrity of the data. When the directory service is used for identification, authentication, or authorization functions, a compromise of the database objects could lead to a compromise of all systems relying on the directory service. For Active Directory (AD), the Group Policy objects require special attention. In a distributed administration model (i.e., help desk), Group Policy objects are more likely to have access permissions changed from the secure defaults. If inappropriate access permissions are defined for Group Policy Objects, this could allow an intruder to change the security policy applied to all domain client computers (workstations and servers).

Checks: C-27774r475539_chk

Verify the permissions on Group Policy objects. 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. If any standard user accounts or groups have greater than Allow permissions of Read and Apply group policy, this is a finding. Other access permissions that allow the objects to be updated are considered findings unless specifically documented by the ISSO. The default permissions noted below meet this requirement. The permissions shown are at the summary level. More detailed permissions can be viewed by selecting the next Advanced button, selecting the desired Permission entry, and the Edit button. Authenticated Users - Read, Apply group policy, Special permissions The Special permissions for Authenticated Users are for Read type Properties. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. The Special permissions for the following default groups are not the focus of this requirement and may include a wide range of permissions and properties. CREATOR OWNER - Special permissions SYSTEM - Read, Write, Create all child objects, Delete all child objects, Special permissions Domain Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions Enterprise Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions The Domain Admins and Enterprise Admins will not have the "Delete all child objects" permission on the two default group policy objects: Default Domain Policy and Default Domain Controllers Policy. They will have this permission on created group policy objects. The Anonymous Logon, Guests, or any group that contains those groups (in which users are not uniquely identified and authenticated) must not have any access permissions unless the group and justification is explicitly documented with the ISSO.

Fix: F-27762r794771_fix

Ensure the permissions on Group Policy objects do not allow greater than Read and Apply group policy for standard user accounts or groups. The default permissions below meet this requirement. Authenticated Users - Read, Apply group policy, Special permissions The Special permissions for Authenticated Users are for Read type Properties. CREATOR OWNER - Special permissions SYSTEM - Read, Write, Create all child objects, Delete all child objects, Special permissions Domain Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions Enterprise Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions Document any other access permissions that allow the objects to be updated with the ISSO. The Domain Admins and Enterprise Admins will not have the "Delete all child objects" permission on the two default group policy objects: Default Domain Policy and Default Domain Controllers Policy. They will have this permission on created group policy objects.

c

The Active Directory Domain Controllers Organizational Unit (OU) object must have the proper access control permissions.

AC-6 - High - CCI-002235 - V-226073 - SV-226073r794774_rule

RMF Control

AC-6

Severity

H

CCI

Version

WN12-AD-000004-DC

Vuln IDs

V-226073
V-39332

Rule IDs

SV-226073r794774_rule
SV-51178

When Active Directory (AD) objects do not have appropriate access control permissions, it may be possible for malicious users to create, read, update, or delete the objects and degrade or destroy the integrity of the data. When the directory service is used for identification, authentication, or authorization functions, a compromise of the database objects could lead to a compromise of all systems that rely on the directory service. The Domain Controllers OU object requires special attention as the Domain Controllers are central to the configuration and management of the domain. Inappropriate access permissions defined for the Domain Controllers OU could allow an intruder or unauthorized personnel to make changes which could lead to the compromise of the domain.

Checks: C-27775r475542_chk

Verify the permissions on the Domain Controllers OU. Open "Active Directory Users and Computers". (Available from various menus or run "dsa.msc".) Select Advanced Features in the View menu if not previously selected. Navigate to the Domain Controllers OU (folder in folder icon). Right click the OU and select Properties. Select the Security tab. If the permissions on the Domain Controllers OU do not restrict changes to System, Domain Admins, Enterprise Admins and Administrators, this is a finding. The default permissions listed below satisfy this requirement. Domains supporting Microsoft Exchange will have additional Exchange related permissions on the Domain Controllers OU. These may include some change related permissions and are not a finding. The permissions shown are at the summary level. More detailed permissions can be viewed by selecting the Advanced button, selecting the desired Permission entry, and the Edit button. SELF - Special permissions Authenticated Users - Read, Special permissions The Special permissions for Authenticated Users are Read types. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. SYSTEM - Full Control Domain Admins - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions Enterprise Admins - Full Control Administrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions Pre-Windows 2000 Compatible Access - Special permissions The Special permissions for Pre-Windows 2000 Compatible Access are Read types. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions

Fix: F-27763r794773_fix

Limit the permissions on the Domain Controllers OU to restrict changes to System, Domain Admins, Enterprise Admins and Administrators. The default permissions listed below satisfy this requirement. Domains supporting Microsoft Exchange will have additional Exchange related permissions on the Domain Controllers OU. These may include some change related permissions. SELF - Special permissions Authenticated Users - Read, Special permissions The Special permissions for Authenticated Users are Read types. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. SYSTEM - Full Control Domain Admins - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions Enterprise Admins - Full Control Administrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions Pre-Windows 2000 Compatible Access - Special permissions The Special permissions for Pre-Windows 2000 Compatible Access are Read types. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions

c

Domain created Active Directory Organizational Unit (OU) objects must have proper access control permissions.

AC-6 - High - CCI-002235 - V-226074 - SV-226074r794776_rule

RMF Control

AC-6

Severity

H

CCI

Version

WN12-AD-000005-DC

Vuln IDs

V-226074
V-39333

Rule IDs

SV-226074r794776_rule
SV-51179

When directory service database objects do not have appropriate access control permissions, it may be possible for malicious users to create, read, update, or delete the objects and degrade or destroy the integrity of the data. When the directory service is used for identification, authentication, or authorization functions, a compromise of the database objects could lead to a compromise of all systems that rely on the directory service. For Active Directory (AD), the Organizational Unit (OU) objects require special attention. In a distributed administration model (i.e., help desk), OU objects are more likely to have access permissions changed from the secure defaults. If inappropriate access permissions are defined for OU objects, it could allow an intruder to add or delete users in the OU. This could result in unauthorized access to data or a Denial of Service to authorized users.

Checks: C-27776r475545_chk

Verifying the permissions on domain defined OUs. Open "Active Directory Users and Computers". (Available from various menus or run "dsa.msc".) Ensure Advanced Features is selected in the View menu. For each OU that is defined (folder in folder icon) excluding the Domain Controllers OU: Right click the OU and select Properties. Select the Security tab. If the permissions on the OU are not at least as restrictive as those below, this is a finding. The permissions shown are at the summary level. More detailed permissions can be viewed by selecting the next Advanced button, selecting the desired Permission entry and the Edit button. Self - Special permissions Authenticated Users - Read, Special permissions The Special permissions for Authenticated Users are Read type. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. SYSTEM - Full Control Domain Admins - Full Control Enterprise Admins - Full Control Administrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions Pre-Windows 2000 Compatible Access - Special permissions The Special permissions for Pre-Windows 2000 Compatible Access are for Read types. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions If an ISSO-approved distributed administration model (help desk or other user support staff) is implemented, permissions above Read may be allowed for groups documented by the ISSO.

Fix: F-27764r794775_fix

Ensure the permissions on domain defined OUs are at least as restrictive as the defaults below. Document any additional permissions above read with the ISSO if an approved distributed administration model (help desk or other user support staff) is implemented. Self - Special permissions Authenticated Users - Read, Special permissions The Special permissions for Authenticated Users are Read type. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. SYSTEM - Full Control Domain Admins - Full Control Enterprise Admins - Full Control Administrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions Pre-Windows 2000 Compatible Access - Special permissions The Special permissions for Pre-Windows 2000 Compatible Access are for Read types. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions Severity Override Guidance: If any OU with improper permissions includes identification or authentication data (e.g., accounts, passwords, or password hash data) used by systems to determine access control, the severity is CAT I (e.g., OUs that include user accounts, including service/application accounts). If the OU with improper permissions does not include identification and authentication data used by systems to determine access control, the severity is CAT II (e.g., Workstation, Printer OUs).

b

Data files owned by users must be on a different logical partition from the directory server data files.

SC-2 - Medium - CCI-001082 - V-226075 - SV-226075r794310_rule

RMF Control

SC-2

Severity

M

CCI

CCI-001082

Version

WN12-AD-000006-DC

Vuln IDs

V-226075
V-8317

Rule IDs

SV-226075r794310_rule
SV-51180

When directory service data files, especially for directories used for identification, authentication, or authorization, reside on the same logical partition as user-owned files, the directory service data may be more vulnerable to unauthorized access or other availability compromises. Directory service and user-owned data files sharing a partition may be configured with less restrictive permissions in order to allow access to the user data. The directory service may be vulnerable to a denial of service attack when user-owned files on a common partition are expanded to an extent preventing the directory service from acquiring more space for directory or audit data.

Checks: C-27777r475548_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-27765r475549_fix

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

b

Time synchronization must be enabled on the domain controller.

AU-8 - Medium - CCI-001891 - V-226076 - SV-226076r794807_rule

RMF Control

AU-8

Severity

M

CCI

CCI-001891

Version

WN12-AD-000007-DC

Vuln IDs

V-226076
V-8322

Rule IDs

SV-226076r794807_rule
SV-51181

When a directory service using multi-master replication (such as AD) executes on computers that do not have synchronized time, directory data may be corrupted or updated invalidly. The lack of synchronized time could lead to audit log data that is misleading, inconclusive, or unusable. In cases of intrusion this may invalidate the audit data as a source of forensic evidence in an incident investigation. In AD, the lack of synchronized time could prevent clients from logging on or accessing server resources as a result of Kerberos requirements related to time variance.

Checks: C-27778r475551_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-27766r794806_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

a

The time synchronization tool must be configured to enable logging of time source switching.

CM-6 - Low - CCI-000366 - V-226077 - SV-226077r794796_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN12-AD-000008-DC

Vuln IDs

V-226077
V-8324

Rule IDs

SV-226077r794796_rule
SV-51182

When a time synchronization tool executes, it may switch between time sources according to network or server contention. If switches between time sources are not logged, it may be difficult or impossible to detect malicious activity or availability problems.

Checks: C-27779r475554_chk

Verify logging is configured to capture time source switches. If the Windows Time Service is used, verify the following registry value. If it is not configured as specified, this is a finding. Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \System\CurrentControlSet\Services\W32Time\Config\ Value Name: EventLogFlags Type: REG_DWORD Value: 2 or 3 If another time synchronization tool is used, review the available configuration options and logs. If the tool has time source logging capability and it is not enabled, this is a finding.

Fix: F-27767r794795_fix

Configure the time synchronization tool to log time source switching. If the Windows Time Service is used, configure the following registry value. Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \System\CurrentControlSet\Services\W32Time\Config\ Value Name: EventLogFlags Type: REG_DWORD Value: 2 or 3

b

The directory server supporting (directly or indirectly) system access or resource authorization must run on a machine dedicated to that function.

SC-2 - Medium - CCI-001082 - V-226078 - SV-226078r794311_rule

RMF Control

SC-2

Severity

M

CCI

CCI-001082

Version

WN12-AD-000009-DC

Vuln IDs

V-226078
V-8326

Rule IDs

SV-226078r794311_rule
SV-51183

Executing application servers on the same host machine with a directory server may substantially weaken the security of the directory server. Web or database server applications usually require the addition of many programs and accounts increasing the attack surface of the computer. Some applications require the addition of privileged accounts providing potential sources of compromise. Some applications (such as MS Exchange) may require the use of network ports or services conflicting with the directory server. In this case, non-standard ports might be selected and this could interfere with intrusion detection or prevention services.

Checks: C-27780r475557_chk

Review the roles and services the domain controller is running. 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. Installed roles can be displayed by viewing Server Roles in the Add (or Remove) Roles and Features wizard. (Cancel before any changes are made.) Determine if any additional server roles are installed. A basic domain controller set up will include the following: -Active Directory Domain Services -DNS Server -File and Storage Services If any roles not requiring installation on a domain controller are installed, 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-27768r475558_fix

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

b

Windows services that are critical for directory server operation must be configured for automatic startup.

CM-6 - Medium - CCI-000366 - V-226079 - SV-226079r794798_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-AD-000010-DC

Vuln IDs

V-226079
V-8327

Rule IDs

SV-226079r794798_rule
SV-51184

Active Directory (AD) is dependent on several Windows services. If one or more of these services is not configured for automatic startup, AD functions may be partially or completely unavailable until the services are manually started. This could result in a failure to replicate data or to support client authentication and authorization requests.

Checks: C-27781r475560_chk

Run "services.msc" to display the Services console. Verify the Startup Type for the following Windows services: - Active Directory Domain Services - DFS Replication - DNS Client - DNS server - Group Policy Client - Intersite Messaging - Kerberos Key Distribution Center - NetLogon - 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-27769r794797_fix

Ensure the following services that are critical for directory server operation are configured for automatic startup. - Active Directory Domain Services - DFS Replication - DNS Client - DNS server - Group Policy Client - Intersite Messaging - Kerberos Key Distribution Center - NetLogon - Windows Time (not required if another time synchronization tool is implemented to start automatically)

b

Separate, NSA-approved (Type 1) cryptography must be used to protect the directory data-in-transit for directory service implementations at a classified confidentiality level when replication data traverses a network cleared to a lower level than the data

SC-13 - Medium - CCI-002450 - V-226080 - SV-226080r794334_rule

RMF Control

SC-13

Severity

M

CCI

CCI-002450

Version

WN12-AD-000011-DC

Vuln IDs

V-226080
V-14783

Rule IDs

SV-226080r794334_rule
SV-51185

Commercial-grade encryption does not provide adequate protection when the classification level of directory data in transit is higher than the level of the network.

Checks: C-27782r475563_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-27770r475564_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.

a

Anonymous access to the root DSE of a non-public directory must be disabled.

CM-6 - Low - CCI-000366 - V-226081 - SV-226081r794800_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN12-AD-000012-DC

Vuln IDs

V-226081
V-14797

Rule IDs

SV-226081r794800_rule
SV-51186

Allowing anonymous access to the root DSE data on a directory server provides potential attackers with a number of details about the configuration and data contents of a directory. For example, the namingContexts attribute indicates the directory space contained in the directory; the supportedLDAPVersion attribute indicates which versions of the LDAP protocol the server supports; and the supportedSASLMechanisms attribute indicates the names of supported authentication mechanisms. An attacker with this information may be able to select more precisely targeted attack tools or higher value targets.

Checks: C-27783r475566_chk

At this time, this is a finding for all Windows domain controllers for sensitive or classified levels as Windows Active Directory Domain Services (AD DS) does not provide a method to restrict anonymous access to the root DSE on domain controllers. The following can be used to verify anonymous access is allowed. Open a command prompt (not elevated). Run "ldp.exe". From the Connection menu, select Bind. Clear the User, Password, and Domain fields. Select Simple bind for the Bind type, Click OK. RootDSE attributes should display, such as various namingContexts. Confirmation of anonymous access will be displayed at the end: res = ldap_simple_bind_s Authenticated as: 'NT AUTHORITY\ANONYMOUS LOGON'

Fix: F-27771r794799_fix

Implement network protections to reduce the risk of anonymous access. Network hardware ports at the site are subject to 802.1x authentication or MAC address restrictions. Premise firewall or host restrictions prevent access to ports 389, 636, 3268, and 3269 from client hosts not explicitly identified by domain (.mil) or IP address. Severity Override Guidance: The following network controls allow the finding severity to be downgraded to not a finding since these measures lower the risk associated with anonymous access.

c

Directory data (outside the root DSE) of a non-public directory must be configured to prevent anonymous access.

CM-6 - High - CCI-000366 - V-226082 - SV-226082r794802_rule

RMF Control

CM-6

Severity

H

CCI

Version

WN12-AD-000013-DC

Vuln IDs

V-226082
V-14798

Rule IDs

SV-226082r794802_rule
SV-51187

To the extent that anonymous access to directory data (outside the root DSE) is permitted, read access control of the data is effectively disabled. If other means of controlling access (such as, network restrictions) are compromised, there may be nothing else to protect the confidentiality of sensitive directory data.

Checks: C-27784r475569_chk

Verify anonymous access is not allowed to the AD domain naming context. Open a command prompt (not elevated). Run "ldp.exe". From the Connection menu, select Bind. Clear the User, Password, and Domain fields. Select Simple bind for the Bind type, Click OK. Confirmation of anonymous access will be displayed at the end: res = ldap_simple_bind_s Authenticated as: 'NT AUTHORITY\ANONYMOUS LOGON' From the Browse menu, select Search. In the Search dialog, enter the DN of the domain naming context (generally something like "dc=disaost,dc=mil") in the Base DN field. Clear the Attributes field and select Run. Error messages should display related to bind and user not authenticated. If attribute data is displayed, anonymous access is enabled to the domain naming context and this is a finding.

Fix: F-27772r794801_fix

Configure directory data (outside the root DSE) of a non-public directory to prevent anonymous access. For AD, there are multiple configuration items that could enable anonymous access. Changing the access permissions on the domain naming context object (from the secure defaults) could enable anonymous access. If the check procedures indicate this is the cause, the process that was used to change the permissions should be reversed. This could have been through the Windows Support Tools ADSI Edit console (adsiedit.msc). The dsHeuristics option is used. This is addressed in check V-8555 in the AD Forest STIG. Severity Override Guidance: The following network controls allow the finding severity to be downgraded to a CAT II since these measures lower the risk associated with anonymous access. Network hardware ports at the site are subject to 802.1x authentication or MAC address restrictions. Premise firewall or host restrictions prevent access to ports 389, 636, 3268, and 3269 from client hosts not explicitly identified by domain (.mil) or IP address.

a

The directory service must be configured to terminate LDAP-based network connections to the directory server after five (5) minutes of inactivity.

SC-10 - Low - CCI-001133 - V-226083 - SV-226083r794805_rule

RMF Control

SC-10

Severity

L

CCI

Version

WN12-AD-000014-DC

Vuln IDs

V-226083
V-14831

Rule IDs

SV-226083r794805_rule
SV-51188

The failure to terminate inactive network connections increases the risk of a successful attack on the directory server. The longer an established session is in progress, the more time an attacker has to hijack the session, implement a means to passively intercept data, or compromise any protections on client access. For example, if an attacker gains control of a client computer, an existing (already authenticated) session with the directory server could allow access to the directory. The lack of confidentiality protection in LDAP-based sessions increases exposure to this vulnerability.

Checks: C-27785r794803_chk

Verify the value for MaxConnIdleTime. Open an elevated command prompt. Enter "ntdsutil". At the "ntdsutil:" prompt, enter "LDAP policies". At the "ldap policy:" prompt, enter "connections". At the "server connections:" prompt, enter "connect to server [host-name]". (Where [host-name] is the computer name of the domain controller.) At the "server connections:" prompt, enter "q". At the "ldap policy:" prompt, enter "show values". If the value for MaxConnIdleTime is greater than 300 (the value for five minutes) or it is not specified, this is a finding. Enter "q" at the "ldap policy:" and "ntdsutil:" prompts to exit. Alternately, Dsquery can be used to display MaxConnIdleTime: Open an elevated command prompt. Enter the following command (on a single line). dsquery * "cn=Default Query Policy,cn=Query-Policies,cn=Directory Service, cn=Windows NT,cn=Services,cn=Configuration,dc=[forest-name]" -attr LDAPAdminLimits The quotes are required and dc=[forest-name] is the fully qualified LDAP name of the domain being reviewed (e.g., dc=disaost,dc=mil).

Fix: F-27773r794804_fix

Configure the directory service to terminate LDAP-based network connections to the directory server after five (5) minutes of inactivity. Open an elevated command prompt. Enter "ntdsutil". At the "ntdsutil:" prompt, enter "LDAP policies". At the "ldap policy:" prompt, enter "connections". At the "server connections:" prompt, enter "connect to server [host-name]". (Where [host-name] is the computer name of the domain controller.) At the "server connections:" prompt, enter "q". At the "ldap policy:" prompt, enter "Set MaxConnIdleTime to 300". Enter "Commit Changes" to save. Enter "Show values" to verify changes. Enter "q" at the "ldap policy:" and "ntdsutil:" prompts to exit.

b

The password for the krbtgt account on a domain must be reset at least every 180 days.

CM-6 - Medium - CCI-000366 - V-226084 - SV-226084r794809_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-AD-000015-DC

Vuln IDs

V-226084
V-91777

Rule IDs

SV-226084r794809_rule
SV-101879

The krbtgt account acts as a service account for the Kerberos Key Distribution Center (KDC) service. The account and password are created when a domain is created and the password is typically not changed. If the krbtgt account is compromised, attackers can create valid Kerberos Ticket Granting Tickets (TGT). The password must be changed twice to effectively remove the password history.Changing once, waiting for replication to complete and the amount of time equal to or greater than the maximum Kerberos ticket lifetime, and changing again reduces the risk of issues.

Checks: C-27786r475575_chk

This requirement is applicable to domain controllers; it is NA for other systems. Open "Windows PowerShell". Enter "Get-ADUser krbtgt -Property PasswordLastSet". If the "PasswordLastSet" date is more than 180 days old, this is a finding.

Fix: F-27774r794808_fix

Reset the password for the krbtgt account a least every 180 days. The password must be changed twice to effectively remove the password history. Changing once, waiting for replication to complete and changing again reduces the risk of issues. Changing twice in rapid succession forces clients to re-authenticate (including application services) but is desired if a compromise is suspected. PowerShell scripts are available to accomplish this such as at the following link: https://gallery.technet.microsoft.com/Reset-the-krbtgt-account-581a9e51 Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). Select "Advanced Features" in the "View" menu if not previously selected. Select the "Users" node. Right click on the krbtgt account and select "Reset password". Enter a password that meets password complexity requirements. Clear the "User must change password at next logon" check box. The system will automatically change this to a system generated complex password.

b

The system must be configured to audit Account Logon - Credential Validation successes.

AU-12 - Medium - CCI-000172 - V-226085 - SV-226085r794339_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000001

Vuln IDs

V-226085
V-26529

Rule IDs

SV-226085r794339_rule
SV-53013

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Credential validation records events related to validation tests on credentials for a user account logon.

Checks: C-27787r475578_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*". Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. Account Logon -> Credential Validation - Success

Fix: F-27775r475579_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Account Logon -> "Audit Credential Validation" with "Success" selected.

b

The system must be configured to audit Account Logon - Credential Validation failures.

AU-12 - Medium - CCI-000172 - V-226086 - SV-226086r794340_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000002

Vuln IDs

V-226086
V-26530

Rule IDs

SV-226086r794340_rule
SV-53011

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Credential validation records events related to validation tests on credentials for a user account logon.

Checks: C-27788r475581_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*". Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. Account Logon -> Credential Validation - Failure

Fix: F-27776r475582_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Account Logon -> "Audit Credential Validation" with "Failure" selected.

b

Windows Server 2012/2012 R2 domain controllers must be configured to audit Account Management - Computer Account Management successes.

AU-12 - Medium - CCI-000172 - V-226087 - SV-226087r794341_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000011-DC

Vuln IDs

V-226087
V-26531

Rule IDs

SV-226087r794341_rule
SV-52234

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Computer Account Management records events such as creating, changing, deleting, renaming, disabling, or enabling computer accounts.

Checks: C-27789r475584_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*". Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. Account Management >> Computer Account Management - Success

Fix: F-27777r475585_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Account Management >> "Audit Computer Account Management" with "Success" selected.

b

The system must be configured to audit Account Management - Other Account Management Events successes.

AU-12 - Medium - CCI-000172 - V-226088 - SV-226088r794342_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000015

Vuln IDs

V-226088
V-26533

Rule IDs

SV-226088r794342_rule
SV-53009

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Other Account Management Events records events such as the access of a password hash or the Password Policy Checking API being called.

Checks: C-27790r475587_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*". Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. Account Management -> Other Account Management Events - Success

Fix: F-27778r475588_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Account Management -> "Audit Other Account Management Events" with "Success" selected.

b

The system must be configured to audit Account Management - Security Group Management successes.

AC-2 - Medium - CCI-000018 - V-226089 - SV-226089r794274_rule

RMF Control

AC-2

Severity

M

CCI

CCI-000018

Version

WN12-AU-000017

Vuln IDs

V-226089
V-26535

Rule IDs

SV-226089r794274_rule
SV-53007

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Security Group Management records events such as creating, deleting, or changing security groups, including changes in group members.

Checks: C-27791r475590_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*". Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. Account Management -> Security Group Management - Success

Fix: F-27779r475591_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Account Management -> "Audit Security Group Management" with "Success" selected.

b

The system must be configured to audit Account Management - User Account Management successes.

AC-2 - Medium - CCI-000018 - V-226090 - SV-226090r794275_rule

RMF Control

AC-2

Severity

M

CCI

CCI-000018

Version

WN12-AU-000019

Vuln IDs

V-226090
V-26537

Rule IDs

SV-226090r794275_rule
SV-53003

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. User Account Management records events such as creating, changing, deleting, renaming, disabling, or enabling user accounts.

Checks: C-27792r475593_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*". Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. Account Management -> User Account Management - Success

Fix: F-27780r475594_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Account Management -> "Audit User Account Management" with "Success" selected.

b

The system must be configured to audit Account Management - User Account Management failures.

AC-2 - Medium - CCI-000018 - V-226091 - SV-226091r794276_rule

RMF Control

AC-2

Severity

M

CCI

CCI-000018

Version

WN12-AU-000020

Vuln IDs

V-226091
V-26538

Rule IDs

SV-226091r794276_rule
SV-53001

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. User Account Management records events such as creating, changing, deleting, renaming, disabling, or enabling user accounts.

Checks: C-27793r475596_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*". Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. Account Management -> User Account Management - Failure

Fix: F-27781r475597_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Account Management -> "Audit User Account Management" with "Failure" selected.

b

The system must be configured to audit Detailed Tracking - Process Creation successes.

AU-12 - Medium - CCI-000172 - V-226092 - SV-226092r794343_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000023

Vuln IDs

V-226092
V-26539

Rule IDs

SV-226092r794343_rule
SV-52999

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Process Creation records events related to the creation of a process and the source.

Checks: C-27794r475599_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*". Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. Detailed Tracking -> Process Creation - Success

Fix: F-27782r475600_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Detailed Tracking -> "Audit Process Creation" with "Success" selected.

b

Windows Server 2012/2012 R2 must be configured to audit Logon/Logoff - Account Lockout successes.

AU-12 - Medium - CCI-000172 - V-226093 - SV-226093r794360_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000030

Vuln IDs

V-226093
V-78057

Rule IDs

SV-226093r794360_rule
SV-92765

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Account Lockout events can be used to identify potentially malicious logon attempts.

Checks: C-27795r475602_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: Open an elevated "Command Prompt" (run as administrator). Enter "AuditPol /get /category:*" Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. Logon/Logoff >> Account Lockout - Success

Fix: F-27783r475603_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> "Audit Account Lockout" with "Success" selected.

b

Windows Server 2012/2012 R2 must be configured to audit Logon/Logoff - Account Lockout failures.

AU-12 - Medium - CCI-000172 - V-226094 - SV-226094r794361_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000031

Vuln IDs

V-226094
V-78059

Rule IDs

SV-226094r794361_rule
SV-92769

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Account Lockout events can be used to identify potentially malicious logon attempts.

Checks: C-27796r475605_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: Open an elevated "Command Prompt" (run as administrator). Enter "AuditPol /get /category:*" Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. Logon/Logoff >> Account Lockout - Failure

Fix: F-27784r475606_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> "Audit Account Lockout" with "Failure" selected.

b

The system must be configured to audit DS Access - Directory Service Access successes.

AU-12 - Medium - CCI-000172 - V-226095 - SV-226095r794782_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000031-DC

Vuln IDs

V-226095
V-33663

Rule IDs

SV-226095r794782_rule
SV-51151

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detecting attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Audit directory service access records events related to users accessing an Active Directory object.

Checks: C-27797r475608_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*". Compare the Auditpol settings with the following. If the system does not audit the following, this is a finding. DS Access -> Directory Service Access - Success

Fix: F-27785r794781_fix

Detailed auditing subcategories are configured in Security Settings -> Advanced Audit Policy Configuration. The summary level settings under Security Settings -> Local Policies -> Audit Policy will not be enforced (see V-14230). Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> DS Access -> "Directory Service Access" with "Success" selected.

b

The system must be configured to audit DS Access - Directory Service Access failures.

AU-12 - Medium - CCI-000172 - V-226096 - SV-226096r794784_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000032-DC

Vuln IDs

V-226096
V-33664

Rule IDs

SV-226096r794784_rule
SV-51152

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detecting attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Audit directory service access records events related to users accessing an Active Directory object.

Checks: C-27798r475611_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*". Compare the Auditpol settings with the following. If the system does not audit the following, this is a finding. DS Access -> Directory Service Access - Failure

Fix: F-27786r794783_fix

Detailed auditing subcategories are configured in Security Settings -> Advanced Audit Policy Configuration. The summary level settings under Security Settings -> Local Policies -> Audit Policy will not be enforced (see V-14230). Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> DS Access -> "Directory Service Access" with "Failure" selected.

b

The system must be configured to audit DS Access - Directory Service Changes successes.

AU-12 - Medium - CCI-000172 - V-226097 - SV-226097r794786_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000035-DC

Vuln IDs

V-226097
V-33665

Rule IDs

SV-226097r794786_rule
SV-51153

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detecting attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Audit directory service changes records events related to changes made to objects in Active Directory Domain Services.

Checks: C-27799r475614_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*". Compare the Auditpol settings with the following. If the system does not audit the following, this is a finding. DS Access -> Directory Service Changes - Success

Fix: F-27787r794785_fix

Detailed auditing subcategories are configured in Security Settings -> Advanced Audit Policy Configuration. The summary level settings under Security Settings -> Local Policies -> Audit Policy will not be enforced (see V-14230). Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> DS Access -> "Directory Service Changes" with "Success" selected.

b

The system must be configured to audit DS Access - Directory Service Changes failures.

AU-12 - Medium - CCI-000172 - V-226098 - SV-226098r794788_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000036-DC

Vuln IDs

V-226098
V-33666

Rule IDs

SV-226098r794788_rule
SV-51155

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detecting attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Audit directory service changes records events related to changes made to objects in Active Directory Domain Services.

Checks: C-27800r475617_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*". Compare the Auditpol settings with the following. If the system does not audit the following, this is a finding. DS Access -> Directory Service Changes - Failure

Fix: F-27788r794787_fix

Detailed auditing subcategories are configured in Security Settings -> Advanced Audit Policy Configuration. The summary level settings under Security Settings -> Local Policies -> Audit Policy will not be enforced (see V-14230). Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> DS Access -> "Directory Service Changes" with "Failure" selected.

b

The system must be configured to audit Logon/Logoff - Logoff successes.

AC-17 - Medium - CCI-000067 - V-226099 - SV-226099r794279_rule

RMF Control

AC-17

Severity

M

CCI

CCI-000067

Version

WN12-AU-000045

Vuln IDs

V-226099
V-26540

Rule IDs

SV-226099r794279_rule
SV-52996

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Logoff records user logoffs. If this is an interactive logoff, it is recorded on the local system. If it is to a network share, it is recorded on the system accessed.

Checks: C-27801r475620_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*". Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. Logon/Logoff -> Logoff - Success

Fix: F-27789r475621_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Logon/Logoff -> "Audit Logoff" with "Success" selected.

b

The system must be configured to audit Logon/Logoff - Logon successes.

AC-17 - Medium - CCI-000067 - V-226100 - SV-226100r794280_rule

RMF Control

AC-17

Severity

M

CCI

CCI-000067

Version

WN12-AU-000047

Vuln IDs

V-226100
V-26541

Rule IDs

SV-226100r794280_rule
SV-52994

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Logon records user logons. If this is an interactive logon, it is recorded on the local system. If it is to a network share, it is recorded on the system accessed.

Checks: C-27802r475623_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*". Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. Logon/Logoff -> Logon - Success

Fix: F-27790r475624_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Logon/Logoff -> "Audit Logon" with "Success" selected.

b

The system must be configured to audit Logon/Logoff - Logon failures.

AC-17 - Medium - CCI-000067 - V-226101 - SV-226101r794281_rule

RMF Control

AC-17

Severity

M

CCI

CCI-000067

Version

WN12-AU-000048

Vuln IDs

V-226101
V-26542

Rule IDs

SV-226101r794281_rule
SV-52993

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Logon records user logons. If this is an interactive logon, it is recorded on the local system. If it is to a network share, it is recorded on the system accessed.

Checks: C-27803r475626_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*". Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. Logon/Logoff -> Logon - Failure

Fix: F-27791r475627_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Logon/Logoff -> "Audit Logon" with "Failure" selected.

b

The system must be configured to audit Logon/Logoff - Special Logon successes.

AU-12 - Medium - CCI-000172 - V-226102 - SV-226102r794335_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000053

Vuln IDs

V-226102
V-26543

Rule IDs

SV-226102r794335_rule
SV-52987

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Special Logon records special logons which have administrative privileges and can be used to elevate processes.

Checks: C-27804r475629_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*". Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. Logon/Logoff -> Special Logon - Success

Fix: F-27792r475630_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Logon/Logoff -> "Audit Special Logon" with "Success" selected.

b

The system must be configured to audit Object Access - Central Access Policy Staging successes.

AU-12 - Medium - CCI-000172 - V-226103 - SV-226103r794362_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000059

Vuln IDs

V-226103
V-40202

Rule IDs

SV-226103r794362_rule
SV-52161

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Central Access Policy Staging auditing under Object Access is used to enable the recording of events related to differences in permissions between central access policies and proposed policies.

Checks: C-27805r475632_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*". Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. Object Access -> Central Policy Staging - Success

Fix: F-27793r475633_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Object Access -> "Audit Central Access Policy Staging" with "Success" selected.

b

The system must be configured to audit Object Access - Central Access Policy Staging failures.

AU-12 - Medium - CCI-000172 - V-226104 - SV-226104r794363_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000060

Vuln IDs

V-226104
V-40200

Rule IDs

SV-226104r794363_rule
SV-52159

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Central Access Policy Staging auditing under Object Access is used to enable the recording of events related to differences in permissions between central access policies and proposed policies.

Checks: C-27806r475635_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*". Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. Object Access -> Central Policy Staging - Failure

Fix: F-27794r475636_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Object Access -> "Audit Central Access Policy Staging" with "Failure" selected.

b

The system must be configured to audit Object Access - Removable Storage successes.

AU-12 - Medium - CCI-000172 - V-226105 - SV-226105r794364_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000081

Vuln IDs

V-226105
V-36668

Rule IDs

SV-226105r794364_rule
SV-51601

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Removable Storage auditing under Object Access records events related to access attempts on file system objects on removable storage devices.

Checks: C-27807r475638_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*" Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. Object Access >> Removable Storage - Success Virtual machines or systems that use network attached storage may generate excessive audit events for secondary virtual drives or the network attached storage when this setting is enabled. This may be set to Not Configured in such cases and would not be a finding.

Fix: F-27795r475639_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> "Audit Removable Storage" with "Success" selected.

b

The system must be configured to audit Object Access - Removable Storage failures.

AU-12 - Medium - CCI-000172 - V-226106 - SV-226106r794365_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000082

Vuln IDs

V-226106
V-36667

Rule IDs

SV-226106r794365_rule
SV-51604

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Removable Storage auditing under Object Access records events related to access attempts on file system objects on removable storage devices.

Checks: C-27808r475641_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*" Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. Object Access >> Removable Storage - Failure Virtual machines or systems that use network attached storage may generate excessive audit events for secondary virtual drives or the network attached storage when this setting is enabled. This may be set to Not Configured in such cases and would not be a finding.

Fix: F-27796r475642_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> "Audit Removable Storage" with "Failure" selected.

b

The system must be configured to audit Policy Change - Audit Policy Change successes.

AU-12 - Medium - CCI-000172 - V-226107 - SV-226107r794336_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000085

Vuln IDs

V-226107
V-26546

Rule IDs

SV-226107r794336_rule
SV-52983

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Audit Policy Change records events related to changes in audit policy.

Checks: C-27809r475644_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*". Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. Policy Change -> Audit Policy Change - Success

Fix: F-27797r475645_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Policy Change -> "Audit Audit Policy Change" with "Success" selected.

b

The system must be configured to audit Policy Change - Audit Policy Change failures.

AU-12 - Medium - CCI-000172 - V-226108 - SV-226108r794352_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000086

Vuln IDs

V-226108
V-26547

Rule IDs

SV-226108r794352_rule
SV-52982

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Audit Policy Change records events related to changes in audit policy.

Checks: C-27810r475647_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*". Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. Policy Change -> Audit Policy Change - Failure

Fix: F-27798r475648_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Policy Change -> "Audit Audit Policy Change" with "Failure" selected.

b

The system must be configured to audit Policy Change - Authentication Policy Change successes.

AU-12 - Medium - CCI-000172 - V-226109 - SV-226109r794353_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000087

Vuln IDs

V-226109
V-26548

Rule IDs

SV-226109r794353_rule
SV-52981

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Authentication Policy Change records events related to changes in authentication policy, including Kerberos policy and Trust changes.

Checks: C-27811r475650_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*". Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. Policy Change -> Authentication Policy Change - Success

Fix: F-27799r475651_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Policy Change -> "Audit Authentication Policy Change" with "Success" selected.

b

The system must be configured to audit Policy Change - Authorization Policy Change successes.

AU-12 - Medium - CCI-000172 - V-226110 - SV-226110r794366_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000089

Vuln IDs

V-226110
V-57633

Rule IDs

SV-226110r794366_rule
SV-72043

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Authorization Policy Change records events related to changes in user rights, such as Create a token object.

Checks: C-27812r475653_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*". Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. Policy Change -> Authorization Policy Change - Success

Fix: F-27800r475654_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Policy Change -> "Audit Authorization Policy Change" with "Success" selected.

b

The system must be configured to audit Privilege Use - Sensitive Privilege Use successes.

AU-12 - Medium - CCI-000172 - V-226111 - SV-226111r794354_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000101

Vuln IDs

V-226111
V-26549

Rule IDs

SV-226111r794354_rule
SV-52980

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Sensitive Privilege Use records events related to use of sensitive privileges, such as "Act as part of the operating system" or "Debug programs".

Checks: C-27813r475656_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*". Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. Privilege Use -> Sensitive Privilege Use - Success

Fix: F-27801r475657_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Privilege Use -> "Audit Sensitive Privilege Use" with "Success" selected.

b

The system must be configured to audit Privilege Use - Sensitive Privilege Use failures.

AU-12 - Medium - CCI-000172 - V-226112 - SV-226112r794355_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000102

Vuln IDs

V-226112
V-26550

Rule IDs

SV-226112r794355_rule
SV-52979

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Sensitive Privilege Use records events related to use of sensitive privileges, such as "Act as part of the operating system" or "Debug programs".

Checks: C-27814r475659_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*". Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. Privilege Use -> Sensitive Privilege Use - Failure

Fix: F-27802r475660_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> Privilege Use -> "Audit Sensitive Privilege Use" with "Failure" selected.

b

The system must be configured to audit System - IPsec Driver successes.

AU-12 - Medium - CCI-000172 - V-226113 - SV-226113r794367_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000103

Vuln IDs

V-226113
V-26551

Rule IDs

SV-226113r794367_rule
SV-52978

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. IPsec Driver records events related to the IPSec Driver such as dropped packets.

Checks: C-27815r475662_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*". Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. System -> IPsec Driver - Success

Fix: F-27803r475663_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> System -> "Audit IPsec Driver" with "Success" selected.

b

The system must be configured to audit System - IPsec Driver failures.

AU-12 - Medium - CCI-000172 - V-226114 - SV-226114r794368_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000104

Vuln IDs

V-226114
V-26552

Rule IDs

SV-226114r794368_rule
SV-52977

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. IPsec Driver records events related to the IPsec Driver such as dropped packets.

Checks: C-27816r475665_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*". Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. System -> IPsec Driver - Failure

Fix: F-27804r475666_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> System -> "Audit IPsec Driver" with "Failure" selected.

b

Windows Server 2012/2012 R2 must be configured to audit System - Other System Events successes.

AU-12 - Medium - CCI-000172 - V-226115 - SV-226115r794290_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000105

Vuln IDs

V-226115
V-78061

Rule IDs

SV-226115r794290_rule
SV-92773

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Audit Other System Events records information related to cryptographic key operations and the Windows Firewall service. Satisfies: SRG-OS-000458-GPOS-00203

Checks: C-27817r475668_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: Open an elevated "Command Prompt" (run as administrator). Enter "AuditPol /get /category:*" Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. System >> Other System Events - Success

Fix: F-27805r475669_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> System >> "Audit Other System Events" with "Success" selected.

b

Windows Server 2012/2012 R2 must be configured to audit System - Other System Events failures.

AU-12 - Medium - CCI-000172 - V-226116 - SV-226116r794291_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000106

Vuln IDs

V-226116
V-78063

Rule IDs

SV-226116r794291_rule
SV-92781

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Audit Other System Events records information related to cryptographic key operations and the Windows Firewall service. Satisfies: SRG-OS-000458-GPOS-00203

Checks: C-27818r475671_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: Open an elevated "Command Prompt" (run as administrator). Enter "AuditPol /get /category:*". Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. System >> Other System Events - Failure

Fix: F-27806r475672_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> System >> "Audit Other System Events" with "Failure" selected.

b

The system must be configured to audit System - Security State Change successes.

AU-12 - Medium - CCI-000172 - V-226117 - SV-226117r794356_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000107

Vuln IDs

V-226117
V-26553

Rule IDs

SV-226117r794356_rule
SV-52976

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Security State Change records events related to changes in the security state, such as startup and shutdown of the system.

Checks: C-27819r475674_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*". Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. System -> Security State Change - Success

Fix: F-27807r475675_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> System -> "Audit Security State Change" with "Success" selected.

b

The system must be configured to audit System - Security System Extension successes.

AU-12 - Medium - CCI-000172 - V-226118 - SV-226118r794357_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000109

Vuln IDs

V-226118
V-26555

Rule IDs

SV-226118r794357_rule
SV-52974

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Security System Extension records events related to extension code being loaded by the security subsystem.

Checks: C-27820r475677_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*". Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. System -> Security System Extension - Success

Fix: F-27808r475678_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> System -> "Audit Security System Extension" with "Success" selected.

b

The system must be configured to audit System - System Integrity successes.

AU-12 - Medium - CCI-000172 - V-226119 - SV-226119r794358_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000111

Vuln IDs

V-226119
V-26557

Rule IDs

SV-226119r794358_rule
SV-52972

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. System Integrity records events related to violations of integrity to the security subsystem.

Checks: C-27821r475680_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*". Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. System -> System Integrity - Success

Fix: F-27809r475681_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> System -> "Audit System Integrity" with "Success" selected.

b

The system must be configured to audit System - System Integrity failures.

AU-12 - Medium - CCI-000172 - V-226120 - SV-226120r794359_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000112

Vuln IDs

V-226120
V-26558

Rule IDs

SV-226120r794359_rule
SV-52971

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. System Integrity records events related to violations of integrity to the security subsystem.

Checks: C-27822r475683_chk

Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: -Open a Command Prompt with elevated privileges ("Run as Administrator"). -Enter "AuditPol /get /category:*". Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. System -> System Integrity - Failure

Fix: F-27810r475684_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> System Audit Policies -> System -> "Audit System Integrity" with "Failure" selected.

b

Audit data must be reviewed on a regular basis.

CM-6 - Medium - CCI-000366 - V-226121 - SV-226121r794316_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-AU-000200

Vuln IDs

V-226121
V-36670

Rule IDs

SV-226121r794316_rule
SV-51561

To be of value, audit logs from critical systems must be reviewed on a regular basis. Critical systems should be reviewed on a daily basis to identify security breaches and potential weaknesses in the security structure. This can be done with the use of monitoring software or other utilities for this purpose.

Checks: C-27823r475686_chk

Determine whether audit logs are reviewed on a predetermined schedule. If audit logs are not reviewed on a regular basis, this is a finding.

Fix: F-27811r475687_fix

Review audit logs on a predetermined scheduled.

b

Audit data must be retained for at least one year.

CM-6 - Medium - CCI-000366 - V-226122 - SV-226122r794317_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-AU-000201

Vuln IDs

V-226122
V-36671

Rule IDs

SV-226122r794317_rule
SV-51563

Audit records are essential for investigating system activity after the fact. Retention periods for audit data are determined based on the sensitivity of the data handled by the system.

Checks: C-27824r475689_chk

Determine whether audit data is retained for at least one year. If the audit data is not retained for at least a year, this is a finding.

Fix: F-27812r475690_fix

Ensure the audit data is retained for at least a year.

b

Audit records must be backed up onto a different system or media than the system being audited.

AU-4 - Medium - CCI-001851 - V-226123 - SV-226123r794330_rule

RMF Control

AU-4

Severity

M

CCI

CCI-001851

Version

WN12-AU-000203-01

Vuln IDs

V-226123
V-36672

Rule IDs

SV-226123r794330_rule
SV-51566

Protection of log data includes assuring the log data is not accidentally lost or deleted. Audit information stored in one location is vulnerable to accidental or incidental deletion or alteration.

Checks: C-27825r475692_chk

Determine if a process to back up log data to a different system or media than the system being audited has been implemented. If it has not, this is a finding.

Fix: F-27813r475693_fix

Establish and implement a process for backing up log data to another system or media other than the system being audited.

b

The operating system must, at a minimum, off-load audit records of interconnected systems in real time and off-load standalone systems weekly.

AU-4 - Medium - CCI-001851 - V-226124 - SV-226124r794331_rule

RMF Control

AU-4

Severity

M

CCI

CCI-001851

Version

WN12-AU-000203-02

Vuln IDs

V-226124
V-57719

Rule IDs

SV-226124r794331_rule
SV-72133

Protection of log data includes assuring the log data is not accidentally lost or deleted. Audit information stored in one location is vulnerable to accidental or incidental deletion or alteration.

Checks: C-27826r475695_chk

Verify the operating system, at a minimum, off-loads audit records of interconnected systems in real time and off-loads standalone systems weekly. If it does not, this is a finding.

Fix: F-27814r475696_fix

Configure the operating system to, at a minimum, off-load audit records of interconnected systems in real time and off-load standalone systems weekly.

b

Permissions for the Application event log must prevent access by nonprivileged accounts.

AU-9 - Medium - CCI-000162 - V-226125 - SV-226125r794760_rule

RMF Control

AU-9

Severity

M

CCI

Version

WN12-AU-000204

Vuln IDs

V-226125
V-36722

Rule IDs

SV-226125r794760_rule
SV-51569

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. The Application event log may be susceptible to tampering if proper permissions are not applied.

Checks: C-27827r475698_chk

Verify the permissions on the Application event log (Application.evtx). Standard user accounts or groups must not have greater than Read access. The default permissions listed below satisfy this requirement: Eventlog - Full Control SYSTEM - Full Control Administrators - Full Control The default location is the "%SystemRoot%\SYSTEM32\WINEVT\LOGS" directory. They may have been moved to another folder. If the permissions for these files are not as restrictive as the ACLs listed, this is a finding.

Fix: F-27815r794759_fix

Ensure the permissions on the Application event log (Application.evtx) are configured to prevent standard user accounts or groups from having greater than Read access. The default permissions listed below satisfy this requirement: Eventlog - Full Control SYSTEM - Full Control Administrators - Full Control The default location is the "%SystemRoot%\SYSTEM32\WINEVT\LOGS" directory. If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog".

b

Permissions for the Security event log must prevent access by nonprivileged accounts.

AU-9 - Medium - CCI-000162 - V-226126 - SV-226126r794762_rule

RMF Control

AU-9

Severity

M

CCI

Version

WN12-AU-000205

Vuln IDs

V-226126
V-36723

Rule IDs

SV-226126r794762_rule
SV-51571

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. The Security event log may disclose sensitive information or be susceptible to tampering if proper permissions are not applied.

Checks: C-27828r475701_chk

Verify the permissions on the Security event log (Security.evtx). Standard user accounts or groups must not have access. The default permissions listed below satisfy this requirement: Eventlog - Full Control SYSTEM - Full Control Administrators - Full Control The default location is the "%SystemRoot%\SYSTEM32\WINEVT\LOGS" directory. They may have been moved to another folder. If the permissions for these files are not as restrictive as the ACLs listed, this is a finding.

Fix: F-27816r794761_fix

Ensure the permissions on the Security event log (Security.evtx) are configured to prevent standard user accounts or groups from having access. The default permissions listed below satisfy this requirement: Eventlog - Full Control SYSTEM - Full Control Administrators - Full Control The default location is the "%SystemRoot%\SYSTEM32\WINEVT\LOGS" directory. If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog".

b

Permissions for the System event log must prevent access by nonprivileged accounts.

AU-9 - Medium - CCI-000162 - V-226127 - SV-226127r794764_rule

RMF Control

AU-9

Severity

M

CCI

Version

WN12-AU-000206

Vuln IDs

V-226127
V-36724

Rule IDs

SV-226127r794764_rule
SV-51572

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. The System event log may be susceptible to tampering if proper permissions are not applied.

Checks: C-27829r475704_chk

Verify the permissions on the System event log (System.evtx). Standard user accounts or groups must not have greater than Read access. The default permissions listed below satisfy this requirement: Eventlog - Full Control SYSTEM - Full Control Administrators - Full Control The default location is the "%SystemRoot%\SYSTEM32\WINEVT\LOGS" directory. They may have been moved to another folder. If the permissions for these files are not as restrictive as the ACLs listed, this is a finding.

Fix: F-27817r794763_fix

Ensure the permissions on the System event log (System.evtx) are configured to prevent standard user accounts or groups from having greater than Read access. The default permissions listed below satisfy this requirement: Eventlog - Full Control SYSTEM - Full Control Administrators - Full Control The default location is the "%SystemRoot%\SYSTEM32\WINEVT\LOGS" directory. If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog".

b

Active Directory Group Policy objects must be configured with proper audit settings.

AU-12 - Medium - CCI-000172 - V-226128 - SV-226128r794780_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000207-DC

Vuln IDs

V-226128
V-39325

Rule IDs

SV-226128r794780_rule
SV-51169

When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes Group Policy objects. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. Satisfies: SRG-OS-000471-GPOS-00215

Checks: C-27830r475707_chk

Review the auditing configuration for all Group Policy objects. 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 Principal - Everyone Access - Full Control Applies to - This object and all descendant objects or Descendant 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. Type - Success Principal - Everyone Access - Special (Permissions: Write all properties, Modify permissions; Properties: all "Write" type selected) Inherited from - Parent Object Applies to - Descendant groupPolicyContainer objects Two instances with the following summary information will be listed. Type - Success Principal - Everyone Access - blank (Permissions: none selected; Properties: one instance - Write gPLink, one instance - Write gPOptions) Inherited from - Parent Object Applies to - Descendant Organization Unit Objects

Fix: F-27818r794779_fix

Configure the audit settings for Group Policy objects to include the following. This can be done at the Policy level in Active Directory to apply to all group policies. Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). Select "Advanced Features" from the "View" Menu. Navigate to [Domain] >> System >> Policies in the left panel. Right click "Policies", select "Properties". Select the "Security" tab. Select the "Advanced" button. Select the "Auditing" tab. Type - Fail Principal - Everyone Access - Full Control Applies to - This object and all descendant objects or Descendant 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. Type - Success Principal - Everyone Access - Special (Permissions: Write all properties, Modify permissions; Properties: all "Write" type selected) Inherited from - Parent Object Applies to - Descendant groupPolicyContainer objects Two instances with the following summary information will be listed. Type - Success Principal - Everyone Access - blank (Permissions: none selected; Properties: one instance - Write gPLink, one instance - Write gPOptions) Inherited from - Parent Object Applies to - Descendant Organization Unit Objects

b

The Active Directory Domain object must be configured with proper audit settings.

AU-12 - Medium - CCI-000172 - V-226129 - SV-226129r794489_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000208-DC

Vuln IDs

V-226129
V-39326

Rule IDs

SV-226129r794489_rule
SV-51170

When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the Domain object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. Satisfies: SRG-OS-000471-GPOS-00215

Checks: C-27831r475710_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 Principal - Everyone Access - Full Control Inherited from - None Applies 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 Principal - Everyone Access - (blank) Inherited from - None Applies to - Special Type - Success Principal - Domain Users Access - All extended rights Inherited from - None Applies to - This object only Type - Success Principal - Administrators Access - All extended rights Inherited from - None Applies to - This object only Type - Success Principal - Everyone Access - Special Inherited from - None Applies to - This object only (Access - Special = Permissions: Write all properties, Modify permissions, Modify owner)

Fix: F-27819r475711_fix

Configure the audit settings for Domain object to include the following. Type - Fail Principal - Everyone Access - Full Control Inherited from - None Applies 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 Principal - Everyone Access - (blank) Inherited from - None Applies to - Special Type - Success Principal - Domain Users Access - All extended rights Inherited from - None Applies to - This object only Type - Success Principal - Administrators Access - All extended rights Inherited from - None Applies to - This object only Type - Success Principal - Everyone Access - Special Inherited from - None Applies to - This object only (Access - Special = Permissions: Write all properties, Modify permissions, Modify owner.)

b

The Active Directory Infrastructure object must be configured with proper audit settings.

AU-12 - Medium - CCI-000172 - V-226130 - SV-226130r794490_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000209-DC

Vuln IDs

V-226130
V-39327

Rule IDs

SV-226130r794490_rule
SV-51171

When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the Infrastructure object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. Satisfies: SRG-OS-000471-GPOS-00215

Checks: C-27832r475713_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 Principal - Everyone Access - Full Control Inherited from - None 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 Principal - Everyone Access - Special Inherited from - None (Access - Special = Permissions: Write all properties, All extended rights, Change infrastructure master) Two instances with the following summary information will be listed. Type - Success Principal - Everyone Access - (blank) Inherited from - (CN of domain)

Fix: F-27820r475714_fix

Configure the audit settings for Infrastructure object to include the following. Type - Fail Principal - Everyone Access - Full Control Inherited from - None 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 Principal - Everyone Access - Special Inherited from - None (Access - Special = Permissions: Write all properties, All extended rights, Change infrastructure master) Two instances with the following summary information will be listed. Type - Success Principal - Everyone Access - (blank) Inherited from - (CN of domain)

b

The Active Directory Domain Controllers Organizational Unit (OU) object must be configured with proper audit settings.

AU-12 - Medium - CCI-000172 - V-226131 - SV-226131r794491_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000210-DC

Vuln IDs

V-226131
V-39328

Rule IDs

SV-226131r794491_rule
SV-51172

When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the Domain Controller OU object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. Satisifes: SRG-OS-000471-GPOS-00215

Checks: C-27833r475716_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 Principal - Everyone Access - Full Control Inherited from - None Applies to - This object and all descendant 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 Principal - Everyone Access - Special Inherited from - None Applies to - This object only (Access - Special = Permissions: all create, delete and modify permissions) Type - Success Principal - Everyone Access - Write all properties Inherited from - None Applies to - This object and all descendant objects Two instances with the following summary information will be listed. Type - Success Principal - Everyone Access - (blank) Inherited from - (CN of domain) Applies to - Descendant Organizational Unit objects

Fix: F-27821r475717_fix

Configure the audit settings for Domain Controllers OU object to include the following. Type - Fail Principal - Everyone Access - Full Control Inherited from - None 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 Principal - Everyone Access - Special Inherited from - None Applies to - This object only (Access - Special = Permissions: all create, delete and modify permissions) Type - Success Principal - Everyone Access - Write all properties Inherited from - None Applies to - This object and all descendant objects Two instances with the following summary information will be listed. Type - Success Principal - Everyone Access - (blank) Inherited from - (CN of domain) Applies to - Descendant Organizational Unit objects

b

The Active Directory AdminSDHolder object must be configured with proper audit settings.

AU-12 - Medium - CCI-000172 - V-226132 - SV-226132r794492_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000211-DC

Vuln IDs

V-226132
V-39329

Rule IDs

SV-226132r794492_rule
SV-51173

When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the AdminSDHolder object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. Satisfies: SRG-OS-000471-GPOS-00215

Checks: C-27834r475719_chk

Verify the auditing configuration for the AdminSDHolder 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 System under the domain being reviewed in the left pane. Right click the AdminSDHolder 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 AdminSDHolder object are not at least as inclusive as those below, this is a finding. Type - Fail Principal - Everyone Access - Full Control Inherited from - None Applies 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. Type - Success Principal - Everyone Access - Special Inherited from - None Applies to - This object only (Access - Special = Write all properties, Modify permissions, Modify owner) Two instances with the following summary information will be listed. Type - Success Principal - Everyone Access - (blank) Inherited from - (CN of domain) Applies to - Descendant Organizational Unit objects

Fix: F-27822r475720_fix

Configure the audit settings for AdminSDHolder object to include the following. Type - Fail Principal - Everyone Access - Full Control Inherited from - None Applies 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. Type - Success Principal - Everyone Access - Special Inherited from - None Applies to - This object only (Access - Special = Write all properties, Modify permissions, Modify owner) Two instances with the following summary information will be listed. Type - Success Principal - Everyone Access - (blank) Inherited from - (CN of domain) Applies to - Descendant Organizational Unit objects

b

The Active Directory RID Manager$ object must be configured with proper audit settings.

AU-12 - Medium - CCI-000172 - V-226133 - SV-226133r794493_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN12-AU-000212-DC

Vuln IDs

V-226133
V-39330

Rule IDs

SV-226133r794493_rule
SV-51174

When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the RID Manager$ object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. Satisfies: SRG-OS-000471-GPOS-00215

Checks: C-27835r475722_chk

Verify the auditing configuration for the RID Manager$ 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 System under the domain being reviewed in the left pane. Right-click the RID Manager$ 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 RID Manager$ object are not at least as inclusive as those below, this is a finding. Type - Fail Principal - Everyone Access - Full Control Inherited from - None 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 Principal - Everyone Access - Special Inherited from - None (Access - Special = Write all properties, All extended rights, Change RID master) Two instances with the following summary information will be listed. Type - Success Principal - Everyone Access - (blank) Inherited from - (CN of domain)

Fix: F-27823r475723_fix

Configure the audit settings for RID Manager$ object to include the following. Type - Fail Principal - Everyone Access - Full Control Inherited from - None 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 Principal - Everyone Access - Special Inherited from - None (Access - Special = Write all properties, All extended rights, Change RID master) Two instances with the following summary information will be listed. Type - Success Principal - Everyone Access - (blank) Inherited from - (CN of domain)

b

Event Viewer must be protected from unauthorized modification and deletion.

AU-9 - Medium - CCI-001494 - V-226134 - SV-226134r794458_rule

RMF Control

AU-9

Severity

M

CCI

CCI-001494

Version

WN12-AU-000213

Vuln IDs

V-226134
V-57721

Rule IDs

SV-226134r794458_rule
SV-72135

Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information. Operating systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order to make access decisions regarding the modification or deletion of audit tools.

Checks: C-27836r475725_chk

Verify the permissions on Event Viewer only allow TrustedInstaller permissions to change or modify. If any groups or accounts other than TrustedInstaller have Full control or Modify, this is a finding. Navigate to "%SystemRoot%\SYSTEM32". View the permissions on "Eventvwr.exe". The default permissions below satisfy this requirement. TrustedInstaller - Full Control Administrators, SYSTEM, Users, ALL APPLICATION PACKAGES - Read & Execute

Fix: F-27824r475726_fix

Ensure only TrustedInstaller has permissions to change or modify Event Viewer ("%SystemRoot%\SYSTEM32\Eventvwr.exe). The default permissions below satisfy this requirement. TrustedInstaller - Full Control Administrators, SYSTEM, Users, ALL APPLICATION PACKAGES - Read & Execute

b

The Mapper I/O network protocol (LLTDIO) driver must be disabled.

CM-7 - Medium - CCI-000381 - V-226135 - SV-226135r794411_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-CC-000001

Vuln IDs

V-226135
V-15696

Rule IDs

SV-226135r794411_rule
SV-53072

The Mapper I/O network protocol (LLTDIO) driver allows the discovery of the connected network and allows various options to be enabled. Disabling this helps protect the system from potentially discovering and connecting to unauthorized devices.

Checks: C-27837r475728_chk

If the following registry values do not exist or are not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \Software\Policies\Microsoft\Windows\LLTD\ Value Name: AllowLLTDIOOndomain Value Name: AllowLLTDIOOnPublicNet Value Name: EnableLLTDIO Value Name: ProhibitLLTDIOOnPrivateNet Type: REG_DWORD Value: 0

Fix: F-27825r475729_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Network -> Link-Layer Topology Discovery -> "Turn on Mapper I/O (LLTDIO) driver" to "Disabled".

b

The Responder network protocol driver must be disabled.

CM-7 - Medium - CCI-000381 - V-226136 - SV-226136r794412_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-CC-000002

Vuln IDs

V-226136
V-15697

Rule IDs

SV-226136r794412_rule
SV-53081

The Responder network protocol driver allows a computer to be discovered and located on a network. Disabling this helps protect the system from potentially being discovered and connected to by unauthorized devices.

Checks: C-27838r475731_chk

If the following registry values do not exist or are not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \Software\Policies\Microsoft\Windows\LLTD\ Value Name: AllowRspndrOndomain Value Name: AllowRspndrOnPublicNet Value Name: EnableRspndr Value Name: ProhibitRspndrOnPrivateNet Type: REG_DWORD Value: 0

Fix: F-27826r475732_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Network -> Link-Layer Topology Discovery -> "Turn on Responder (RSPNDR) driver" to "Disabled".

b

Windows Peer-to-Peer networking services must be turned off.

CM-7 - Medium - CCI-000381 - V-226137 - SV-226137r794413_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-CC-000003

Vuln IDs

V-226137
V-15666

Rule IDs

SV-226137r794413_rule
SV-53012

Peer-to-Peer applications can allow unauthorized access to a system and exposure of sensitive data. This setting will turn off the Microsoft Peer-to-Peer Networking Service.

Checks: C-27839r475734_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\Peernet\ Value Name: Disabled Type: REG_DWORD Value: 1

Fix: F-27827r475735_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Network -> Microsoft Peer-to-Peer Networking Services -> "Turn off Microsoft Peer-to-Peer Networking Services" to "Enabled".

b

Network Bridges must be prohibited in Windows.

CM-7 - Medium - CCI-000381 - V-226138 - SV-226138r794414_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-CC-000004

Vuln IDs

V-226138
V-15667

Rule IDs

SV-226138r794414_rule
SV-53014

A Network Bridge can connect two or more network segments, allowing unauthorized access or exposure of sensitive data. This setting prevents a Network Bridge from being installed and configured.

Checks: C-27840r475737_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\Windows\Network Connections\ Value Name: NC_AllowNetBridge_NLA Type: REG_DWORD Value: 0

Fix: F-27828r475738_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Network -> Network Connections -> "Prohibit installation and configuration of Network Bridge on your DNS domain network" to "Enabled".

a

Domain users must be required to elevate when setting a networks location.

SC-3 - Low - CCI-001084 - V-226139 - SV-226139r794452_rule

RMF Control

SC-3

Severity

L

CCI

Version

WN12-CC-000005

Vuln IDs

V-226139
V-21960

Rule IDs

SV-226139r794452_rule
SV-53182

Selecting an incorrect network location may allow greater exposure of a system. Elevation is required by default on nondomain systems to change network location. This setting configures elevation to also be required on domain-joined systems.

Checks: C-27841r475740_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\Windows\Network Connections\ Value Name: NC_StdDomainUserSetLocation Type: REG_DWORD Value: 1

Fix: F-27829r475741_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Network -> Network Connections -> "Require domain users to elevate when setting a network's location" to "Enabled".

a

All Direct Access traffic must be routed through the internal network.

CM-6 - Low - CCI-000366 - V-226140 - SV-226140r794494_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN12-CC-000006

Vuln IDs

V-226140
V-21961

Rule IDs

SV-226140r794494_rule
SV-53183

Routing all Direct Access traffic through the internal network allows monitoring and prevents split tunneling.

Checks: C-27842r475743_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\Windows\TCPIP\v6Transition\ Value Name: Force_Tunneling Type: REG_SZ Value: Enabled

Fix: F-27830r475744_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Network -> Network Connections -> "Route all traffic through the internal network" to "Enabled: Enabled State".

a

IP stateless autoconfiguration limits state must be enabled.

CM-6 - Low - CCI-000366 - V-226145 - SV-226145r794495_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN12-CC-000011

Vuln IDs

V-226145
V-36673

Rule IDs

SV-226145r794495_rule
SV-51605

IP stateless autoconfiguration could configure routes that circumvent preferred routes if not limited.

Checks: C-27847r475758_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: \System\CurrentControlSet\Services\Tcpip\Parameters\ Value Name: EnableIPAutoConfigurationLimits Type: REG_DWORD Value: 1

Fix: F-27835r475759_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Network -> TCPIP Settings -> Parameters -> "Set IP Stateless Autoconfiguration Limits State" to "Enabled".

b

The configuration of wireless devices using Windows Connect Now must be disabled.

CM-7 - Medium - CCI-000381 - V-226146 - SV-226146r794417_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-CC-000012

Vuln IDs

V-226146
V-15698

Rule IDs

SV-226146r794417_rule
SV-53085

Windows Connect Now allows the discovery and configuration of devices over wireless. Wireless devices must be managed. If a rogue device is connected to a system, there is potential for sensitive information to be compromised.

Checks: C-27848r475761_chk

If the following registry values do not exist or are not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \Software\Policies\Microsoft\Windows\WCN\Registrars\ Value Name: DisableFlashConfigRegistrar Value Name: DisableInBand802DOT11Registrar Value Name: DisableUPnPRegistrar Value Name: DisableWPDRegistrar Value Name: EnableRegistrars Type: REG_DWORD Value: 0

Fix: F-27836r475762_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Network -> Windows Connect Now -> "Configuration of wireless settings using Windows Connect Now" to "Disabled".

b

The Windows Connect Now wizards must be disabled.

CM-7 - Medium - CCI-000381 - V-226147 - SV-226147r794418_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-CC-000013

Vuln IDs

V-226147
V-15699

Rule IDs

SV-226147r794418_rule
SV-53089

Windows Connect Now provides wizards for tasks such as "Set up a wireless router or access point" and must not be available to users. Functions such as these may allow unauthorized connections to a system and the potential for sensitive information to be compromised.

Checks: C-27849r475764_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\Windows\WCN\UI\ Value Name: DisableWcnUi Type: REG_DWORD Value: 1

Fix: F-27837r475765_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Network -> Windows Connect Now -> "Prohibit access of the Windows Connect Now wizards" to "Enabled".

a

Windows Update must be prevented from searching for point and print drivers.

CM-11 - Low - CCI-001812 - V-226148 - SV-226148r794467_rule

RMF Control

CM-11

Severity

L

CCI

Version

WN12-CC-000016

Vuln IDs

V-226148
V-21963

Rule IDs

SV-226148r794467_rule
SV-53184

Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. This setting will prevent Windows from searching Windows Update for point and print drivers. Only the local driver store and server driver cache will be searched.

Checks: C-27850r475767_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\Windows NT\Printers\ Value Name: DoNotInstallCompatibleDriverFromWindowsUpdate Type: REG_DWORD Value: 1

Fix: F-27838r475768_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Printers -> "Extend Point and Print connection to search Windows Update" to "Disabled".

a

Optional component installation and component repair must be prevented from using Windows Update.

CM-11 - Low - CCI-001812 - V-226149 - SV-226149r794468_rule

RMF Control

CM-11

Severity

L

CCI

Version

WN12-CC-000018

Vuln IDs

V-226149
V-36677

Rule IDs

SV-226149r794468_rule
SV-51606

Uncontrolled system updates can introduce issues to a system. Obtaining update components from an outside source may also potentially provide sensitive information outside of the enterprise. Optional component installation or repair must be obtained from an internal source.

Checks: C-27851r475770_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\Microsoft\Windows\CurrentVersion\Policies\Servicing\ Value Name: UseWindowsUpdate Type: REG_DWORD Value: 2

Fix: F-27839r475771_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> "Specify settings for optional component installation and component repair" to "Enabled" and with "Never attempt to download payload from Windows Update" selected.

b

Remote access to the Plug and Play interface must be disabled for device installation.

CM-7 - Medium - CCI-000381 - V-226150 - SV-226150r794419_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-CC-000019

Vuln IDs

V-226150
V-15700

Rule IDs

SV-226150r794419_rule
SV-53094

Remote access to the Plug and Play interface could potentially allow connections by unauthorized devices. This setting configures remote access to the Plug and Play interface and must be disabled.

Checks: C-27852r475773_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\Windows\DeviceInstall\Settings\ Value Name: AllowRemoteRPC Type: REG_DWORD Value: 0

Fix: F-27840r475774_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Device Installation -> "Allow remote access to the Plug and Play interface" to "Disabled".

a

An Error Report must not be sent when a generic device driver is installed.

CM-7 - Low - CCI-000381 - V-226151 - SV-226151r794420_rule

RMF Control

CM-7

Severity

L

CCI

Version

WN12-CC-000020

Vuln IDs

V-226151
V-15702

Rule IDs

SV-226151r794420_rule
SV-53105

Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. This setting prevents an error report from being sent when a generic device driver is installed.

Checks: C-27853r475776_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\Windows\DeviceInstall\Settings\ Value Name: DisableSendGenericDriverNotFoundToWER Type: REG_DWORD Value: 1

Fix: F-27841r475777_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Device Installation -> "Do not send a Windows error report when a generic driver is installed on a device" to "Enabled".

a

A system restore point must be created when a new device driver is installed.

CM-6 - Low - CCI-000366 - V-226152 - SV-226152r794496_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN12-CC-000021

Vuln IDs

V-226152
V-15701

Rule IDs

SV-226152r794496_rule
SV-53099

A system restore point allows a rollback if an issue is encountered when a new device driver is installed.

Checks: C-27854r475779_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\Windows\DeviceInstall\Settings\ Value Name: DisableSystemRestore Type: REG_DWORD Value: 0

Fix: F-27842r475780_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Device Installation -> "Prevent creation of a system restore point during device activity that would normally prompt creation of a restore point" to "Disabled".

a

Device metadata retrieval from the Internet must be prevented.

CM-7 - Low - CCI-000381 - V-226153 - SV-226153r794421_rule

RMF Control

CM-7

Severity

L

CCI

Version

WN12-CC-000022

Vuln IDs

V-226153
V-21964

Rule IDs

SV-226153r794421_rule
SV-53185

Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. This setting will prevent Windows from retrieving device metadata from the Internet.

Checks: C-27855r475782_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\Windows\Device Metadata\ Value Name: PreventDeviceMetadataFromNetwork Value Type: REG_DWORD Value: 1

Fix: F-27843r475783_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Device Installation >> "Prevent device metadata retrieval from the Internet" to "Enabled".

a

Windows must be prevented from sending an error report when a device driver requests additional software during installation.

CM-7 - Low - CCI-000381 - V-226154 - SV-226154r794422_rule

RMF Control

CM-7

Severity

L

CCI

Version

WN12-CC-000023

Vuln IDs

V-226154
V-28504

Rule IDs

SV-226154r794422_rule
SV-52962

Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. This setting will prevent Windows from sending an error report to Microsoft when a device driver requests additional software during installation.

Checks: C-27856r475785_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\Windows\DeviceInstall\Settings\ Value Name: DisableSendRequestAdditionalSoftwareToWER Type: REG_DWORD Value: 1

Fix: F-27844r475786_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Device Installation -> "Prevent Windows from sending an error report when a device driver requests additional software during installation" to "Enabled".

a

Device driver searches using Windows Update must be prevented.

CM-11 - Low - CCI-001812 - V-226155 - SV-226155r794469_rule

RMF Control

CM-11

Severity

L

CCI

Version

WN12-CC-000024

Vuln IDs

V-226155
V-21965

Rule IDs

SV-226155r794469_rule
SV-53186

Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. This setting will prevent the system from searching Windows Update for device drivers.

Checks: C-27857r475788_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\Windows\DriverSearching\ Value Name: SearchOrderConfig Type: REG_DWORD Value: 0

Fix: F-27845r475789_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Device Installation -> "Specify search order for device driver source locations" to "Enabled: Do not search Windows Update".

a

Device driver updates must only search managed servers, not Windows Update.

CM-11 - Low - CCI-001812 - V-226156 - SV-226156r794470_rule

RMF Control

CM-11

Severity

L

CCI

Version

WN12-CC-000025

Vuln IDs

V-226156
V-36678

Rule IDs

SV-226156r794470_rule
SV-51607

Uncontrolled system updates can introduce issues to a system. Obtaining update components from an outside source may also potentially provide sensitive information outside of the enterprise. Device driver updates must be obtained from an internal source.

Checks: C-27858r475791_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\Windows\DriverSearching\ Value Name: DriverServerSelection Type: REG_DWORD Value: 1

Fix: F-27846r475792_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Device Installation -> "Specify the search server for device driver updates" to "Enabled" with "Search Managed Server" selected.

a

Users must not be prompted to search Windows Update for device drivers.

CM-11 - Low - CCI-001812 - V-226157 - SV-226157r794471_rule

RMF Control

CM-11

Severity

L

CCI

Version

WN12-CC-000026

Vuln IDs

V-226157
V-15703

Rule IDs

SV-226157r794471_rule
SV-53115

Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. This setting prevents users from being prompted to search Windows Update for device drivers.

Checks: C-27859r475794_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\Windows\DriverSearching\ Value Name: DontPromptForWindowsUpdate Type: REG_DWORD Value: 1

Fix: F-27847r475795_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Driver Installation -> "Turn off Windows Update device driver search prompt" to "Enabled".

b

Early Launch Antimalware, Boot-Start Driver Initialization Policy must be enabled and configured to only Good and Unknown.

CM-6 - Medium - CCI-000366 - V-226158 - SV-226158r794497_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-CC-000027

Vuln IDs

V-226158
V-36679

Rule IDs

SV-226158r794497_rule
SV-51608

Compromised boot drivers can introduce malware prior to some protection mechanisms that load after initialization. The Early Launch Antimalware driver can limit allowed drivers based on classifications determined by the malware protection application. At a minimum, drivers determined to be bad must not be allowed.

Checks: C-27860r475797_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: \System\CurrentControlSet\Policies\EarlyLaunch\ Value Name: DriverLoadPolicy Type: REG_DWORD Value: 1

Fix: F-27848r475798_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Early Launch Antimalware -> "Boot-Start Driver Initialization Policy" to "Enabled" with "Good and Unknown" selected.

b

Group Policy objects must be reprocessed even if they have not changed.

CM-6 - Medium - CCI-000366 - V-226159 - SV-226159r794498_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-CC-000028

Vuln IDs

V-226159
V-4448

Rule IDs

SV-226159r794498_rule
SV-52933

Enabling this setting and then selecting the "Process even if the Group Policy objects have not changed" option ensures that the policies will be reprocessed even if none have been changed. This way, any unauthorized changes are forced to match the domain-based group policy settings again.

Checks: C-27861r475800_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\Windows\Group Policy\{35378EAC-683F-11D2-A89A-00C04FBBCFA2}\ Value Name: NoGPOListChanges Type: REG_DWORD Value: 0

Fix: F-27849r475801_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Group Policy -> "Configure registry policy processing" to "Enabled" and select the option "Process even if the Group Policy objects have not changed".

b

Group Policies must be refreshed in the background if the user is logged on.

CM-6 - Medium - CCI-000366 - V-226160 - SV-226160r794499_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-CC-000029

Vuln IDs

V-226160
V-3469

Rule IDs

SV-226160r794499_rule
SV-52906

If this setting is enabled, then Group Policy settings are not refreshed while a user is currently logged on. This could lead to instances when a user does not have the latest changes to a policy applied and is therefore operating in an insecure context.

Checks: C-27862r475803_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 exists but is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \Software\Microsoft\Windows\CurrentVersion\Policies\system\ Value Name: DisableBkGndGroupPolicy Type: REG_DWORD Value: 0

Fix: F-27850r475804_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Group Policy -> "Turn off background refresh of Group Policy" to "Disabled".

b

Access to the Windows Store must be turned off.

CM-6 - Medium - CCI-000366 - V-226161 - SV-226161r794423_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-CC-000030

Vuln IDs

V-226161
V-36680

Rule IDs

SV-226161r794423_rule
SV-51609

Uncontrolled installation of applications can introduce various issues, including system instability, and allow access to sensitive information. Installation of applications must be controlled by the enterprise. Turning off access to the Windows Store will limit access to publicly available applications.

Checks: C-27863r475806_chk

The Windows Store is not installed by default. If the \Windows\WinStore directory does not exist, this is NA. 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\Windows\Explorer\ Value Name: NoUseStoreOpenWith Type: REG_DWORD Value: 1

Fix: F-27851r475807_fix

If the \Windows\WinStore directory exists, configure the policy value for Computer Configuration >> Administrative Templates >> System >> Internet Communication Management >> Internet Communication settings >> "Turn off access to the Store" to "Enabled". Alternately, uninstall the "Desktop Experience" feature from Windows 2012. This is located under "User Interfaces and Infrastructure" in the "Add Roles and Features Wizard". The \Windows\WinStore directory may need to be manually deleted after this.

b

Downloading print driver packages over HTTP must be prevented.

CM-7 - Medium - CCI-000381 - V-226162 - SV-226162r794424_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-CC-000032

Vuln IDs

V-226162
V-14260

Rule IDs

SV-226162r794424_rule
SV-52998

Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. This setting prevents the computer from downloading print driver packages over HTTP.

Checks: C-27864r475809_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\Windows NT\Printers\ Value Name: DisableWebPnPDownload Type: REG_DWORD Value: 1

Fix: F-27852r475810_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Internet Communication Management -> Internet Communication settings -> "Turn off downloading of print drivers over HTTP" to "Enabled".

a

Event Viewer Events.asp links must be turned off.

CM-7 - Low - CCI-000381 - V-226163 - SV-226163r794425_rule

RMF Control

CM-7

Severity

L

CCI

Version

WN12-CC-000033

Vuln IDs

V-226163
V-15672

Rule IDs

SV-226163r794425_rule
SV-53017

Viewing events is a function of administrators, who must not access the internet with privileged accounts. This setting will disable Events.asp hyperlinks in Event Viewer to prevent links to the internet from within events.

Checks: C-27865r475812_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\EventViewer\ Value Name: MicrosoftEventVwrDisableLinks Type: REG_DWORD Value: 1

Fix: F-27853r475813_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Internet Communication Management -> Internet Communication settings -> "Turn off Event Viewer "Events.asp" links" to "Enabled".

a

Errors in handwriting recognition on tablet PCs must not be reported to Microsoft.

CM-7 - Low - CCI-000381 - V-226164 - SV-226164r794426_rule

RMF Control

CM-7

Severity

L

CCI

Version

WN12-CC-000035

Vuln IDs

V-226164
V-15704

Rule IDs

SV-226164r794426_rule
SV-53116

Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. This setting prevents errors in handwriting recognition on tablet PCs from being reported to Microsoft.

Checks: C-27866r475815_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\Windows\HandwritingErrorReports\ Value Name: PreventHandwritingErrorReports Type: REG_DWORD Value: 1

Fix: F-27854r475816_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Internet Communication Management -> Internet Communication settings -> "Turn off handwriting recognition error reporting" to "Enabled".

b

The Internet File Association service must be turned off.

CM-7 - Medium - CCI-000381 - V-226165 - SV-226165r794427_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-CC-000038

Vuln IDs

V-226165
V-15674

Rule IDs

SV-226165r794427_rule
SV-53021

Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. This setting prevents unhandled file associations from using the Microsoft Web service to find an application.

Checks: C-27867r475818_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\Microsoft\Windows\CurrentVersion\Policies\Explorer\ Value Name: NoInternetOpenWith Type: REG_DWORD Value: 1

Fix: F-27855r475819_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Internet Communication Management -> Internet Communication settings -> "Turn off Internet File Association service" to "Enabled".

b

Printing over HTTP must be prevented.

CM-7 - Medium - CCI-000381 - V-226166 - SV-226166r794428_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-CC-000039

Vuln IDs

V-226166
V-14259

Rule IDs

SV-226166r794428_rule
SV-52997

Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. This setting prevents the client computer from printing over HTTP, which allows the computer to print to printers on the intranet as well as the Internet.

Checks: C-27868r475821_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\Windows NT\Printers\ Value Name: DisableHTTPPrinting Type: REG_DWORD Value: 1

Fix: F-27856r475822_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Internet Communication Management -> Internet Communication settings -> "Turn off printing over HTTP" to "Enabled".

b

The Windows Customer Experience Improvement Program must be disabled.

CM-7 - Medium - CCI-000381 - V-226167 - SV-226167r794429_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-CC-000045

Vuln IDs

V-226167
V-16020

Rule IDs

SV-226167r794429_rule
SV-53143

Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. This setting ensures the Windows Customer Experience Improvement Program is disabled so information is not passed to the vendor.

Checks: C-27869r475824_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\SQMClient\Windows\ Value Name: CEIPEnable Type: REG_DWORD Value: 0

Fix: F-27857r475825_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Internet Communication Management -> Internet Communication Settings -> "Turn off Windows Customer Experience Improvement Program" to "Enabled".

b

Windows must be prevented from using Windows Update to search for drivers.

CM-11 - Medium - CCI-001812 - V-226168 - SV-226168r794472_rule

RMF Control

CM-11

Severity

M

CCI

Version

WN12-CC-000047

Vuln IDs

V-226168
V-14261

Rule IDs

SV-226168r794472_rule
SV-53000

Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. This setting prevents Windows from searching Windows Update for device drivers when no local drivers for a device are present.

Checks: C-27870r475827_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\Windows\DriverSearching\ Value Name: DontSearchWindowsUpdate Type: REG_DWORD Value: 1

Fix: F-27858r475828_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Internet Communication Management -> Internet Communication settings -> "Turn off Windows Update device driver searching" to "Enabled".

b

Copying of user input methods to the system account for sign-in must be prevented.

CM-7 - Medium - CCI-000381 - V-226169 - SV-226169r794430_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-CC-000048

Vuln IDs

V-226169
V-36681

Rule IDs

SV-226169r794430_rule
SV-51610

Allowing different input methods for sign-in could open different avenues of attack. User input methods must be restricted to those enabled for the system account at sign-in.

Checks: C-27871r475830_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\Control Panel\International\ Value Name: BlockUserInputMethodsForSignIn Type: REG_DWORD Value: 1

Fix: F-27859r475831_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Locale Services -> "Disallow copying of user input methods to the system account for sign-in" to "Enabled".

b

Local users on domain-joined computers must not be enumerated.

CM-7 - Medium - CCI-000381 - V-226170 - SV-226170r794431_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-CC-000051

Vuln IDs

V-226170
V-36684

Rule IDs

SV-226170r794431_rule
SV-51611

The username is one part of logon credentials that could be used to gain access to a system. Preventing the enumeration of users limits this information to authorized personnel.

Checks: C-27872r475833_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\Windows\System\ Value Name: EnumerateLocalUsers Type: REG_DWORD Value: 0

Fix: F-27860r475834_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Logon -> "Enumerate local users on domain-joined computers" to "Disabled".

b

App notifications on the lock screen must be turned off.

CM-7 - Medium - CCI-000381 - V-226171 - SV-226171r794432_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-CC-000052

Vuln IDs

V-226171
V-36687

Rule IDs

SV-226171r794432_rule
SV-51612

App notifications that are displayed on the lock screen could display sensitive information to unauthorized personnel. Turning off this feature will limit access to the information to a logged on user.

Checks: C-27873r475836_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\Windows\System\ Value Name: DisableLockScreenAppNotifications Type: REG_DWORD Value: 1

Fix: F-27861r475837_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Logon -> "Turn off app notifications on the lock screen" to "Enabled".

b

Users must be prompted to authenticate on resume from sleep (on battery).

IA-11 - Medium - CCI-002038 - V-226172 - SV-226172r794480_rule

RMF Control

IA-11

Severity

M

CCI

Version

WN12-CC-000054

Vuln IDs

V-226172
V-15705

Rule IDs

SV-226172r794480_rule
SV-53131

Authentication must always be required when accessing a system. This setting ensures the user is prompted for a password on resume from sleep (on battery).

Checks: C-27874r475839_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\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51\ Value Name: DCSettingIndex Type: REG_DWORD Value: 1

Fix: F-27862r475840_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Power Management -> Sleep Settings -> "Require a password when a computer wakes (on battery)" to "Enabled".

b

The user must be prompted to authenticate on resume from sleep (plugged in).

IA-11 - Medium - CCI-002038 - V-226173 - SV-226173r794481_rule

RMF Control

IA-11

Severity

M

CCI

Version

WN12-CC-000055

Vuln IDs

V-226173
V-15706

Rule IDs

SV-226173r794481_rule
SV-53132

Authentication must always be required when accessing a system. This setting ensures the user is prompted for a password on resume from sleep (plugged in).

Checks: C-27875r475842_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\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51\ Value Name: ACSettingIndex Type: REG_DWORD Value: 1

Fix: F-27863r475843_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Power Management -> Sleep Settings -> "Require a password when a computer wakes (plugged in)" to "Enabled".

b

The system must be configured to prevent unsolicited remote assistance offers.

SC-4 - Medium - CCI-001090 - V-226174 - SV-226174r794454_rule

RMF Control

SC-4

Severity

M

CCI

Version

WN12-CC-000058

Vuln IDs

V-226174
V-3470

Rule IDs

SV-226174r794454_rule
SV-52917

Remote assistance allows another user to view or take control of the local session of a user. Unsolicited remote assistance is help that is offered by the remote user. This may allow unauthorized parties access to the resources on the computer.

Checks: C-27876r475845_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\Windows NT\Terminal Services\ Value Name: fAllowUnsolicited Type: REG_DWORD Value: 0

Fix: F-27864r475846_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Remote Assistance -> "Configure Offer Remote Assistance" to "Disabled".

c

Solicited Remote Assistance must not be allowed.

SC-4 - High - CCI-001090 - V-226175 - SV-226175r794455_rule

RMF Control

SC-4

Severity

H

CCI

Version

WN12-CC-000059

Vuln IDs

V-226175
V-3343

Rule IDs

SV-226175r794455_rule
SV-52885

Remote assistance allows another user to view or take control of the local session of a user. Solicited assistance is help that is specifically requested by the local user. This may allow unauthorized parties access to the resources on the computer.

Checks: C-27877r475848_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\Windows NT\Terminal Services\ Value Name: fAllowToGetHelp Type: REG_DWORD Value: 0

Fix: F-27865r475849_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Remote Assistance -> "Configure Solicited Remote Assistance" to "Disabled".

a

Remote Assistance log files must be generated.

CM-6 - Low - CCI-000366 - V-226176 - SV-226176r794500_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN12-CC-000062

Vuln IDs

V-226176
V-15707

Rule IDs

SV-226176r794500_rule
SV-53133

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. This setting will turn on session logging for Remote Assistance connections.

Checks: C-27878r475851_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\Windows NT\Terminal Services\ Value Name: LoggingEnabled Type: REG_DWORD Value: 1

Fix: F-27866r475852_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Remote Assistance -> "Turn on session logging" to "Enabled".

a

The detection of compatibility issues for applications and drivers must be turned off.

CM-7 - Low - CCI-000381 - V-226177 - SV-226177r794433_rule

RMF Control

CM-7

Severity

L

CCI

Version

WN12-CC-000065

Vuln IDs

V-226177
V-36696

Rule IDs

SV-226177r794433_rule
SV-51737

Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this feature will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system.

Checks: C-27879r475854_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\Windows\AppCompat\ Value Name: DisablePcaUI Type: REG_DWORD Value: 0

Fix: F-27867r475855_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Troubleshooting and Diagnostics -> Application Compatibility Diagnostics -> "Detect compatibility issues for applications and drivers" to "Disabled".

a

Microsoft Support Diagnostic Tool (MSDT) interactive communication with Microsoft must be prevented.

CM-7 - Low - CCI-000381 - V-226178 - SV-226178r794434_rule

RMF Control

CM-7

Severity

L

CCI

Version

WN12-CC-000066

Vuln IDs

V-226178
V-21967

Rule IDs

SV-226178r794434_rule
SV-53187

Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. This setting prevents the MSDT from communicating with and sending collected data to Microsoft, the default support provider.

Checks: C-27880r475857_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\Windows\ScriptedDiagnosticsProvider\Policy\ Value Name: DisableQueryRemoteServer Type: REG_DWORD Value: 0

Fix: F-27868r475858_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Troubleshooting and Diagnostics -> Microsoft Support Diagnostic Tool -> "Microsoft Support Diagnostic Tool: Turn on MSDT interactive communication with support provider" to "Disabled".

a

Access to Windows Online Troubleshooting Service (WOTS) must be prevented.

CM-7 - Low - CCI-000381 - V-226179 - SV-226179r794435_rule

RMF Control

CM-7

Severity

L

CCI

Version

WN12-CC-000067

Vuln IDs

V-226179
V-21969

Rule IDs

SV-226179r794435_rule
SV-53188

Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. This setting prevents users from searching troubleshooting content on Microsoft servers. Only local content will be available.

Checks: C-27881r475860_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\Windows\ScriptedDiagnosticsProvider\Policy\ Value Name: EnableQueryRemoteServer Type: REG_DWORD Value: 0

Fix: F-27869r475861_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Troubleshooting and Diagnostics -> Scripted Diagnostics -> "Troubleshooting: Allow users to access online troubleshooting content on Microsoft servers from the Troubleshooting Control Panel (via the Windows Online Troubleshooting Service - WOTS)" to "Disabled".

a

Responsiveness events must be prevented from being aggregated and sent to Microsoft.

CM-7 - Low - CCI-000381 - V-226180 - SV-226180r794436_rule

RMF Control

CM-7

Severity

L

CCI

Version

WN12-CC-000068

Vuln IDs

V-226180
V-21970

Rule IDs

SV-226180r794436_rule
SV-53128

Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. This setting prevents responsiveness events from being aggregated and sent to Microsoft.

Checks: C-27882r475863_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\Windows\WDI\{9c5a40da-b965-4fc3-8781-88dd50a6299d}\ Value Name: ScenarioExecutionEnabled Type: REG_DWORD Value: 0

Fix: F-27870r475864_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Troubleshooting and Diagnostics -> Windows Performance PerfTrack -> "Enable/Disable PerfTrack" to "Disabled".

a

The time service must synchronize with an appropriate DoD time source.

AU-8 - Low - CCI-001891 - V-226181 - SV-226181r794507_rule

RMF Control

AU-8

Severity

L

CCI

CCI-001891

Version

WN12-CC-000069

Vuln IDs

V-226181
V-3472

Rule IDs

SV-226181r794507_rule
SV-52919

The Windows Time Service controls time synchronization settings. Time synchronization is essential for authentication and auditing purposes. If the Windows Time Service is used, it must synchronize with a secure, authorized time source. Domain-joined systems are automatically configured to synchronize with domain controllers. If an NTP server is configured, it must synchronize with a secure, authorized time source.

Checks: C-27883r475866_chk

Open "Windows PowerShell" or an elevated "Command Prompt" (run as administrator). Enter "W32tm /query /configuration". Domain-joined systems are automatically configured with a "Type" of "NT5DS" to synchronize with domain controllers and would not be a finding. If systems are configured with a "Type" of "NTP", including standalone systems and the forest root domain controller with the PDC Emulator role, and do not have a DoD time server defined for "NTPServer", this is a finding. (See V-8557 in the Active Directory Forest STIG for the time source requirement of the forest root domain PDC emulator.) If an alternate time synchronization tool is used and is not enabled or not configured to synchronize with a DoD time source, this is a finding. The US Naval Observatory operates stratum 1 time servers, identified at http://tycho.usno.navy.mil/ntp.html. Time synchronization will occur through a hierarchy of time servers down to the local level. Clients and lower-level servers will synchronize with an authorized time server in the hierarchy.

Fix: F-27871r475867_fix

If the system needs to be configured to an NTP server, configure the system to point to an authorized time server by setting the policy value for Computer Configuration >> Administrative Templates >> System >> Windows Time Service >> Time Providers >> "Configure Windows NTP Client" to "Enabled", and configure the "NtpServer" field to point to an authorized time server. The US Naval Observatory operates stratum 1 time servers, identified at http://tycho.usno.navy.mil/ntp.html. Time synchronization will occur through a hierarchy of time servers down to the local level. Clients and lower-level servers will synchronize with an authorized time server in the hierarchy.

a

Trusted app installation must be enabled to allow for signed enterprise line of business apps.

CM-6 - Low - CCI-000366 - V-226182 - SV-226182r794437_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN12-CC-000070

Vuln IDs

V-226182
V-36697

Rule IDs

SV-226182r794437_rule
SV-51738

Enabling trusted app installation allows for enterprise line of business Windows 8 type apps. A trusted app package is one that is signed with a certificate chain that can be successfully validated in the enterprise. Configuring this ensures enterprise line of business apps are accessible.

Checks: C-27884r475869_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\Windows\Appx\ Value Name: AllowAllTrustedApps Type: REG_DWORD Value: 1

Fix: F-27872r475870_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> App Package Deployment -> "Allow all trusted apps to install" to "Enabled".

a

The Application Compatibility Program Inventory must be prevented from collecting data and sending the information to Microsoft.

CM-7 - Low - CCI-000381 - V-226183 - SV-226183r794438_rule

RMF Control

CM-7

Severity

L

CCI

Version

WN12-CC-000071

Vuln IDs

V-226183
V-21971

Rule IDs

SV-226183r794438_rule
SV-53127

Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. This setting will prevent the Program Inventory from collecting data about a system and sending the information to Microsoft.

Checks: C-27885r475872_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\Windows\AppCompat\ Value Name: DisableInventory Type: REG_DWORD Value: 1

Fix: F-27873r475873_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Application Compatibility -> "Turn off Inventory Collector" to "Enabled".

c

Autoplay must be turned off for non-volume devices.

CM-7 - High - CCI-001764 - V-226184 - SV-226184r794477_rule

RMF Control

CM-7

Severity

H

CCI

CCI-001764

Version

WN12-CC-000072

Vuln IDs

V-226184
V-21973

Rule IDs

SV-226184r794477_rule
SV-53126

Allowing Autoplay to execute may introduce malicious code to a system. Autoplay begins reading from a drive as soon as media is inserted into the drive. As a result, the setup file of programs or music on audio media may start. This setting will disable Autoplay for non-volume devices (such as Media Transfer Protocol (MTP) devices).

Checks: C-27886r475875_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\Windows\Explorer\ Value Name: NoAutoplayfornonVolume Type: REG_DWORD Value: 1

Fix: F-27874r475876_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> AutoPlay Policies -> "Disallow Autoplay for non-volume devices" to "Enabled".

c

The default Autorun behavior must be configured to prevent Autorun commands.

CM-7 - High - CCI-001764 - V-226185 - SV-226185r794478_rule

RMF Control

CM-7

Severity

H

CCI

CCI-001764

Version

WN12-CC-000073

Vuln IDs

V-226185
V-22692

Rule IDs

SV-226185r794478_rule
SV-53124

Allowing Autorun commands to execute may introduce malicious code to a system. Configuring this setting prevents Autorun commands from executing.

Checks: C-27887r475878_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\Microsoft\Windows\CurrentVersion\Policies\Explorer\ Value Name: NoAutorun Type: REG_DWORD Value: 1

Fix: F-27875r475879_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> AutoPlay Policies -> "Set the default behavior for AutoRun" to "Enabled:Do not execute any autorun commands".

c

Autoplay must be disabled for all drives.

CM-7 - High - CCI-001764 - V-226186 - SV-226186r794479_rule

RMF Control

CM-7

Severity

H

CCI

CCI-001764

Version

WN12-CC-000074

Vuln IDs

V-226186
V-2374

Rule IDs

SV-226186r794479_rule
SV-52879

Allowing Autoplay to execute may introduce malicious code to a system. Autoplay begins reading from a drive as soon media is inserted into the drive. As a result, the setup file of programs or music on audio media may start. By default, Autoplay is disabled on removable drives, such as the floppy disk drive (but not the CD-ROM drive) and on network drives. Enabling this policy disables Autoplay on all drives.

Checks: C-27888r475881_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\Microsoft\Windows\CurrentVersion\policies\Explorer\ Value Name: NoDriveTypeAutoRun Type: REG_DWORD Value: 0x000000ff (255)

Fix: F-27876r475882_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> AutoPlay Policies -> "Turn off AutoPlay" to "Enabled:All Drives".

b

The use of biometrics must be disabled.

CM-7 - Medium - CCI-000381 - V-226187 - SV-226187r794439_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-CC-000075

Vuln IDs

V-226187
V-36698

Rule IDs

SV-226187r794439_rule
SV-51739

Allowing biometrics may bypass required authentication methods. Biometrics may only be used as an additional authentication factor where an enhanced strength of identity credential is necessary or desirable. Additional factors must be met per DoD policy.

Checks: C-27889r475884_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\Biometrics\ Value Name: Enabled Type: REG_DWORD Value: 0

Fix: F-27877r475885_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Biometrics -> "Allow the use of biometrics" to "Disabled".

b

The password reveal button must not be displayed.

IA-6 - Medium - CCI-000206 - V-226188 - SV-226188r794410_rule

RMF Control

IA-6

Severity

M

CCI

CCI-000206

Version

WN12-CC-000076

Vuln IDs

V-226188
V-36700

Rule IDs

SV-226188r794410_rule
SV-51740

Visible passwords may be seen by nearby persons, compromising them. The password reveal button can be used to display an entered password and must not be allowed.

Checks: C-27890r475887_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\Windows\CredUI\ Value Name: DisablePasswordReveal Type: REG_DWORD Value: 1

Fix: F-27878r475888_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Credential User Interface -> "Do not display the password reveal button" to "Enabled".

b

Administrator accounts must not be enumerated during elevation.

SC-3 - Medium - CCI-001084 - V-226189 - SV-226189r794453_rule

RMF Control

SC-3

Severity

M

CCI

Version

WN12-CC-000077

Vuln IDs

V-226189
V-14243

Rule IDs

SV-226189r794453_rule
SV-52955

Enumeration of administrator accounts when elevating can provide part of the logon information to an unauthorized user. This setting configures the system to always require users to enter in a username and password to elevate a running application.

Checks: C-27891r475890_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\Microsoft\Windows\CurrentVersion\Policies\CredUI\ Value Name: EnumerateAdministrators Type: REG_DWORD Value: 0x00000000 (0)

Fix: F-27879r475891_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Credential User Interface >> "Enumerate administrator accounts on elevation" to "Disabled".

b

The Application event log size must be configured to 32768 KB or greater.

AU-4 - Medium - CCI-001849 - V-226190 - SV-226190r794463_rule

RMF Control

AU-4

Severity

M

CCI

Version

WN12-CC-000084

Vuln IDs

V-226190
V-26579

Rule IDs

SV-226190r794463_rule
SV-52966

Inadequate log size will cause the log to fill up quickly. This may prevent audit events from being recorded properly and require frequent attention by administrative personnel.

Checks: C-27892r475893_chk

If the system is configured to write events directly to an audit server, this is NA. 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\Windows\EventLog\Application\ Value Name: MaxSize Type: REG_DWORD Value: 0x00008000 (32768) (or greater)

Fix: F-27880r475894_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Event Log Service >> Application >> "Specify the maximum log file size (KB)" to "Enabled" with a "Maximum Log Size (KB)" of "32768" or greater.

b

The Security event log size must be configured to 196608 KB or greater.

AU-4 - Medium - CCI-001849 - V-226191 - SV-226191r794464_rule

RMF Control

AU-4

Severity

M

CCI

Version

WN12-CC-000085

Vuln IDs

V-226191
V-26580

Rule IDs

SV-226191r794464_rule
SV-52965

Inadequate log size will cause the log to fill up quickly. This may prevent audit events from being recorded properly and require frequent attention by administrative personnel.

Checks: C-27893r475896_chk

If the system is configured to write events directly to an audit server, this is NA. 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\Windows\EventLog\Security\ Value Name: MaxSize Type: REG_DWORD Value: 0x00030000 (196608) (or greater)

Fix: F-27881r475897_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Event Log Service >> Security >> "Specify the maximum log file size (KB)" to "Enabled" with a "Maximum Log Size (KB)" of "196608" or greater.

b

The Setup event log size must be configured to 32768 KB or greater.

AU-4 - Medium - CCI-001849 - V-226192 - SV-226192r794465_rule

RMF Control

AU-4

Severity

M

CCI

Version

WN12-CC-000086

Vuln IDs

V-226192
V-26581

Rule IDs

SV-226192r794465_rule
SV-52964

Inadequate log size will cause the log to fill up quickly. This may prevent audit events from being recorded properly and require frequent attention by administrative personnel.

Checks: C-27894r475899_chk

If the system is configured to write events directly to an audit server, this is NA. 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\Windows\EventLog\Setup\ Value Name: MaxSize Type: REG_DWORD Value: 0x00008000 (32768) (or greater)

Fix: F-27882r475900_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Event Log Service >> Setup >> "Specify the maximum log file size (KB)" to "Enabled" with a "Maximum Log Size (KB)" of "32768" or greater.

b

The System event log size must be configured to 32768 KB or greater.

AU-4 - Medium - CCI-001849 - V-226193 - SV-226193r794466_rule

RMF Control

AU-4

Severity

M

CCI

Version

WN12-CC-000087

Vuln IDs

V-226193
V-26582

Rule IDs

SV-226193r794466_rule
SV-52963

Inadequate log size will cause the log to fill up quickly. This may prevent audit events from being recorded properly and require frequent attention by administrative personnel.

Checks: C-27895r475902_chk

If the system is configured to write events directly to an audit server, this is NA. 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\Windows\EventLog\System\ Value Name: MaxSize Type: REG_DWORD Value: 0x00008000 (32768) (or greater)

Fix: F-27883r475903_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Event Log Service >> System >> "Specify the maximum log file size (KB)" to "Enabled" with a "Maximum Log Size (KB)" of "32768" or greater.

b

Windows SmartScreen must be enabled on Windows 2012/2012 R2.

CM-7 - Medium - CCI-000381 - V-226194 - SV-226194r794440_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-CC-000088

Vuln IDs

V-226194
V-36707

Rule IDs

SV-226194r794440_rule
SV-51747

Windows SmartScreen helps protect systems from programs downloaded from the Internet that may be malicious. Warning a user before running downloaded unknown software, at minimum, will help prevent potentially malicious programs from executing.

Checks: C-27896r475905_chk

This is applicable to unclassified systems; for other systems, this is NA. 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\Windows\System\ Value Name: EnableSmartScreen Type: REG_DWORD Value: 0x00000001 (1) (Give user a warning…) Or 0x00000002 (2) (Require approval…)

Fix: F-27884r475906_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> "Configure Windows SmartScreen" to "Enabled" with either "Give user a warning before running downloaded unknown software" or "Require approval from an administrator before running downloaded unknown software" selected. Microsoft has changed this setting several times in the Windows 10 administrative templates, which will affect group policies in a domain if later templates are used. v1607 of Windows 10 and Windows Server 2016 changed the setting to only Enabled or Disabled without additional selections. Enabled is effectively "Give user a warning…". v1703 of Windows 10 or later administrative templates changed the policy name to "Configure Windows Defender SmartScreen", and the selectable options are "Warn" and "Warn and prevent bypass". When either of these are applied to a Windows 2012/2012 R2 system, it will configure the registry equivalent of "Give user a warning…").

b

Explorer Data Execution Prevention must be enabled.

SI-16 - Medium - CCI-002824 - V-226195 - SV-226195r794488_rule

RMF Control

SI-16

Severity

M

CCI

CCI-002824

Version

WN12-CC-000089

Vuln IDs

V-226195
V-21980

Rule IDs

SV-226195r794488_rule
SV-53125

Data Execution Prevention (DEP) provides additional protection by performing checks on memory to help prevent malicious code from running. This setting will prevent Data Execution Prevention from being turned off for File Explorer.

Checks: C-27897r475908_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\Windows\Explorer\ Value Name: NoDataExecutionPrevention Type: REG_DWORD Value: 0

Fix: F-27885r475909_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> File Explorer -> "Turn off Data Execution Prevention for Explorer" to "Disabled".

a

Turning off File Explorer heap termination on corruption must be disabled.

SC-5 - Low - CCI-002385 - V-226196 - SV-226196r794487_rule

RMF Control

SC-5

Severity

L

CCI

Version

WN12-CC-000090

Vuln IDs

V-226196
V-15718

Rule IDs

SV-226196r794487_rule
SV-53137

Legacy plug-in applications may continue to function when a File Explorer session has become corrupt. Disabling this feature will prevent this.

Checks: C-27898r475911_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\Windows\Explorer\ Value Name: NoHeapTerminationOnCorruption Type: REG_DWORD Value: 0

Fix: F-27886r475912_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> File Explorer -> "Turn off heap termination on corruption" to "Disabled".

b

File Explorer shell protocol must run in protected mode.

CM-6 - Medium - CCI-000366 - V-226197 - SV-226197r794501_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-CC-000091

Vuln IDs

V-226197
V-15683

Rule IDs

SV-226197r794501_rule
SV-53045

The shell protocol will limit the set of folders applications can open when run in protected mode. Restricting files an application can open to a limited set of folders increases the security of Windows.

Checks: C-27899r475914_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\Microsoft\Windows\CurrentVersion\Policies\Explorer\ Value Name: PreXPSP2ShellProtocolBehavior Type: REG_DWORD Value: 0

Fix: F-27887r475915_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> File Explorer -> "Turn off shell protocol protected mode" to "Disabled".

b

The location feature must be turned off.

CM-7 - Medium - CCI-000381 - V-226198 - SV-226198r794441_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-CC-000095

Vuln IDs

V-226198
V-36708

Rule IDs

SV-226198r794441_rule
SV-51748

The location service on systems may allow sensitive data to be used by applications on the system. This should be turned off unless explicitly allowed for approved systems/applications.

Checks: C-27900r475917_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\Windows\LocationAndSensors\ Value Name: DisableLocation Type: REG_DWORD Value: 1 (Enabled) If location services are approved for the system by the organization, this may be set to "Disabled" (0). This must be documented with the ISSO.

Fix: F-27888r475918_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Location and Sensors -> "Turn off location" to "Enabled". If location services are approved by the organization for a device, this must be documented.

b

Passwords must not be saved in the Remote Desktop Client.

IA-11 - Medium - CCI-002038 - V-226199 - SV-226199r794482_rule

RMF Control

IA-11

Severity

M

CCI

Version

WN12-CC-000096

Vuln IDs

V-226199
V-14247

Rule IDs

SV-226199r794482_rule
SV-52958

Saving passwords in the Remote Desktop Client could allow an unauthorized user to establish a remote desktop session to another system. The system must be configured to prevent users from saving passwords in the Remote Desktop Client.

Checks: C-27901r475920_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\Windows NT\Terminal Services\ Value Name: DisablePasswordSaving Type: REG_DWORD Value: 1

Fix: F-27889r475921_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Connection Client -> "Do not allow passwords to be saved" to "Enabled".

b

Local drives must be prevented from sharing with Remote Desktop Session Hosts. (Remote Desktop Services Role).

SC-4 - Medium - CCI-001090 - V-226200 - SV-226200r794456_rule

RMF Control

SC-4

Severity

M

CCI

Version

WN12-CC-000098

Vuln IDs

V-226200
V-14249

Rule IDs

SV-226200r794456_rule
SV-52959

Preventing users from sharing the local drives on their client computers to Remote Session Hosts that they access helps reduce possible exposure of sensitive data.

Checks: C-27902r475923_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\Windows NT\Terminal Services\ Value Name: fDisableCdm Type: REG_DWORD Value: 1

Fix: F-27890r475924_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Device and Resource Redirection -> "Do not allow drive redirection" to "Enabled".

b

Remote Desktop Services must always prompt a client for passwords upon connection.

IA-11 - Medium - CCI-002038 - V-226201 - SV-226201r794483_rule

RMF Control

IA-11

Severity

M

CCI

Version

WN12-CC-000099

Vuln IDs

V-226201
V-3453

Rule IDs

SV-226201r794483_rule
SV-52898

This setting controls the ability of users to supply passwords automatically as part of their remote desktop connection. Disabling this setting would allow anyone to use the stored credentials in a connection item to connect to the terminal server.

Checks: C-27903r475926_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\Windows NT\Terminal Services\ Value Name: fPromptForPassword Type: REG_DWORD Value: 1

Fix: F-27891r475927_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Security -> "Always prompt for password upon connection" to "Enabled".

b

Remote Desktop Services must be configured with the client connection encryption set to the required level.

AC-17 - Medium - CCI-000068 - V-226202 - SV-226202r794408_rule

RMF Control

AC-17

Severity

M

CCI

CCI-000068

Version

WN12-CC-000100

Vuln IDs

V-226202
V-3454

Rule IDs

SV-226202r794408_rule
SV-52899

Remote connections must be encrypted to prevent interception of data or sensitive information. Selecting "High Level" will ensure encryption of Remote Desktop Services sessions in both directions.

Checks: C-27904r475929_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\Windows NT\Terminal Services\ Value Name: MinEncryptionLevel Type: REG_DWORD Value: 3

Fix: F-27892r475930_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Security -> "Set client connection encryption level" to "Enabled" and "High Level".

b

Remote Desktop Services must delete temporary folders when a session is terminated.

CM-6 - Medium - CCI-000366 - V-226203 - SV-226203r794502_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-CC-000103

Vuln IDs

V-226203
V-3456

Rule IDs

SV-226203r794502_rule
SV-52901

Remote desktop session temporary folders must always be deleted after a session is over to prevent hard disk clutter and potential leakage of information. This setting controls the deletion of the temporary folders when the session is terminated.

Checks: C-27905r475932_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\Windows NT\Terminal Services\ Value Name: DeleteTempDirsOnExit Type: REG_DWORD Value: 1

Fix: F-27893r475933_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Temporary Folders -> "Do not delete temp folder upon exit" to "Disabled".

b

Remote Desktop Services must be configured to use session-specific temporary folders.

CM-6 - Medium - CCI-000366 - V-226204 - SV-226204r794503_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-CC-000104

Vuln IDs

V-226204
V-3455

Rule IDs

SV-226204r794503_rule
SV-52900

If a communal temporary folder is used for remote desktop sessions, it might be possible for users to access other users' temporary folders. If this setting is enabled, only one temporary folder is used for all remote desktop sessions. Per session temporary folders must be established.

Checks: C-27906r475935_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\Windows NT\Terminal Services\ Value Name: PerSessionTempDir Type: REG_DWORD Value: 1

Fix: F-27894r475936_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Temporary Folders -> "Do not use temporary folders per session" to "Disabled".

b

Attachments must be prevented from being downloaded from RSS feeds.

CM-6 - Medium - CCI-000366 - V-226205 - SV-226205r794504_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-CC-000105

Vuln IDs

V-226205
V-15682

Rule IDs

SV-226205r794504_rule
SV-53040

Attachments from RSS feeds may not be secure. This setting will prevent attachments from being downloaded from RSS feeds.

Checks: C-27907r475938_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\Internet Explorer\Feeds\ Value Name: DisableEnclosureDownload Type: REG_DWORD Value: 1

Fix: F-27895r475939_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> RSS Feeds -> "Prevent downloading of enclosures" to "Enabled".

b

Basic authentication for RSS feeds over HTTP must be turned off.

CM-7 - Medium - CCI-000381 - V-226206 - SV-226206r794442_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-CC-000106

Vuln IDs

V-226206
V-36709

Rule IDs

SV-226206r794442_rule
SV-51749

Basic authentication uses plain text passwords that could be used to compromise a system.

Checks: C-27908r475941_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\Internet Explorer\Feeds\ Value Name: AllowBasicAuthInClear Type: REG_DWORD Value: 0

Fix: F-27896r475942_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> RSS Feeds -> "Turn on Basic feed authentication over HTTP" to "Disabled".

a

Automatic download of updates from the Windows Store must be turned off.

CM-6 - Low - CCI-000366 - V-226207 - SV-226207r794443_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN12-CC-000109

Vuln IDs

V-226207
V-36710

Rule IDs

SV-226207r794443_rule
SV-51750

Uncontrolled system updates can introduce issues to a system. Obtaining update components from an outside source may also potentially allow sensitive information outside of the enterprise. Application updates must be obtained from an internal source.

Checks: C-27909r475944_chk

The Windows Store is not installed by default. If the \Windows\WinStore directory does not exist, this is NA. If the following registry value does not exist or is not configured as specified, this is a finding: Windows 2012 R2: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Policies\Microsoft\WindowsStore\ Value Name: AutoDownload Type: REG_DWORD Value: 0x00000002 (2) Windows 2012: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Policies\Microsoft\WindowsStore\WindowsUpdate\ Value Name: AutoDownload Type: REG_DWORD Value: 0x00000002 (2)

Fix: F-27897r475945_fix

The Windows Store is not installed by default. If the \Windows\WinStore directory does not exist, this is NA. Windows 2012 R2: Windows 2012 R2 split the original policy that configures this setting into two separate ones. Configuring either one to "Enabled" will update the registry value as identified in the Check section. Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Store -> "Turn off Automatic Download of updates on Win8 machines" or "Turn off Automatic Download and install of updates" to "Enabled". Windows 2012: Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Store -> "Turn off Automatic Download of updates" to "Enabled".

b

The Windows Store application must be turned off.

CM-6 - Medium - CCI-000366 - V-226208 - SV-226208r794444_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-CC-000110

Vuln IDs

V-226208
V-36711

Rule IDs

SV-226208r794444_rule
SV-51751

Uncontrolled installation of applications can introduce various issues, including system instability, and provide access to sensitive information. Installation of applications must be controlled by the enterprise. Turning off access to the Windows Store will limit access to publicly available applications.

Checks: C-27910r475947_chk

The Windows Store is not installed by default. If the \Windows\WinStore directory does not exist, this is NA. 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\WindowsStore\ Value Name: RemoveWindowsStore Type: REG_DWORD Value: 1

Fix: F-27898r475948_fix

The Windows Store is not installed by default. If the \Windows\WinStore directory does not exist, this is NA. Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Store -> "Turn off the Store application" to "Enabled".

b

Users must be prevented from changing installation options.

CM-11 - Medium - CCI-001812 - V-226209 - SV-226209r794473_rule

RMF Control

CM-11

Severity

M

CCI

Version

WN12-CC-000115

Vuln IDs

V-226209
V-15685

Rule IDs

SV-226209r794473_rule
SV-53061

Installation options for applications are typically controlled by administrators. This setting prevents users from changing installation options that may bypass security features.

Checks: C-27911r475950_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\Windows\Installer\ Value Name: EnableUserControl Type: REG_DWORD Value: 0

Fix: F-27899r475951_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Installer -> "Allow user control over installs" to "Disabled".

c

The Windows Installer Always install with elevated privileges option must be disabled.

CM-11 - High - CCI-001812 - V-226210 - SV-226210r794474_rule

RMF Control

CM-11

Severity

H

CCI

Version

WN12-CC-000116

Vuln IDs

V-226210
V-34974

Rule IDs

SV-226210r794474_rule
SV-52954

Standard user accounts must not be granted elevated privileges. Enabling Windows Installer to elevate privileges when installing applications can allow malicious persons and applications to gain full control of a system.

Checks: C-27912r475953_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\Windows\Installer\ Value Name: AlwaysInstallElevated Type: REG_DWORD Value: 0

Fix: F-27900r475954_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Installer -> "Always install with elevated privileges" to "Disabled".

b

Users must be notified if a web-based program attempts to install software.

CM-6 - Medium - CCI-000366 - V-226211 - SV-226211r794505_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-CC-000117

Vuln IDs

V-226211
V-15684

Rule IDs

SV-226211r794505_rule
SV-53056

Users must be aware of attempted program installations. This setting ensures users are notified if a web-based program attempts to install software.

Checks: C-27913r475956_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\Windows\Installer\ Value Name: SafeForScripting Type: REG_DWORD Value: 0

Fix: F-27901r475957_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Installer -> "Prevent Internet Explorer security prompt for Windows Installer scripts" to "Disabled".

a

Nonadministrators must be prevented from applying vendor-signed updates.

CM-11 - Low - CCI-001812 - V-226212 - SV-226212r794475_rule

RMF Control

CM-11

Severity

L

CCI

Version

WN12-CC-000118

Vuln IDs

V-226212
V-15686

Rule IDs

SV-226212r794475_rule
SV-53065

Uncontrolled system updates can introduce issues to a system. This setting will prevent users from applying vendor-signed updates (though they may be from a trusted source).

Checks: C-27914r475959_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\Windows\Installer\ Value Name: DisableLUAPatching Type: REG_DWORD Value: 1

Fix: F-27902r475960_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Installer -> "Prohibit non-administrators from applying vendor signed updates" to "Enabled".

b

Windows Media Digital Rights Management (DRM) must be prevented from accessing the Internet.

CM-7 - Medium - CCI-000381 - V-226213 - SV-226213r794445_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-CC-000120

Vuln IDs

V-226213
V-15722

Rule IDs

SV-226213r794445_rule
SV-53139

Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. This check verifies that Windows Media DRM will be prevented from accessing the Internet.

Checks: C-27915r475962_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\WMDRM\ Value Name: DisableOnline Type: REG_DWORD Value: 1

Fix: F-27903r475963_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Media Digital Rights Management -> "Prevent Windows Media DRM Internet Access" to "Enabled".

a

Users must not be presented with Privacy and Installation options on first use of Windows Media Player.

CM-6 - Low - CCI-000366 - V-226214 - SV-226214r794506_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN12-CC-000121

Vuln IDs

V-226214
V-15687

Rule IDs

SV-226214r794506_rule
SV-53069

Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. This setting prevents users from being presented with Privacy and Installation options on first use of Windows Media Player, which could enable some communication with the vendor.

Checks: C-27916r475965_chk

Windows Media Player is not installed by default. If it is not installed, this is NA. 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\WindowsMediaPlayer\ Value Name: GroupPrivacyAcceptance Type: REG_DWORD Value: 1

Fix: F-27904r475966_fix

If Windows Media Player is installed, configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Media Player -> "Do Not Show First Use Dialog Boxes" to "Enabled".

b

Windows Media Player must be configured to prevent automatic checking for updates.

CM-11 - Medium - CCI-001812 - V-226215 - SV-226215r794476_rule

RMF Control

CM-11

Severity

M

CCI

Version

WN12-CC-000122

Vuln IDs

V-226215
V-3480

Rule IDs

SV-226215r794476_rule
SV-53130

Uncontrolled system updates can introduce issues to a system. The automatic check for updates performed by Windows Media Player must be disabled to ensure a constant platform and to prevent the introduction of unknown\untested software on the system.

Checks: C-27917r475968_chk

Windows Media Player is not installed by default. If it is not installed, this is NA. 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\WindowsMediaPlayer\ Value Name: DisableAutoupdate Type: REG_DWORD Value: 1

Fix: F-27905r475969_fix

If Windows Media Player is installed, configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Media Player -> "Prevent Automatic Updates" to "Enabled".

c

The Windows Remote Management (WinRM) client must not use Basic authentication.

MA-4 - High - CCI-000877 - V-226216 - SV-226216r794449_rule

RMF Control

MA-4

Severity

H

CCI

CCI-000877

Version

WN12-CC-000123

Vuln IDs

V-226216
V-36712

Rule IDs

SV-226216r794449_rule
SV-51752

Basic authentication uses plain text passwords that could be used to compromise a system.

Checks: C-27918r475971_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\Windows\WinRM\Client\ Value Name: AllowBasic Type: REG_DWORD Value: 0

Fix: F-27906r475972_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Remote Management (WinRM) -> WinRM Client -> "Allow Basic authentication" to "Disabled".

b

The Windows Remote Management (WinRM) client must not allow unencrypted traffic.

MA-4 - Medium - CCI-002890 - V-226217 - SV-226217r794485_rule

RMF Control

MA-4

Severity

M

CCI

CCI-002890

Version

WN12-CC-000124

Vuln IDs

V-226217
V-36713

Rule IDs

SV-226217r794485_rule
SV-51753

Unencrypted remote access to a system can allow sensitive information to be compromised. Windows remote management connections must be encrypted to prevent this.

Checks: C-27919r475974_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\Windows\WinRM\Client\ Value Name: AllowUnencryptedTraffic Type: REG_DWORD Value: 0

Fix: F-27907r475975_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Remote Management (WinRM) -> WinRM Client -> "Allow unencrypted traffic" to "Disabled".

b

The Windows Remote Management (WinRM) client must not use Digest authentication.

MA-4 - Medium - CCI-000877 - V-226218 - SV-226218r794450_rule

RMF Control

MA-4

Severity

M

CCI

CCI-000877

Version

WN12-CC-000125

Vuln IDs

V-226218
V-36714

Rule IDs

SV-226218r794450_rule
SV-51754

Digest authentication is not as strong as other options and may be subject to man-in-the-middle attacks.

Checks: C-27920r475977_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\Windows\WinRM\Client\ Value Name: AllowDigest Type: REG_DWORD Value: 0

Fix: F-27908r475978_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Remote Management (WinRM) -> WinRM Client -> "Disallow Digest authentication" to "Enabled".

c

The Windows Remote Management (WinRM) service must not use Basic authentication.

MA-4 - High - CCI-000877 - V-226219 - SV-226219r794451_rule

RMF Control

MA-4

Severity

H

CCI

CCI-000877

Version

WN12-CC-000126

Vuln IDs

V-226219
V-36718

Rule IDs

SV-226219r794451_rule
SV-51755

Basic authentication uses plain text passwords that could be used to compromise a system.

Checks: C-27921r475980_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\Windows\WinRM\Service\ Value Name: AllowBasic Type: REG_DWORD Value: 0

Fix: F-27909r475981_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Remote Management (WinRM) -> WinRM Service -> "Allow Basic authentication" to "Disabled".

b

The Windows Remote Management (WinRM) service must not allow unencrypted traffic.

MA-4 - Medium - CCI-002890 - V-226220 - SV-226220r794486_rule

RMF Control

MA-4

Severity

M

CCI

CCI-002890

Version

WN12-CC-000127

Vuln IDs

V-226220
V-36719

Rule IDs

SV-226220r794486_rule
SV-51756

Unencrypted remote access to a system can allow sensitive information to be compromised. Windows remote management connections must be encrypted to prevent this.

Checks: C-27922r475983_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\Windows\WinRM\Service\ Value Name: AllowUnencryptedTraffic Type: REG_DWORD Value: 0

Fix: F-27910r475984_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Remote Management (WinRM) -> WinRM Service -> "Allow unencrypted traffic" to "Disabled".

b

The Windows Remote Management (WinRM) service must not store RunAs credentials.

IA-11 - Medium - CCI-002038 - V-226221 - SV-226221r794484_rule

RMF Control

IA-11

Severity

M

CCI

Version

WN12-CC-000128

Vuln IDs

V-226221
V-36720

Rule IDs

SV-226221r794484_rule
SV-51757

Storage of administrative credentials could allow unauthorized access. Disallowing the storage of RunAs credentials for Windows Remote Management will prevent them from being used with plug-ins.

Checks: C-27923r475986_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\Windows\WinRM\Service\ Value Name: DisableRunAs Type: REG_DWORD Value: 1

Fix: F-27911r475987_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Remote Management (WinRM) -> WinRM Service -> "Disallow WinRM from storing RunAs credentials" to "Enabled".

b

The Remote Desktop Session Host must require secure RPC communications.

AC-17 - Medium - CCI-001453 - V-226222 - SV-226222r794457_rule

RMF Control

AC-17

Severity

M

CCI

CCI-001453

Version

WN12-CC-000130

Vuln IDs

V-226222
V-4447

Rule IDs

SV-226222r794457_rule
SV-52932

Allowing unsecure RPC communication exposes the system to man-in-the-middle attacks and data disclosure attacks. A man-in-the-middle attack occurs when an intruder captures packets between a client and server and modifies them before allowing the packets to be exchanged. Usually the attacker will modify the information in the packets in an attempt to cause either the client or server to reveal sensitive information.

Checks: C-27924r475989_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\Windows NT\Terminal Services\ Value Name: fEncryptRPCTraffic Type: REG_DWORD Value: 1

Fix: F-27912r475990_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Security -> "Require secure RPC communication" to "Enabled".

b

Users must be prevented from mapping local COM ports and redirecting data from the Remote Desktop Session Host to local COM ports. (Remote Desktop Services Role).

AC-17 - Medium - CCI-002314 - V-226224 - SV-226224r794459_rule

RMF Control

AC-17

Severity

M

CCI

Version

WN12-CC-000132

Vuln IDs

V-226224
V-15997

Rule IDs

SV-226224r794459_rule
SV-52224

Preventing the redirection of Remote Desktop session data to a client computer's COM ports helps reduce possible exposure of sensitive data.

Checks: C-27926r475995_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\Windows NT\Terminal Services\ Value Name: fDisableCcm Type: REG_DWORD Value: 1

Fix: F-27914r475996_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Device and Resource Redirection -> "Do not allow COM port redirection" to "Enabled".

b

Users must be prevented from mapping local LPT ports and redirecting data from the Remote Desktop Session Host to local LPT ports. (Remote Desktop Services Role).

AC-17 - Medium - CCI-002314 - V-226225 - SV-226225r794460_rule

RMF Control

AC-17

Severity

M

CCI

Version

WN12-CC-000133

Vuln IDs

V-226225
V-15998

Rule IDs

SV-226225r794460_rule
SV-52226

Preventing the redirection of Remote Desktop session data to a client computer's LPT ports helps reduce possible exposure of sensitive data.

Checks: C-27927r475998_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\Windows NT\Terminal Services\ Value Name: fDisableLPT Type: REG_DWORD Value: 1

Fix: F-27915r475999_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Device and Resource Redirection -> "Do not allow LPT port redirection" to "Enabled".

b

The system must be configured to ensure smart card devices can be redirected to the Remote Desktop session. (Remote Desktop Services Role).

AC-17 - Medium - CCI-002314 - V-226226 - SV-226226r794461_rule

RMF Control

AC-17

Severity

M

CCI

Version

WN12-CC-000134

Vuln IDs

V-226226
V-16000

Rule IDs

SV-226226r794461_rule
SV-52230

Enabling the redirection of smart card devices allows their use within Remote Desktop sessions.

Checks: C-27928r476001_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\Windows NT\Terminal Services\ Value Name: fEnableSmartCard Type: REG_DWORD Value: 1

Fix: F-27916r476002_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Device and Resource Redirection -> "Do not allow smart card device redirection" to "Disabled".

b

Users must be prevented from redirecting Plug and Play devices to the Remote Desktop Session Host. (Remote Desktop Services Role).

AC-17 - Medium - CCI-002314 - V-226227 - SV-226227r794462_rule

RMF Control

AC-17

Severity

M

CCI

Version

WN12-CC-000135

Vuln IDs

V-226227
V-15999

Rule IDs

SV-226227r794462_rule
SV-52229

Preventing the redirection of Plug and Play devices in Remote Desktop sessions helps reduce possible exposure of sensitive data.

Checks: C-27929r476004_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\Windows NT\Terminal Services\ Value Name: fDisablePNPRedir Type: REG_DWORD Value: 1

Fix: F-27917r476005_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Device and Resource Redirection -> "Do not allow supported Plug and Play device redirection" to "Enabled".

b

Only the default client printer must be redirected to the Remote Desktop Session Host. (Remote Desktop Services Role).

CM-6 - Medium - CCI-000366 - V-226228 - SV-226228r794448_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-CC-000136

Vuln IDs

V-226228
V-40204

Rule IDs

SV-226228r794448_rule
SV-52163

Allowing the redirection of only the default client printer to a Remote Desktop session helps reduce possible exposure of sensitive data.

Checks: C-27930r476007_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\Windows NT\Terminal Services\ Value Name: RedirectOnlyDefaultClientPrinter Type: REG_DWORD Value: 1

Fix: F-27918r476008_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Printer Redirection -> "Redirect only the default client printer" to "Enabled".

b

The display of slide shows on the lock screen must be disabled (Windows 2012 R2).

CM-7 - Medium - CCI-000381 - V-226229 - SV-226229r794446_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-CC-000138

Vuln IDs

V-226229
V-43238

Rule IDs

SV-226229r794446_rule
SV-56343

Slide shows that are displayed on the lock screen could display sensitive information to unauthorized personnel. Turning off this feature will limit access to the information to a logged on user.

Checks: C-27931r476531_chk

This requirement is NA for the initial release of Windows 2012. It is applicable to Windows 2012 R2. Verify the registry value below. If it does not exist or is not configured as specified, this is a finding. Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Personalization\ Value Name: NoLockScreenSlideshow Value Type: REG_DWORD Value: 1

Fix: F-27919r476532_fix

This requirement is NA for the initial release of Windows 2012. It is applicable to Windows 2012 R2. Configure the policy value for Computer Configuration -> Administrative Templates -> Control Panel -> Personalization -> "Prevent enabling lock screen slide show" to "Enabled".

b

Windows 2012 R2 must include command line data in process creation events.

AU-3 - Medium - CCI-000135 - V-226230 - SV-226230r794409_rule

RMF Control

AU-3

Severity

M

CCI

CCI-000135

Version

WN12-CC-000139

Vuln IDs

V-226230
V-43239

Rule IDs

SV-226230r794409_rule
SV-56344

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Enabling "Include command line data for process creation events" will record the command line information with the process creation events in the log. This can provide additional detail when malware has run on a system. Satisfies: SRG-OS-000042-GPOS-00021

Checks: C-27932r476534_chk

This requirement is NA for the initial release of Windows 2012. It is applicable to Windows 2012 R2. Verify the registry value below. If it does not exist or is not configured as specified, this is a finding. Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Audit\ Value Name: ProcessCreationIncludeCmdLine_Enabled Value Type: REG_DWORD Value: 0x00000001 (1)

Fix: F-27920r476535_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Audit Process Creation >> "Include command line in process creation events" to "Enabled".

b

The network selection user interface (UI) must not be displayed on the logon screen (Windows 2012 R2).

CM-7 - Medium - CCI-000381 - V-226231 - SV-226231r794532_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-CC-000140

Vuln IDs

V-226231
V-43240

Rule IDs

SV-226231r794532_rule
SV-56346

Enabling interaction with the network selection UI allows users to change connections to available networks without signing into Windows.

Checks: C-27933r476537_chk

This requirement is NA for the initial release of Windows 2012. It is applicable to Windows 2012 R2. Verify the registry value below. If it does not exist or is not configured as specified, this is a finding. Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Policies\Microsoft\Windows\System\ Value Name: DontDisplayNetworkSelectionUI Value Type: REG_DWORD Value: 1

Fix: F-27921r476538_fix

This requirement is NA for the initial release of Windows 2012. It is applicable to Windows 2012 R2. Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Logon -> "Do not display network selection UI" to "Enabled".

a

The setting to allow Microsoft accounts to be optional for modern style apps must be enabled (Windows 2012 R2).

CM-6 - Low - CCI-000366 - V-226232 - SV-226232r794574_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN12-CC-000141

Vuln IDs

V-226232
V-43241

Rule IDs

SV-226232r794574_rule
SV-56353

Control of credentials and the system must be maintained within the enterprise. Enabling this setting allows enterprise credentials to be used with modern style apps that support this, instead of Microsoft accounts.

Checks: C-27934r476540_chk

This requirement is NA for the initial release of Windows 2012. It is applicable to Windows 2012 R2. Verify the registry value below. If it does not exist or is not configured as specified, this is a finding. Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System Value Name: MSAOptional Value Type: REG_DWORD Value: 1

Fix: F-27922r476541_fix

This requirement is NA for the initial release of Windows 2012. It is applicable to Windows 2012 R2. Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> App Runtime -> "Allow Microsoft accounts to be optional" to "Enabled".

b

The Windows Explorer Preview pane must be disabled for Windows 2012.

CM-6 - Medium - CCI-000366 - V-226233 - SV-226233r794560_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-CC-000142

Vuln IDs

V-226233
V-102619

Rule IDs

SV-226233r794560_rule
SV-111569

A known vulnerability in Windows could allow the execution of malicious code by either opening a compromised document or viewing it in the Windows Preview pane. Organizations must disable the Windows Preview pane and Windows Detail pane.

Checks: C-27935r476543_chk

If the following registry values do not exist or are not configured as specified, this is a finding: Registry Hive: HKEY_CURRENT_USER Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer Value Name: NoPreviewPane Value Type: REG_DWORD Value: 1 Registry Hive: HKEY_CURRENT_USER Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer Value Name: NoReadingPane Value Type: REG_DWORD Value: 1

Fix: F-27923r476544_fix

Ensure the following settings are configured for Windows 2012 locally or applied through group policy. Configure the policy value for User Configuration >> Administrative Templates >> Windows Components >> File Explorer >> Explorer Frame Pane "Turn off Preview Pane" to "Enabled". Configure the policy value for User Configuration >> Administrative Templates >> Windows Components >> File Explorer >> Explorer Frame Pane "Turn on or off details pane" to "Enabled" and "Configure details pane" to "Always hide".

b

Automatically signing in the last interactive user after a system-initiated restart must be disabled (Windows 2012 R2).

CM-6 - Medium - CCI-000366 - V-226234 - SV-226234r794575_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-CC-000145

Vuln IDs

V-226234
V-43245

Rule IDs

SV-226234r794575_rule
SV-56355

Windows 2012 R2 can be configured to automatically sign the user back in after a Windows Update restart. Some protections are in place to help ensure this is done in a secure fashion; however, disabling this will prevent the caching of credentials for this purpose and also ensure the user is aware of the restart.

Checks: C-27936r476546_chk

This requirement is NA for the initial release of Windows 2012. It is applicable to Windows 2012 R2. Verify the registry value below. If it does not exist or is not configured as specified, this is a finding. Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ Value Name: DisableAutomaticRestartSignOn Value Type: REG_DWORD Value: 1

Fix: F-27924r476547_fix

This requirement is NA for the initial release of Windows 2012. It is applicable to Windows 2012 R2. Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Logon Options -> "Sign-in last interactive user automatically after a system-initiated restart" to "Disabled".

b

WDigest Authentication must be disabled.

CM-7 - Medium - CCI-000381 - V-226235 - SV-226235r794533_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-CC-000150

Vuln IDs

V-226235
V-72753

Rule IDs

SV-226235r794533_rule
SV-87391

When the WDigest Authentication protocol is enabled, plain text passwords are stored in the Local Security Authority Subsystem Service (LSASS) exposing them to theft. This setting will prevent WDigest from storing credentials in memory.

Checks: C-27937r476549_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: \SYSTEM\CurrentControlSet\Control\SecurityProviders\Wdigest\ Value Name: UseLogonCredential Type: REG_DWORD Value: 0x00000000 (0) Note: Microsoft Security Advisory update 2871997 is required for this setting to be effective on Windows 2012. It is not required for Windows 2012 R2.

Fix: F-27925r476550_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> "WDigest Authentication (disabling may require KB2871997)" to "Disabled". Note: Microsoft Security Advisory update 2871997 is required for this setting to be effective on Windows 2012. It is not required for Windows 2012 R2. This policy setting requires the installation of the SecGuide custom templates included with the STIG package. "SecGuide.admx" and "SecGuide.adml" must be copied to the \Windows\PolicyDefinitions and \Windows\PolicyDefinitions\en-US directories respectively.

b

A host-based firewall must be installed and enabled on the system.

CM-6 - Medium - CCI-000366 - V-226236 - SV-226236r794607_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-FW-000001

Vuln IDs

V-226236
V-42420

Rule IDs

SV-226236r794607_rule
SV-55085

A firewall provides a line of defense against attack, allowing or blocking inbound and outbound connections based on a set of rules.

Checks: C-27938r476552_chk

Determine if a host-based firewall is installed and enabled on the system. If a host-based firewall is not installed and enabled on the system, this is a finding. The configuration requirements will be determined by the applicable firewall STIG.

Fix: F-27926r476553_fix

Install and enable a host-based firewall on the system.

c

Systems must be maintained at a supported service pack level.

CM-6 - High - CCI-000366 - V-226237 - SV-226237r794611_rule

RMF Control

CM-6

Severity

H

CCI

Version

WN12-GE-000001

Vuln IDs

V-226237
V-1073

Rule IDs

SV-226237r794611_rule
SV-53189

Systems at unsupported service packs or releases will not receive security updates for new vulnerabilities, which leave them subject to exploitation. Systems must be maintained at a service pack level supported by the vendor with new security updates.

Checks: C-27939r476555_chk

Run "winver.exe". If the "About Windows" dialog box does not display "Microsoft Windows Server Version 6.2 (Build 9200)" or greater, this is a finding. No preview versions will be used in a production environment. Unsupported Service Packs/Releases: Windows 2012 - any release candidates or versions prior to the initial release.

Fix: F-27927r476556_fix

Update the system to a supported release or service pack level.

c

Only administrators responsible for the domain controller must have Administrator rights on the system.

AC-6 - High - CCI-002235 - V-226238 - SV-226238r794556_rule

RMF Control

AC-6

Severity

H

CCI

Version

WN12-GE-000004-DC

Vuln IDs

V-226238
V-1127

Rule IDs

SV-226238r794556_rule
SV-51157

An account that does not have Administrator duties must not have Administrator rights. Such rights would allow the account to bypass or modify required security restrictions on that machine and make it vulnerable to attack. System administrators must log on to systems only using accounts with the minimum level of authority necessary. Standard user accounts must not be members of the built-in Administrators group.

Checks: C-27940r476558_chk

Review the Administrators group. Only the appropriate administrator groups or accounts responsible for administration of the system may be members of the group. Standard user accounts must not be members of the local administrator group. If prohibited accounts are members of the local administrators group, this is a finding. The built-in Administrator account or other required administrative accounts would not be a finding.

Fix: F-27928r476559_fix

Configure the system to include only administrator groups or accounts that are responsible for the system in the Administrators group. Remove any standard user accounts.

c

Local volumes must use a format that supports NTFS attributes.

AC-3 - High - CCI-000213 - V-226239 - SV-226239r794530_rule

RMF Control

AC-3

Severity

H

CCI

Version

WN12-GE-000005

Vuln IDs

V-226239
V-1081

Rule IDs

SV-226239r794530_rule
SV-52843

The ability to set access permissions and auditing is critical to maintaining the security and proper access controls of a system. To support this, local volumes must be formatted using a file system that supports NTFS attributes.

Checks: C-27941r476561_chk

Open "Computer Management". Select "Disk Management" under "Storage". For each local volume, if the file system does not indicate "NTFS", this is a finding. "ReFS" (Resilient File System) is also acceptable and would not be a finding. “CSV” (Cluster Share Volumes) is also acceptable and would not be a finding. This does not apply to system partitions such as the Recovery and EFI System Partition.

Fix: F-27929r476562_fix

Format local volumes to use NTFS or ReFS.

b

Permissions for system drive root directory (usually C:\) must conform to minimum requirements.

AC-3 - Medium - CCI-002165 - V-226240 - SV-226240r794554_rule

RMF Control

AC-3

Severity

M

CCI

CCI-002165

Version

WN12-GE-000006

Vuln IDs

V-226240
V-40178

Rule IDs

SV-226240r794554_rule
SV-52136

Changing the system's file and directory permissions allows the possibility of unauthorized and anonymous modification to the operating system and installed applications. The default permissions are adequate when the Security Option "Network access: Let everyone permissions apply to anonymous users" is set to "Disabled" (V-3377).

Checks: C-27942r476564_chk

The default permissions are adequate when the Security Option "Network access: Let everyone permissions apply to anonymous users" is set to "Disabled" (V-3377). If the default ACLs are maintained and the referenced option is set to "Disabled", this is not a finding. Verify the default permissions for the system drive's root directory (usually C:\). Nonprivileged groups such as Users or Authenticated Users must not have greater than Read & execute permissions except where noted as defaults. (Individual accounts must not be used to assign permissions.) Viewing in File Explorer: View the Properties of system drive root directory. Select the "Security" tab, and the "Advanced" button. C:\ Type - "Allow" for all Inherited from - "None" for all Principal - Access - Applies to SYSTEM - Full control - This folder, subfolders and files Administrators - Full control - This folder, subfolders and files Users - Read & execute - This folder, subfolders and files Users - Create folders / append data - This folder and subfolders Users - Create files / write data - Subfolders only CREATOR OWNER - Full Control - Subfolders and files only Alternately, use Icacls: Open a Command prompt (admin). Enter icacls followed by the directory: icacls c:\ The following results should be displayed: c:\ NT AUTHORITY\SYSTEM:(OI)(CI)(F) BUILTIN\Administrators:(OI)(CI)(F) BUILTIN\Users:(OI)(CI)(RX) BUILTIN\Users:(CI)(AD) BUILTIN\Users:(CI)(IO)(WD) CREATOR OWNER:(OI)(CI)(IO)(F) Successfully processed 1 files; Failed processing 0 files

Fix: F-27930r476565_fix

Maintain the default permissions for the system drive's root directory and configure the Security Option: "Network access: Let everyone permissions apply to anonymous users" to "Disabled" (V-3377). Default Permissions C:\ Type - "Allow" for all Inherited from - "None" for all Principal - Access - Applies to SYSTEM - Full control - This folder, subfolders and files Administrators - Full control - This folder, subfolders and files Users - Read & execute - This folder, subfolders and files Users - Create folders / append data - This folder and subfolders Users - Create files / write data - Subfolders only CREATOR OWNER - Full Control - Subfolders and files only

b

Permissions for program file directories must conform to minimum requirements.

AC-3 - Medium - CCI-002165 - V-226241 - SV-226241r794555_rule

RMF Control

AC-3

Severity

M

CCI

CCI-002165

Version

WN12-GE-000007

Vuln IDs

V-226241
V-40177

Rule IDs

SV-226241r794555_rule
SV-52135

Changing the system's file and directory permissions allows the possibility of unauthorized and anonymous modification to the operating system and installed applications. The default permissions are adequate when the Security Option "Network access: Let everyone permissions apply to anonymous users" is set to "Disabled" (V-3377).

Checks: C-27943r476567_chk

The default permissions are adequate when the Security Option "Network access: Let everyone permissions apply to anonymous users" is set to "Disabled" (V-3377). If the default ACLs are maintained and the referenced option is set to "Disabled", this is not a finding. Verify the default permissions for the program file directories (Program Files and Program Files (x86)). Nonprivileged groups such as Users or Authenticated Users must not have greater than Read & execute permissions except where noted as defaults. (Individual accounts must not be used to assign permissions.) Viewing in File Explorer: For each folder, view the Properties. Select the "Security" tab, and the "Advanced" button. Default Permissions: \Program Files and \Program Files (x86) Type - "Allow" for all Inherited from - "None" for all Principal - Access - Applies to TrustedInstaller - Full control - This folder and subfolders SYSTEM - Modify - This folder only SYSTEM - Full control - Subfolders and files only Administrators - Modify - This folder only Administrators - Full control - Subfolders and files only Users - Read & execute - This folder, subfolders and files CREATOR OWNER - Full control - Subfolders and files only ALL APPLICATION PACKAGES - Read & execute - This folder, subfolders and files Alternately, use Icacls: Open a Command prompt (admin). Enter icacls followed by the directory: icacls "c:\program files" icacls "c:\program files (x86)" The following results should be displayed as each is entered: c:\program files NT SERVICE\TrustedInstaller:(F) NT SERVICE\TrustedInstaller:(CI)(IO)(F) NT AUTHORITY\SYSTEM:(M) NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(F) BUILTIN\Administrators:(M) BUILTIN\Administrators:(OI)(CI)(IO)(F) BUILTIN\Users:(RX) BUILTIN\Users:(OI)(CI)(IO)(GR,GE) CREATOR OWNER:(OI)(CI)(IO)(F) APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES:(RX) APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE) Successfully processed 1 files; Failed processing 0 files

Fix: F-27931r476568_fix

Maintain the default permissions for the program file directories and configure the Security Option: "Network access: Let everyone permissions apply to anonymous users" to "Disabled" (V-3377). Default Permissions: \Program Files and \Program Files (x86) Type - "Allow" for all Inherited from - "None" for all Principal - Access - Applies to TrustedInstaller - Full control - This folder and subfolders SYSTEM - Modify - This folder only SYSTEM - Full control - Subfolders and files only Administrators - Modify - This folder only Administrators - Full control - Subfolders and files only Users - Read & execute - This folder, subfolders and files CREATOR OWNER - Full control - Subfolders and files only ALL APPLICATION PACKAGES - Read & execute - This folder, subfolders and files

b

Permissions for Windows installation directory must conform to minimum requirements.

CM-5 - Medium - CCI-001499 - V-226242 - SV-226242r794553_rule

RMF Control

CM-5

Severity

M

CCI

CCI-001499

Version

WN12-GE-000008

Vuln IDs

V-226242
V-40179

Rule IDs

SV-226242r794553_rule
SV-52137

Changing the system's file and directory permissions allows the possibility of unauthorized and anonymous modification to the operating system and installed applications. The default permissions are adequate when the Security Option "Network access: Let everyone permissions apply to anonymous users" is set to "Disabled" (V-3377).

Checks: C-27944r476570_chk

The default permissions are adequate when the Security Option "Network access: Let everyone permissions apply to anonymous users" is set to "Disabled" (V-3377). If the default ACLs are maintained and the referenced option is set to "Disabled", this is not a finding. Verify the default permissions for the Windows installation directory (usually C:\Windows). Nonprivileged groups such as Users or Authenticated Users must not have greater than Read & execute permissions except where noted as defaults. (Individual accounts must not be used to assign permissions.) Viewing in File Explorer: View the Properties of the folder. Select the "Security" tab, and the "Advanced" button. Default Permissions: \Windows Type - "Allow" for all Inherited from - "None" for all Principal - Access - Applies to TrustedInstaller - Full control - This folder and subfolders SYSTEM - Modify - This folder only SYSTEM - Full control - Subfolders and files only Administrators - Modify - This folder only Administrators - Full control - Subfolders and files only Users - Read & execute - This folder, subfolders and files CREATOR OWNER - Full control - Subfolders and files only ALL APPLICATION PACKAGES - Read & execute - This folder, subfolders and files Alternately, use Icacls: Open a Command prompt (admin). Enter icacls followed by the directory: icacls c:\windows The following results should be displayed: c:\windows NT SERVICE\TrustedInstaller:(F) NT SERVICE\TrustedInstaller:(CI)(IO)(F) NT AUTHORITY\SYSTEM:(M) NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(F) BUILTIN\Administrators:(M) BUILTIN\Administrators:(OI)(CI)(IO)(F) BUILTIN\Users:(RX) BUILTIN\Users:(OI)(CI)(IO)(GR,GE) CREATOR OWNER:(OI)(CI)(IO)(F) APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES:(RX) APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE) Successfully processed 1 files; Failed processing 0 files

Fix: F-27932r476571_fix

Maintain the default file ACLs and configure the Security Option: "Network access: Let everyone permissions apply to anonymous users" to "Disabled" (V-3377). Default Permissions: Type - "Allow" for all Inherited from - "None" for all Principal - Access - Applies to TrustedInstaller - Full control - This folder and subfolders SYSTEM - Modify - This folder only SYSTEM - Full control - Subfolders and files only Administrators - Modify - This folder only Administrators - Full control - Subfolders and files only Users - Read & execute - This folder, subfolders and files CREATOR OWNER - Full control - Subfolders and files only ALL APPLICATION PACKAGES - Read & execute - This folder, subfolders and files

b

The system must not boot into multiple operating systems (dual-boot).

CM-6 - Medium - CCI-000366 - V-226243 - SV-226243r794576_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-GE-000010

Vuln IDs

V-226243
V-1119

Rule IDs

SV-226243r794576_rule
SV-52858

Allowing a system to boot into multiple operating systems (dual-booting) may allow security to be circumvented on a secure system.

Checks: C-27945r476573_chk

Verify the local system boots directly into Windows. Open Control Panel. Select "System". Select the "Advanced System Settings" link. Select the "Advanced" tab. Click the "Startup and Recovery" Settings button. If the drop-down list box "Default operating system:" shows any operating system other than Windows Server 2012, this is a finding.

Fix: F-27933r476574_fix

Ensure Windows Server 2012 is the only operating system installed for the system to boot into. Remove alternate operating systems.

a

Nonadministrative user accounts or groups must only have print permissions on printer shares.

AC-3 - Low - CCI-000213 - V-226244 - SV-226244r794531_rule

RMF Control

AC-3

Severity

L

CCI

Version

WN12-GE-000012

Vuln IDs

V-226244
V-1135

Rule IDs

SV-226244r794531_rule
SV-52213

Windows shares are a means by which files, folders, printers, and other resources can be published for network users to access. Improper configuration can permit access to devices and data beyond a user's need.

Checks: C-27946r476576_chk

Open "Devices and Printers" in Control Panel or through Search. If there are no printers configured, this is NA.(Exclude Microsoft Print to PDF and Microsoft XPS Document Writer, which do not support sharing.) For each configured printer: Right click on the printer. Select "Printer Properties". Select the "Sharing" tab. View whether "Share this printer" is checked. For any printers with "Share this printer" selected: Select the Security tab. If any standard user accounts or groups have permissions other than "Print", this is a finding. Standard users will typically be given "Print" permission through the Everyone group. "All APPLICATION PACKAGES" and "CREATOR OWNER" are not considered standard user accounts for this requirement.

Fix: F-27934r476577_fix

Configure the permissions on shared printers to restrict standard users to only have Print permissions. This is typically given through the Everyone group by default.

a

Outdated or unused accounts must be removed from the system or disabled.

IA-4 - Low - CCI-000795 - V-226245 - SV-226245r794538_rule

RMF Control

IA-4

Severity

L

CCI

CCI-000795

Version

WN12-GE-000014

Vuln IDs

V-226245
V-1112

Rule IDs

SV-226245r794538_rule
SV-52854

Outdated or unused accounts provide penetration points that may go undetected. Inactive accounts must be deleted if no longer necessary or, if still required, disabled until needed.

Checks: C-27947r476579_chk

Run "PowerShell". Member servers and standalone systems: Copy or enter the lines below to the PowerShell window and enter. (Entering twice may be required. Do not include the quotes at the beginning and end of the query.) "([ADSI]('WinNT://{0}' -f $env:COMPUTERNAME)).Children | Where { $_.SchemaClassName -eq 'user' } | ForEach { $user = ([ADSI]$_.Path) $lastLogin = $user.Properties.LastLogin.Value $enabled = ($user.Properties.UserFlags.Value -band 0x2) -ne 0x2 if ($lastLogin -eq $null) { $lastLogin = 'Never' } Write-Host $user.Name $lastLogin $enabled }" This will return a list of local accounts with the account name, last logon, and if the account is enabled (True/False). For example: User1 10/31/2015 5:49:56 AM True Domain Controllers: Enter the following command in PowerShell. "Search-ADAccount -AccountInactive -UsersOnly -TimeSpan 35.00:00:00" This will return accounts that have not been logged on to for 35 days, along with various attributes such as the Enabled status and LastLogonDate. Review the list of accounts returned by the above queries to determine the finding validity for each account reported. Exclude the following accounts: Built-in administrator account (Renamed, SID ending in 500) Built-in guest account (Renamed, Disabled, SID ending in 501) Application accounts If any enabled accounts have not been logged on to within the past 35 days, this is a finding. Inactive accounts that have been reviewed and deemed to be required must be documented with the ISSO.

Fix: F-27935r476580_fix

Regularly review accounts to determine if they are still active. Disable or delete any active accounts that have not been used in the last 35 days.

c

Windows 2012/2012 R2 accounts must be configured to require passwords.

IA-2 - High - CCI-000764 - V-226246 - SV-226246r794535_rule

RMF Control

IA-2

Severity

H

CCI

CCI-000764

Version

WN12-GE-000015

Vuln IDs

V-226246
V-7002

Rule IDs

SV-226246r794535_rule
SV-52940

The lack of password protection enables anyone to gain access to the information system, which opens a backdoor opportunity for intruders to compromise the system as well as other resources. Accounts on a system must require passwords.

Checks: C-27948r476582_chk

Review the password required status for enabled user accounts. Open "Windows PowerShell". Domain Controllers: Enter "Get-ADUser -Filter * -Properties PasswordNotRequired | Where PasswordNotRequired -eq True | FT Name, PasswordNotRequired, Enabled". Exclude disabled accounts (e.g., Guest) and Trusted Domain Objects (TDOs). If "PasswordNotRequired" is "True" for any enabled user account, this is a finding. Member servers and standalone systems: Enter 'Get-CimInstance -Class Win32_Useraccount -Filter "PasswordRequired=False and LocalAccount=True" | FT Name, PasswordRequired, Disabled, LocalAccount'. Exclude disabled accounts (e.g., Guest). If any enabled user accounts are returned with a "PasswordRequired" status of "False", this is a finding.

Fix: F-27936r476583_fix

Configure all enabled accounts to require passwords. The password required flag can be set by entering the following on a command line: "Net user [username] /passwordreq:yes", substituting [username] with the name of the user account.

b

Windows 2012/2012 R2 passwords must be configured to expire.

IA-5 - Medium - CCI-000199 - V-226247 - SV-226247r794529_rule

RMF Control

IA-5

Severity

M

CCI

CCI-000199

Version

WN12-GE-000016

Vuln IDs

V-226247
V-6840

Rule IDs

SV-226247r794529_rule
SV-52939

Passwords that do not expire or are reused increase the exposure of a password with greater probability of being discovered or cracked.

Checks: C-27949r476585_chk

Review the password never expires status for enabled user accounts. Open "Windows PowerShell" with elevated privileges (run as administrator). Domain Controllers: Enter "Search-ADAccount -PasswordNeverExpires -UsersOnly | Where PasswordNeverExpires -eq True | FT Name, PasswordNeverExpires, Enabled". Exclude application accounts and disabled accounts (e.g., Guest). Domain accounts requiring smart card (CAC/PIV) may also be excluded. If any enabled user accounts are returned with a "PasswordNeverExpires" status of "True", this is a finding. Member servers and standalone systems: Enter 'Get-CimInstance -Class Win32_Useraccount -Filter "PasswordExpires=False and LocalAccount=True" | FT Name, PasswordExpires, Disabled, LocalAccount'. Exclude application accounts and disabled accounts (e.g., Guest). If any enabled user accounts are returned with a "PasswordExpires" status of "False", this is a finding.

Fix: F-27937r476586_fix

Configure all enabled user account passwords to expire. Uncheck "Password never expires" for all enabled user accounts in Active Directory Users and Computers for domain accounts and Users in Computer Management for member servers and standalone systems. Document any exceptions with the ISSO.

b

System files must be monitored for unauthorized changes.

CM-6 - Medium - CCI-000366 - V-226248 - SV-226248r794614_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-GE-000017

Vuln IDs

V-226248
V-2907

Rule IDs

SV-226248r794614_rule
SV-52215

Monitoring system files for changes against a baseline on a regular basis may help detect the possible introduction of malicious code on a system.

Checks: C-27950r794613_chk

Determine whether the site monitors system files (e.g., *.exe, *.bat, *.com, *.cmd, and *.dll) on servers for unauthorized changes against a baseline on a weekly basis. If system files are not monitored for unauthorized changes, this is a finding. A properly configured and approved DoD ESS solution that supports a File Integrity Monitor (FIM) module will meet the requirement for file integrity checking.

Fix: F-27938r476589_fix

Monitor system files (e.g., *.exe, *.bat, *.com, *.cmd, and *.dll) on servers for unauthorized changes against a baseline on a weekly basis. This can be done with the use of various monitoring tools.

b

Non system-created file shares on a system must limit access to groups that require it.

SC-4 - Medium - CCI-001090 - V-226249 - SV-226249r794543_rule

RMF Control

SC-4

Severity

M

CCI

Version

WN12-GE-000018

Vuln IDs

V-226249
V-3245

Rule IDs

SV-226249r794543_rule
SV-52881

Shares on a system provide network access. To prevent exposing sensitive information, where shares are necessary, permissions must be reconfigured to give the minimum access to those accounts that require it.

Checks: C-27951r476591_chk

If only system-created shares such as "ADMIN$", "C$", and "IPC$" exist on the system, this is NA. (System-created shares will display a message that it has been shared for administrative purposes when "Properties" is selected.) Run "Computer Management". Navigate to System Tools >> Shared Folders >> Shares. Right click any non-system-created shares. Select "Properties". Select the "Share Permissions" tab. If the file shares have not been reconfigured to restrict permissions to the specific groups or accounts that require access, this is a finding. Select the "Security" tab. If the NTFS permissions have not been reconfigured to restrict permissions to the specific groups or accounts that require access, this is a finding.

Fix: F-27939r476592_fix

If a non-system-created share is required on a system, configure the share and NTFS permissions to limit access to the specific groups or accounts that require it. Remove any unnecessary non-system-created shares.

b

Software certificate installation files must be removed from Windows 2012/2012 R2.

CM-6 - Medium - CCI-000366 - V-226251 - SV-226251r794577_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-GE-000020

Vuln IDs

V-226251
V-15823

Rule IDs

SV-226251r794577_rule
SV-53141

Use of software certificates and their accompanying installation files for end users to access resources is less secure than the use of hardware-based certificates.

Checks: C-27953r476597_chk

Search all drives for *.p12 and *.pfx files. If any files with these extensions exist, this is a finding. This does not apply to server-based applications that have a requirement for certificate files or Adobe PreFlight certificate files. Some applications create files with extensions of .p12 that are not certificate installation files. Removal of non-certificate installation files from systems is not required. These must be documented with the ISSO.

Fix: F-27941r476598_fix

Remove any certificate installation files (*.p12 and *.pfx) found on a system. This does not apply to server-based applications that have a requirement for certificate files, Adobe PreFlight certificate files, or non-certificate installation files with the same extension.

b

Necessary services must be documented to maintain a baseline to determine if additional, unnecessary services have been added to a system.

CM-7 - Medium - CCI-000381 - V-226252 - SV-226252r794534_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-GE-000021

Vuln IDs

V-226252
V-3487

Rule IDs

SV-226252r794534_rule
SV-52218

Unnecessary services increase the attack surface of a system. Some services may be run under the local System account, which generally has more permissions than required by the service. Compromising a service could allow an intruder to obtain system permissions and open the system to a variety of attacks.

Checks: C-27954r476600_chk

Required services will vary between organizations, and on the role of the individual system. Organizations will develop their own list of services which will be documented and justified with the ISSO. The site's list will be provided for any security review. Services common to multiple systems can be addressed in one document. Exceptions for individual systems should be identified separately by system. Individual services specifically required to be disabled per the STIG are identified in separate requirements. If the site has not documented the services required for their system(s), this is a finding. The following can be used to view the services on a system: Run "Services.msc". Services for Windows Server 2012 roles are managed automatically, adding those necessary for a particular role. The following lists the default services for a baseline installation as a reference. This can be used as a basis for documenting the services necessary. Default Installation Name - Startup Type Application Experience - Manual (Trigger Start) Application Identity - Manual (Trigger Start) Application Information - Manual Application Layer Gateway Service - Manual Application Management - Manual Background Intelligent Transfer Service - Automatic (Delayed Start) Background Tasks Infrastructure Service - Automatic Base Filtering Engine - Automatic Certificate Propagation - Manual CNG Key Isolation - Manual (Trigger Start) COM+ Event System - Automatic COM+ System Application - Manual Computer Browser - Disabled Credential Manager - Manual Cryptographic Services - Automatic DCOM Server Process Launcher - Automatic Device Association Service - Manual (Trigger Start) Device Install Service - Manual (Trigger Start) Device Setup Manager - Manual (Trigger Start) DHCP Client - Automatic Diagnostic Policy Service - Automatic (Delayed Start) Diagnostic Service Host - Manual Diagnostic System Host - Manual Distributed Link Tracking Client - Automatic Distributed Transaction Coordinator - Automatic (Delayed Start) DNS Client - Automatic (Trigger Start) Encrypting File System (EFS) - Manual (Trigger Start) Extensible Authentication Protocol - Manual Function Discovery Provider Host - Manual Function Discovery Resource Publication - Manual Group Policy Client - Automatic (Trigger Start) Health Key and Certificate Management - Manual Human Interface Device Access - Manual (Trigger Start) Hyper-V Data Exchange Service - Manual (Trigger Start) Hyper-V Guest Shutdown Service - Manual (Trigger Start) Hyper-V Heartbeat Service - Manual (Trigger Start) Hyper-V Remote Desktop Virtualization Service - Manual (Trigger Start) Hyper-V Time Synchronization Service - Manual (Trigger Start) Hyper-V Volume Shadow Copy Requestor - Manual (Trigger Start) IKE and AuthIP IPsec Keying Modules - Manual (Trigger Start) Interactive Services Detection - Manual Internet Connection Sharing (ICS) - Disabled IP Helper - Automatic IPsec Policy Agent - Manual (Trigger Start) KDC Proxy Server service (KPS) - Manual KtmRm for Distributed Transaction Coordinator - Manual (Trigger Start) Link-Layer Topology Discovery Mapper - Manual Local Session Manager - Automatic Microsoft iSCSI Initiator Service - Manual Microsoft Software Shadow Copy Provider - Manual Multimedia Class Scheduler - Manual Net.Tcp Port Sharing Service - Disabled Netlogon - Manual Network Access Protection Agent - Manual Network Connections - Manual Network Connectivity Assistant - Manual (Trigger Start) Network List Service - Manual Network Location Awareness - Automatic Network Store Interface Service - Automatic Optimize drives - Manual Performance Counter DLL Host - Manual Performance Logs & Alerts - Manual Plug and Play - Manual Portable Device Enumerator Service - Manual (Trigger Start) Power - Automatic Print Spooler - Automatic Printer Extensions and Notifications - Manual Problem Reports and Solutions Control Panel Support - Manual Remote Access Auto Connection Manager - Manual Remote Access Connection Manager - Manual Remote Desktop Configuration - Manual Remote Desktop Services - Manual Remote Desktop Services UserMode Port Redirector - Manual Remote Procedure Call (RPC) - Automatic Remote Procedure Call (RPC) Locator - Manual Remote Registry - Automatic (Trigger Start) Resultant Set of Policy Provider - Manual Routing and Remote Access - Disabled RPC Endpoint Mapper - Automatic Secondary Logon - Manual Secure Socket Tunneling Protocol Service - Manual Security Accounts Manager - Automatic Server - Automatic Shell Hardware Detection - Automatic Smart Card - Disabled Smart Card Removal Policy - Manual SNMP Trap - Manual Software Protection - Automatic (Delayed Start, Trigger Start) Special Administration Console Helper - Manual Spot Verifier - Manual (Trigger Start) SSDP Discovery - Disabled Superfetch - Manual System Event Notification Service - Automatic Task Scheduler - Automatic TCP/IP NetBIOS Helper - Automatic (Trigger Start) Telephony - Manual Themes - Automatic Thread Ordering Server - Manual UPnP Device Host - Disabled User Access Logging Service - Automatic (Delayed Start) User Profile Service - Automatic Virtual Disk - Manual Volume Shadow Copy - Manual Windows All-User Install Agent - Manual (Trigger Start) Windows Audio - Manual Windows Audio Endpoint Builder - Manual Windows Color System - Manual Windows Driver Foundation - User-mode Driver Framework - Manual (Trigger Start) Windows Error Reporting Service - Manual (Trigger Start) Windows Event Collector - Manual Windows Event Log - Automatic Windows Firewall - Automatic Windows Font Cache Service - Automatic Windows Installer - Manual Windows Licensing Monitoring Service - Automatic Windows Management Instrumentation - Automatic Windows Modules Installer - Manual Windows Remote Management (WS-Management) - Automatic Windows Store Service (WSService) - Manual (Trigger Start) Windows Time - Manual (Trigger Start) Windows Update - Manual WinHTTP Web Proxy Auto-Discovery Service - Manual Wired AutoConfig - Manual WMI Performance Adapter - Manual Workstation - Automatic

Fix: F-27942r476601_fix

Document the services required for the system to operate. Remove or disable any services that are not required.

b

Servers must have a host-based Intrusion Detection System.

CM-6 - Medium - CCI-000366 - V-226253 - SV-226253r794618_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-GE-000022

Vuln IDs

V-226253
V-3289

Rule IDs

SV-226253r794618_rule
SV-52105

A properly configured host-based Intrusion Detection System provides another level of defense against unauthorized access to critical servers. With proper configuration and logging enabled, such a system can stop and/or alert for many attempts to gain unauthorized access to resources.

Checks: C-27955r794617_chk

Determine whether there is a host-based Intrusion Detection System on each server. If the HIPS component of ESS 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. 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 ISSO. If a host-based Intrusion Detection System is not installed on the system, this is a finding.

Fix: F-27943r476604_fix

Install a host-based Intrusion Detection System on each server.

b

Windows Server 2012 / 2012 R2 must employ automated mechanisms to determine the state of system components with regard to flaw remediation using the following frequency: continuously, where ESS is used; 30 days, for any additional internal network scans n

SI-2 - Medium - CCI-001233 - V-226254 - SV-226254r794616_rule

RMF Control

SI-2

Severity

M

CCI

CCI-001233

Version

WN12-GE-000023

Vuln IDs

V-226254
V-36734

Rule IDs

SV-226254r794616_rule
SV-51582

Without the use of automated mechanisms to scan for security flaws on a continuous and/or periodic basis, the operating system or other system components may remain vulnerable to the exploits presented by undetected software flaws. The operating system may have an integrated solution incorporating continuous scanning using ESS and periodic scanning using other tools..

Checks: C-27956r794615_chk

Verify DoD-approved ESS software is installed and properly operating. Ask the site ISSM for documentation of the ESS software installation and configuration. If the ISSM is not able to provide a documented configuration for an installed ESS or if the ESS software is not properly maintained or used, this is a finding. Note: Example of documentation can be a copy of the site's CCB approved Software Baseline with version of software noted or a memo from the ISSM stating current ESS software and version.

Fix: F-27944r641873_fix

Install DoD-approved ESS software and ensure it is operating continuously.

b

The system must support automated patch management tools to facilitate flaw remediation.

CM-6 - Medium - CCI-000366 - V-226255 - SV-226255r794612_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-GE-000024

Vuln IDs

V-226255
V-36735

Rule IDs

SV-226255r794612_rule
SV-51583

The organization (including any contractor to the organization) must promptly install security-relevant software updates (e.g., patches, service packs, hot fixes). Flaws discovered during security assessments, continuous monitoring, incident response activities, or information system error handling must also be addressed.

Checks: C-27957r476609_chk

Verify the organization has an automated process to install security-related software updates. If it does not, this is a finding.

Fix: F-27945r476610_fix

Establish a process to automatically install security-related software updates.

b

The system must query the certification authority to determine whether a public key certificate has been revoked before accepting the certificate for authentication purposes.

CM-6 - Medium - CCI-000366 - V-226256 - SV-226256r794542_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-GE-000025

Vuln IDs

V-226256
V-36736

Rule IDs

SV-226256r794542_rule
SV-51584

Failure to verify a certificate's revocation status can result in the system accepting a revoked, and therefore unauthorized, certificate. This could result in the installation of unauthorized software or a connection for rogue networks, depending on the use for which the certificate is intended. Querying for certificate revocation mitigates the risk that the system will accept an unauthorized certificate.

Checks: C-27958r476612_chk

Verify the system has software installed and running that provides certificate validation and revocation checking. If it does not, this is a finding.

Fix: F-27946r476613_fix

Install software that provides certificate validation and revocation checking.

b

File Transfer Protocol (FTP) servers must be configured to prevent anonymous logons.

CM-6 - Medium - CCI-000366 - V-226257 - SV-226257r794578_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-GE-000026

Vuln IDs

V-226257
V-1120

Rule IDs

SV-226257r794578_rule
SV-52106

The FTP service allows remote users to access shared files and directories. Allowing anonymous FTP connections makes user auditing difficult. Using accounts that have administrator privileges to log on to FTP risks that the userid and password will be captured on the network and give administrator access to an unauthorized user.

Checks: C-27959r476615_chk

If FTP is not installed on the system, this is NA. Determine the IP address and port number assigned to FTP sites from documentation or configuration. If Microsoft FTP is used, open "Internet Information Services (IIS) Manager". Select "Sites" under the server name. For any sites that reference FTP, view the Binding information for IP address and port. The standard port for FTP is 21, however this may be changed. Open a "Command Prompt". Attempt to log on as the user "anonymous" with the following commands: Note: Returned results may vary depending on the FTP server software. C:\> "ftp" ftp> "Open IP Address Port" (Substituting [IP Address] and [Port] with the information previously identified. If no IP Address was listed in the Binding, attempt using "localhost".) (Connected to IP Address 220 Microsoft FTP Service) User (IP Address): "anonymous" (331 Anonymous access allowed, send identity (e-mail name) as password.) Password: "password" (230 User logged in.) ftp> If the response indicates that an anonymous FTP login was permitted, this is a finding. If accounts with administrator privileges are used to access FTP, this is a CAT I finding.

Fix: F-27947r476616_fix

Configure the FTP service to prevent anonymous logons.

c

File Transfer Protocol (FTP) servers must be configured to prevent access to the system drive.

CM-6 - High - CCI-000366 - V-226258 - SV-226258r794579_rule

RMF Control

CM-6

Severity

H

CCI

Version

WN12-GE-000027

Vuln IDs

V-226258
V-1121

Rule IDs

SV-226258r794579_rule
SV-52212

The FTP service allows remote users to access shared files and directories. Access outside of the specific directories of shared data could provide access to system resources and compromise the system.

Checks: C-27960r476618_chk

If FTP is not installed on the system, this is NA. Determine the IP address and port number assigned to FTP sites from documentation or configuration. If Microsoft FTP is used, open "Internet Information Services (IIS) Manager". Select "Sites" under the server name. For any sites that reference FTP, view the Binding information for IP address and port. The standard port for FTP is 21, however this may be changed. Open a "Command Prompt". Access the FTP site and review accessible directories with the following commands: Note: Returned results may vary depending on the FTP server software. C:\> "ftp" ftp> "Open IP Address Port" (Substituting [IP Address] and [Port] with the information previously identified. If no IP Address was listed in the Binding, attempt using "localhost".) (Connected to IP Address 220 Microsoft FTP Service) User (IP Address): "FTP User" (Substituting [FTP User] with an account identified that is allowed access. If it was determined that anonymous access was allowed to the site [see V-1120], also review access using "anonymous".) (331 Password required) Password: "Password" (Substituting [Password] with password for the account attempting access.) (230 User ftpuser logged in.) ftp> "Dir" If the FTP session indicates access to areas of the system other than the specific folder for FTP data, such as the root of the drive, Program Files or Windows directories, this is a finding.

Fix: F-27948r476619_fix

Configure the system to only allow FTP access to specific folders containing the data to be available through the service.

b

Windows 2012 / 2012 R2 must automatically remove or disable temporary user accounts after 72 hours.

AC-2 - Medium - CCI-000016 - V-226259 - SV-226259r794508_rule

RMF Control

AC-2

Severity

M

CCI

CCI-000016

Version

WN12-GE-000056

Vuln IDs

V-226259
V-57653

Rule IDs

SV-226259r794508_rule
SV-72063

If temporary user accounts remain active when no longer needed or for an excessive period, these accounts may be used to gain unauthorized access. To mitigate this risk, automated termination of all temporary accounts must be set upon account creation. Temporary accounts are established as part of normal account activation procedures when there is a need for short-term accounts without the demand for immediacy in account activation. If temporary accounts are used, the operating system must be configured to automatically terminate these types of accounts after a DoD-defined time period of 72 hours. To address access requirements, many operating systems may be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.

Checks: C-27961r476621_chk

Determine if temporary user accounts are used and identify any that exist. If none exist, this is NA. Review temporary user accounts for expiration dates. Open "PowerShell". Domain Controllers: Enter "Search-ADAccount -AccountExpiring -TimeSpan 3:00:00:00 | FT Name, AccountExpirationDate" This will return any accounts configured to expire within the next 3 days. (The "TimeSpan" value to can be changed to find accounts configured to expire at various times such as 30 for the next month.) If any accounts identified as temporary are not listed, this is a finding. For any temporary accounts returned by the previous query: Enter "Get-ADUser -Identity [Name] -Property WhenCreated" to determine when the account was created. If the "WhenCreated" date and "AccountExpirationDate" from the previous query are greater than 3 days apart, this is a finding. Member servers and standalone systems: Enter "Net User [username]", where [username] is the name of the temporary user account. If "Account expires" has not been defined within 72 hours for any temporary user account, this is a finding. If the "Password last set" date and "Account expires" date are greater than 72 hours apart, this is a finding. (Net User does not provide an account creation date.)

Fix: F-27949r476622_fix

Configure temporary user accounts to automatically expire within 72 hours. Domain account can be configured with an account expiration date, under "Account" properties. Local accounts can be configured to expire with the command "Net user [username] /expires:[mm/dd/yyyy]", where username is the name of the temporary user account. Delete any temporary user accounts that are no longer necessary.

b

Windows 2012 / 2012 R2 must automatically remove or disable emergency accounts after the crisis is resolved or within 72 hours.

AC-2 - Medium - CCI-001682 - V-226260 - SV-226260r794541_rule

RMF Control

AC-2

Severity

M

CCI

CCI-001682

Version

WN12-GE-000057

Vuln IDs

V-226260
V-57655

Rule IDs

SV-226260r794541_rule
SV-72065

Emergency administrator accounts are privileged accounts which are established in response to crisis situations where the need for rapid account activation is required. Therefore, emergency account activation may bypass normal account authorization processes. If these accounts are automatically disabled, system maintenance during emergencies may not be possible, thus adversely affecting system availability. Emergency administrator accounts are different from infrequently used accounts (i.e., local logon accounts used by system administrators when network or normal logon/access is not available). Infrequently used accounts are not subject to automatic termination dates. Emergency accounts are accounts created in response to crisis situations, usually for use by maintenance personnel. The automatic expiration or disabling time period may be extended as needed until the crisis is resolved; however, it must not be extended indefinitely. A permanent account should be established for privileged users who need long-term maintenance accounts. To address access requirements, many operating systems can be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.

Checks: C-27962r476624_chk

Determine if emergency administrator accounts are used and identify any that exist. If none exist, this is NA. If emergency administrator accounts cannot be configured with an expiration date due to an ongoing crisis, the accounts must be disabled or removed when the crisis is resolved. If emergency administrator accounts have not been configured with an expiration date or have not been disabled or removed following the resolution of a crisis, this is a finding. Domain Controllers: Enter "Search-ADAccount -AccountExpiring -TimeSpan 3:00:00:00 | FT Name, AccountExpirationDate" This will return any accounts configured to expire within the next 3 days. (The "TimeSpan" value to can be changed to find accounts configured to expire at various times such as 30 for the next month.) If any accounts identified as emergency administrator accounts are not listed, this is a finding. For any emergency administrator accounts returned by the previous query: Enter "Get-ADUser -Identity [Name] -Property WhenCreated" to determine when the account was created. If the "WhenCreated" date and "AccountExpirationDate" from the previous query are greater than 3 days apart, this is a finding. Member servers and standalone systems: Enter "Net User [username]", where [username] is the name of the emergency administrator accounts. If "Account expires" has not been defined within 72 hours for any emergency administrator accounts, this is a finding. If the "Password last set" date and "Account expires" date are greater than 72 hours apart, this is a finding. (Net User does not provide an account creation date.)

Fix: F-27950r476625_fix

Remove emergency administrator accounts after a crisis has been resolved or configure the accounts to automatically expire within 72 hours. Domain accounts can be configured with an account expiration date, under "Account" properties. Local accounts can be configured to expire with the command "Net user [username] /expires:[mm/dd/yyyy]", where username is the name of the emergency administrator account.

b

The DoD Root CA certificates must be installed in the Trusted Root Store.

IA-5 - Medium - CCI-000185 - V-226261 - SV-226261r819682_rule

RMF Control

IA-5

Severity

M

CCI

Version

WN12-PK-000001

Vuln IDs

V-226261
V-32272

Rule IDs

SV-226261r819682_rule
SV-52961

To ensure secure DoD websites and DoD-signed code are properly validated, the system must trust the DoD Root Certificate Authorities (CAs). The DoD root certificates will ensure that the trust chain is established for server certificates issued from the DoD CAs.

Checks: C-27963r819680_chk

Verify the DoD Root CA certificates are installed as Trusted Root Certification Authorities. The certificates and thumbprints referenced below apply to unclassified systems; see PKE documentation for other networks. Run "PowerShell" as an administrator. Execute the following command: Get-ChildItem -Path Cert:Localmachine\root | Where Subject -Like "*DoD*" | FL Subject, Thumbprint, NotAfter If the following certificate "Subject" and "Thumbprint" information is not displayed, this is a finding. Subject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US Thumbprint: D73CA91102A2204A36459ED32213B467D7CE97FB NotAfter: 12/30/2029 Subject: CN=DoD Root CA 4, OU=PKI, OU=DoD, O=U.S. Government, C=US Thumbprint: B8269F25DBD937ECAFD4C35A9838571723F2D026 NotAfter: 7/25/2032 Subject: CN=DoD Root CA 5, OU=PKI, OU=DoD, O=U.S. Government, C=US Thumbprint: 4ECB5CC3095670454DA1CBD410FC921F46B8564B NotAfter: 6/14/2041 Alternately, use the Certificates MMC snap-in: Run "MMC". Select "File", "Add/Remove Snap-in". Select "Certificates", click "Add". Select "Computer account", click "Next". Select "Local computer: (the computer this console is running on)", click "Finish". Click "OK". Expand "Certificates" and navigate to "Trusted Root Certification Authorities >> Certificates". For each of the DoD Root CA certificates noted below: Right-click on the certificate and select "Open". Select the "Details" tab. Scroll to the bottom and select "Thumbprint". If the DoD Root CA certificates below are not listed or the value for the "Thumbprint" field is not as noted, this is a finding. DoD Root CA 3 Thumbprint: D73CA91102A2204A36459ED32213B467D7CE97FB Valid to: Sunday, December 30, 2029 DoD Root CA 4 Thumbprint: B8269F25DBD937ECAFD4C35A9838571723F2D026 Valid to: Sunday, July 25, 2032 DoD Root CA 5 Thumbprint: 4ECB5CC3095670454DA1CBD410FC921F46B8564B Valid to: Friday, June 14, 2041

Fix: F-27951r819681_fix

Install the DoD Root CA certificates: DoD Root CA 3 DoD Root CA 4 DoD Root CA 5 The InstallRoot tool is available on Cyber Exchange at https://cyber.mil/pki-pke/tools-configuration-files.

b

The DoD Interoperability Root CA cross-certificates must be installed into the Untrusted Certificates Store on unclassified systems.

IA-5 - Medium - CCI-000185 - V-226262 - SV-226262r819685_rule

RMF Control

IA-5

Severity

M

CCI

Version

WN12-PK-000003

Vuln IDs

V-226262
V-32274

Rule IDs

SV-226262r819685_rule
SV-52957

To ensure users do not experience denial of service when performing certificate-based authentication to DoD websites due to the system chaining to a root other than DoD Root CAs, the DoD Interoperability Root CA cross-certificates must be installed in the Untrusted Certificate Store. This requirement only applies to unclassified systems.

Checks: C-27964r819683_chk

Verify the DoD Interoperability cross-certificates are installed on unclassified systems as Untrusted Certificates. Run "PowerShell" as an administrator. Execute the following command: Get-ChildItem -Path Cert:Localmachine\disallowed | Where {$_.Issuer -Like "*DoD Interoperability*" -and $_.Subject -Like "*DoD*"} | FL Subject, Issuer, Thumbprint, NotAfter If the following certificate "Subject", "Issuer", and "Thumbprint" information is not displayed, this is a finding. Subject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US Issuer: CN=DoD Interoperability Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US Thumbprint: AC06108CA348CC03B53795C64BF84403C1DBD341 NotAfter: 1/22/2022 10:22:56 AM Subject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US Issuer: CN=DoD Interoperability Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US Thumbprint: 49CBE933151872E17C8EAE7F0ABA97FB610F6477 NotAfter: 11/16/2024 9:57:16 AM Alternately, use the Certificates MMC snap-in: Run "MMC". Select "File", "Add/Remove Snap-in". Select "Certificates", click "Add". Select "Computer account", click "Next". Select "Local computer: (the computer this console is running on)", click "Finish". Click "OK". Expand "Certificates" and navigate to "Untrusted Certificates >> Certificates". For each certificate with "DoD Root CA…" under "Issued To" and "DoD Interoperability Root CA…" under "Issued By": Right-click on the certificate and select "Open". Select the "Details" tab. Scroll to the bottom and select "Thumbprint". If the certificates below are not listed or the value for the "Thumbprint" field is not as noted, this is a finding. Issued To: DoD Root CA 3 Issued By: DoD Interoperability Root CA 2 Thumbprint: A8C27332CCB4CA49554CE55D34062A7DD2850C02 Valid to: Friday, August 26, 2022 Issued To: DoD Root CA 3 Issued By: DoD Interoperability Root CA 2 Thumbprint: 49CBE933151872E17C8EAE7F0ABA97FB610F6477 Valid to: Wednesday, November 16, 2024

Fix: F-27952r819684_fix

Install the DoD Interoperability Root CA cross-certificates on unclassified systems. Issued To - Issued By - Thumbprint DoD Root CA 3 - DoD Interoperability Root CA 2 - 49CBE933151872E17C8EAE7F0ABA97FB610F6477 DoD Root CA 3 - DoD Interoperability Root CA 2 - AC06108CA348CC03B53795C64BF84403C1DBD341 The certificates can be installed using the InstallRoot tool. The tool and user guide are available on Cyber Exchange at https://cyber.mil/pki-pke/tools-configuration-files.

b

The US DoD CCEB Interoperability Root CA cross-certificates must be installed into the Untrusted Certificates Store on unclassified systems.

IA-5 - Medium - CCI-000185 - V-226263 - SV-226263r794522_rule

RMF Control

IA-5

Severity

M

CCI

Version

WN12-PK-000004

Vuln IDs

V-226263
V-40237

Rule IDs

SV-226263r794522_rule
SV-52196

To ensure users do not experience denial of service when performing certificate-based authentication to DoD websites due to the system chaining to a root other than DoD Root CAs, the US DoD CCEB Interoperability Root CA cross-certificates must be installed in the Untrusted Certificate Store. This requirement only applies to unclassified systems.

Checks: C-27965r794520_chk

Verify the US DoD CCEB Interoperability Root CA cross-certificate is installed on unclassified systems as an Untrusted Certificate. Run "PowerShell" as an administrator. Execute the following command: Get-ChildItem -Path Cert:Localmachine\disallowed | Where Issuer -Like "*CCEB Interoperability*" | FL Subject, Issuer, Thumbprint, NotAfter If the following certificate "Subject", "Issuer", and "Thumbprint", information is not displayed, this is a finding. Subject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US Issuer: CN=US DoD CCEB Interoperability Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US Thumbprint: AF132AC65DE86FC4FB3FE51FD637EBA0FF0B12A9 NotAfter: 8/26/2022 Alternately use the Certificates MMC snap-in: Run "MMC". Select "File", "Add/Remove Snap-in". Select "Certificates", click "Add". Select "Computer account", click "Next". Select "Local computer: (the computer this console is running on)", click "Finish". Click "OK". Expand "Certificates" and navigate to "Untrusted Certificates >> Certificates". For each certificate with "US DoD CCEB Interoperability Root CA …" under "Issued By": Right-click on the certificate and select "Open". Select the "Details" Tab. Scroll to the bottom and select "Thumbprint". If the certificate below is not listed or the value for the "Thumbprint" field is not as noted, this is a finding. Issued To: DoD Root CA 3 Issuer by: US DoD CCEB Interoperability Root CA 2 Thumbprint: AF132AC65DE86FC4FB3FE51FD637EBA0FF0B12A9 Valid: Friday, August 26, 2022

Fix: F-27953r794521_fix

Install the US DoD CCEB Interoperability Root CA cross-certificate on unclassified systems. Issued To - Issued By - Thumbprint DoD Root CA 3 - US DoD CCEB Interoperability Root CA 2 - AF132AC65DE86FC4FB3FE51FD637EBA0FF0B12A9 The certificates can be installed using the InstallRoot tool. The tool and user guide are available on Cyber Exchange at https://cyber.mil/pki-pke/tools-configuration-files.

b

Domain controllers must have a PKI server certificate.

IA-5 - Medium - CCI-000185 - V-226264 - SV-226264r794523_rule

RMF Control

IA-5

Severity

M

CCI

Version

WN12-PK-000005-DC

Vuln IDs

V-226264
V-39334

Rule IDs

SV-226264r794523_rule
SV-51189

Domain controller must have a server certificate to establish authenticity as part of PKI authentications in the domain.

Checks: C-27966r476636_chk

Verify the domain controller has a PKI server certificate. Run "mmc". Select "Add/Remove Snap-in" from the File menu. Select "Certificates" in the left pane and click the "Add >" button. Select "Computer Account", click "Next". Select the appropriate option for "Select the computer you want this snap-in to manage.", click "Finish". Click "OK". Select and expand the Certificates (Local Computer) entry in the left pane. Select and expand the Personal entry in the left pane. Select the Certificates entry in the left pane. If no certificate for the domain controller exists in the right pane, this is a finding.

Fix: F-27954r476637_fix

Obtain a server certificate for the domain controller.

c

Domain Controller PKI certificates must be issued by the DoD PKI or an approved External Certificate Authority (ECA).

IA-5 - High - CCI-000185 - V-226265 - SV-226265r794525_rule

RMF Control

IA-5

Severity

H

CCI

Version

WN12-PK-000006-DC

Vuln IDs

V-226265
V-14820

Rule IDs

SV-226265r794525_rule
SV-51190

A PKI implementation depends on the practices established by the Certificate Authority (CA) to ensure the implementation is secure. Without proper practices, the certificates issued by a CA have limited value in authentication functions. The use of multiple CAs from separate PKI implementations results in interoperability issues. If servers and clients do not have a common set of root CA certificates, they are not able to authenticate each other.

Checks: C-27967r476639_chk

Verify the source of the domain controller's server certificate. Run "mmc". Select "Add/Remove Snap-in" from the File menu. Select "Certificates" in the left pane and click the "Add >" button. Select "Computer Account", click "Next". Select the appropriate option for "Select the computer you want this snap-in to manage.", click "Finish". Click "OK". Select and expand the Certificates (Local Computer) entry in the left pane. Select and expand the Personal entry in the left pane. Select the Certificates entry in the left pane. In the right pane, examine the Issued By field for the certificate to determine the issuing CA. If the Issued By field of the PKI certificate being used by the domain controller does not indicate the issuing Certificate Authority (CA) is part of the DoD PKI or an approved ECA, this is a finding. There are multiple sources from which lists of valid DoD CAs and approved ECAs can be obtained: The Global Directory Service (GDS) website provides an online source. The address for this site is https://crl.gds.disa.mil. DoD Public Key Enablement (PKE) Engineering Support maintains the InstallRoot utility to manage DoD supported root certificates on Windows computers which includes a list of authorized CAs. The utility package can be downloaded from the PKI and PKE Tools page on IASE. http://iase.disa.mil/pki-pke/function_pages/tools.html

Fix: F-27955r794524_fix

Obtain PKI certificates issued by the DoD PKI or an approved External Certificate Authority (ECA). Severity Override Guidance: If the certificates in use are issued by a CA authorized by the Component's CIO, this is a CAT II finding. IA Controls: IAKM-1, IAKM-2, IATS-1, IATS-2

c

PKI certificates associated with user accounts must be issued by the DoD PKI or an approved External Certificate Authority (ECA).

IA-5 - High - CCI-000185 - V-226266 - SV-226266r794526_rule

RMF Control

IA-5

Severity

H

CCI

Version

WN12-PK-000007-DC

Vuln IDs

V-226266
V-26683

Rule IDs

SV-226266r794526_rule
SV-51191

A PKI implementation depends on the practices established by the Certificate Authority (CA) to ensure the implementation is secure. Without proper practices, the certificates issued by a CA have limited value in authentication functions.

Checks: C-27968r476642_chk

Open "PowerShell" as Administrator. Enter "Get-ADUser -Filter * | FT Name, UserPrincipalName, Enabled -AutoSize". Review the User Principal Name (UPN) of user accounts, including administrators. Exclude the built-in accounts such as Administrator and Guest. If the User Principal Name (UPN) is not in the format of an individual's identifier for the certificate type and for the appropriate domain suffix, this is a finding. For standard NIPRNET certificates the individual's identifier is in the format of an Electronic Data Interchange - Personnel Identifier (EDI-PI). Alt Tokens and other certificates may use a different UPN format than the EDI-PI, which vary by organization. Verify these with the organization. NIPRNET Example: Name - User Principal Name User1 - 1234567890@mil See PKE documentation for other network domain suffixes. If the mappings are to certificates issued by a CA authorized by the Component's CIO, this is a CAT II finding.

Fix: F-27956r476643_fix

Map user accounts to PKI certificates using the appropriate User Principal Name (UPN) for the network. See PKE documentation for details.

b

Active directory user accounts, including administrators, must be configured to require the use of a Common Access Card (CAC), PIV-compliant hardware token, or Alternate Logon Token (ALT) for user authentication.

IA-2 - Medium - CCI-000765 - V-226267 - SV-226267r794536_rule

RMF Control

IA-2

Severity

M

CCI

CCI-000765

Version

WN12-PK-000008-DC

Vuln IDs

V-226267
V-15488

Rule IDs

SV-226267r794536_rule
SV-51192

Smart cards such as the Common Access Card (CAC) support a two-factor authentication technique. This provides a higher level of trust in the asserted identity than use of the username and password for authentication.

Checks: C-27969r476645_chk

Verify active directory user accounts, including administrators, have "Smart card is required for interactive logon" selected. Run "PowerShell". Enter the following: "Get-ADUser -Filter {(Enabled -eq $True) -and (SmartcardLogonRequired -eq $False)} | FT Name" ("DistinguishedName" may be substituted for "Name" for more detailed output.) If any user accounts are listed, this is a finding. Alternately: To view sample accounts in "Active Directory Users and Computers" (Available from various menus or run "dsa.msc"): Select the Organizational Unit (OU) where the User accounts are located. (By default this is the Users node; however, accounts may be under other organization-defined OUs.) Right click the sample User account and select "Properties". Select the "Account" tab. If any User accounts do not have "Smart card is required for interactive logon" checked in the "Account Options" area, this is a finding.

Fix: F-27957r476646_fix

Configure all user accounts, including administrator accounts, in Active Directory to enable the option "Smart card is required for interactive logon". Run "Active Directory Users and Computers" (Available from various menus or run "dsa.msc"): Select the Organizational Unit (OU) where the user accounts are located. (By default this is the Users node; however, accounts may be under other organization-defined OUs.) Right click the user account and select "Properties". Select the "Account" tab. Check "Smart card is required for interactive logon" in the "Account Options" area.

c

Standard user accounts must only have Read permissions to the Winlogon registry key.

AC-6 - High - CCI-002235 - V-226268 - SV-226268r794557_rule

RMF Control

AC-6

Severity

H

CCI

Version

WN12-RG-000001

Vuln IDs

V-226268
V-26070

Rule IDs

SV-226268r794557_rule
SV-53123

Permissions on the Winlogon registry key must only allow privileged accounts to change registry values. If standard users have these permissions, there is a potential for programs to run with elevated privileges when a privileged user logs on to the system.

Checks: C-27970r476648_chk

Run "Regedit". Navigate to the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\ Right-click on "WinLogon" and select "Permissions…". Select "Advanced". If the permissions are not as restrictive as the defaults listed below, this is a finding. The following are the same for each permission listed: Type - Allow Inherited from - MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion Applies to - This key and subkeys Columns: Principal - Access TrustedInstaller - Full Control SYSTEM - Full Control Administrators - Full Control Users - Read ALL APPLICATION PACKAGES - Read

Fix: F-27958r476649_fix

Maintain permissions at least as restrictive as the defaults listed below for the "WinLogon" registry key. It is recommended to not change the permissions from the defaults. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\ The following are the same for each permission listed: Type - Allow Inherited from - MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion Applies to - This key and subkeys Columns: Principal - Access TrustedInstaller - Full Control SYSTEM - Full Control Administrators - Full Control Users - Read ALL APPLICATION PACKAGES - Read

c

Standard user accounts must only have Read permissions to the Active Setup\Installed Components registry key.

AC-6 - High - CCI-002235 - V-226269 - SV-226269r794558_rule

RMF Control

AC-6

Severity

H

CCI

Version

WN12-RG-000002

Vuln IDs

V-226269
V-32282

Rule IDs

SV-226269r794558_rule
SV-52956

Permissions on the Active Setup\Installed Components registry key must only allow privileged accounts to add or change registry values. If standard user accounts have these permissions, there is a potential for programs to run with elevated privileges when a privileged user logs on to the system.

Checks: C-27971r476651_chk

Run "Regedit". Navigate to the following registry keys and review the permissions: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\ HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Active Setup\Installed Components\ (64-bit systems) If the default permissions listed below have been changed, this is a finding. Users - Read Administrators - Full Control SYSTEM - Full Control CREATOR OWNER - Full Control (Subkeys only) ALL APPLICATION PACKAGES - Read

Fix: F-27959r476652_fix

Maintain the default permissions of the following registry keys: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\ HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Active Setup\Installed Components\ (64-bit systems only) Users - Read Administrators - Full Control SYSTEM - Full Control CREATOR OWNER - Full Control (Subkeys only) ALL APPLICATION PACKAGES - Read

c

Anonymous access to the registry must be restricted.

AC-6 - High - CCI-002235 - V-226270 - SV-226270r794559_rule

RMF Control

AC-6

Severity

H

CCI

Version

WN12-RG-000004

Vuln IDs

V-226270
V-1152

Rule IDs

SV-226270r794559_rule
SV-52864

The registry is integral to the function, security, and stability of the Windows system. Some processes may require anonymous access to the registry. This must be limited to properly protect the system.

Checks: C-27972r476654_chk

Run "Regedit". Navigate to the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg\ If the key does not exist, this is a finding. Right-click on "winreg" and select "Permissions…". Select "Advanced". If the permissions are not as restrictive as the defaults listed below, this is a finding. The following are the same for each permission listed: Type - Allow Inherited from - None Columns: Principal - Access - Applies to Administrators - Full Control - This key and subkeys Backup Operators - Read - This key only LOCAL SERVICE - Read - This key and subkeys

Fix: F-27960r476655_fix

Maintain permissions at least as restrictive as the defaults listed below for the "winreg" registry key. It is recommended to not change the permissions from the defaults. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg\ The following are the same for each permission listed: Type - Allow Inherited from - None Columns: Principal - Access - Applies to Administrators - Full Control - This key and subkeys Backup Operators - Read - This key only LOCAL SERVICE - Read - This key and subkeys

b

The built-in guest account must be disabled.

IA-8 - Medium - CCI-000804 - V-226271 - SV-226271r794540_rule

RMF Control

IA-8

Severity

M

CCI

CCI-000804

Version

WN12-SO-000003

Vuln IDs

V-226271
V-1113

Rule IDs

SV-226271r794540_rule
SV-52855

A system faces an increased vulnerability threat if the built-in guest account is not disabled. This account is a known account that exists on all Windows systems and cannot be deleted. This account is initialized during the installation of the operating system with no password assigned.

Checks: C-27973r476657_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options. If the value for "Accounts: Guest account status" is not set to "Disabled", this is a finding.

Fix: F-27961r476658_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Accounts: Guest account status" to "Disabled".

c

Local accounts with blank passwords must be restricted to prevent access from the network.

CM-6 - High - CCI-000366 - V-226272 - SV-226272r794580_rule

RMF Control

CM-6

Severity

H

CCI

Version

WN12-SO-000004

Vuln IDs

V-226272
V-3344

Rule IDs

SV-226272r794580_rule
SV-52886

An account without a password can allow unauthorized access to a system as only the username would be required. Password policies should prevent accounts with blank passwords from existing on a system. However, if a local account with a blank password did exist, enabling this setting will prevent network access, limiting the account to local console logon only.

Checks: C-27974r476660_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: \System\CurrentControlSet\Control\Lsa\ Value Name: LimitBlankPasswordUse Value Type: REG_DWORD Value: 1

Fix: F-27962r476661_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Accounts: Limit local account use of blank passwords to console logon only" to "Enabled".

b

The built-in administrator account must be renamed.

CM-6 - Medium - CCI-000366 - V-226273 - SV-226273r794581_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-SO-000005

Vuln IDs

V-226273
V-1115

Rule IDs

SV-226273r794581_rule
SV-52857

The built-in administrator account is a well-known account subject to attack. Renaming this account to an unidentified name improves the protection of this account and the system.

Checks: C-27975r476663_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options. If the value for "Accounts: Rename administrator account" is not set to a value other than "Administrator", this is a finding.

Fix: F-27963r476664_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Accounts: Rename administrator account" to a name other than "Administrator".

b

The built-in guest account must be renamed.

CM-6 - Medium - CCI-000366 - V-226274 - SV-226274r794582_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-SO-000006

Vuln IDs

V-226274
V-1114

Rule IDs

SV-226274r794582_rule
SV-52856

The built-in guest account is a well-known user account on all Windows systems and, as initially installed, does not require a password. This can allow access to system resources by unauthorized users. Renaming this account to an unidentified name improves the protection of this account and the system.

Checks: C-27976r476666_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options. If the value for "Accounts: Rename guest account" is not set to a value other than "Guest", this is a finding.

Fix: F-27964r476667_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Accounts: Rename guest account" to a name other than "Guest".

b

Auditing the Access of Global System Objects must be turned off.

SC-5 - Medium - CCI-001095 - V-226275 - SV-226275r794551_rule

RMF Control

SC-5

Severity

M

CCI

CCI-001095

Version

WN12-SO-000007

Vuln IDs

V-226275
V-14228

Rule IDs

SV-226275r794551_rule
SV-53129

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. This setting prevents the system from setting up a default system access control list for certain system objects, which could create a very large number of security events, filling the security log in Windows and making it difficult to identify actual issues.

Checks: C-27977r476669_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: \System\CurrentControlSet\Control\Lsa\ Value Name: AuditBaseObjects Value Type: REG_DWORD Value: 0

Fix: F-27965r476670_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Audit: Audit the access of global system objects" to "Disabled".

b

Auditing of Backup and Restore Privileges must be turned off.

SC-5 - Medium - CCI-001095 - V-226276 - SV-226276r794552_rule

RMF Control

SC-5

Severity

M

CCI

CCI-001095

Version

WN12-SO-000008

Vuln IDs

V-226276
V-14229

Rule IDs

SV-226276r794552_rule
SV-52943

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. This setting prevents the system from generating audit events for every file backed up or restored, which could fill the security log in Windows, making it difficult to identify actual issues.

Checks: C-27978r476672_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: \System\CurrentControlSet\Control\Lsa\ Value Name: FullPrivilegeAuditing Value Type: REG_BINARY Value: 00

Fix: F-27966r476673_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Audit: Audit the use of Backup and Restore privilege" to "Disabled".

b

Audit policy using subcategories must be enabled.

AU-12 - Medium - CCI-000169 - V-226277 - SV-226277r794513_rule

RMF Control

AU-12

Severity

M

CCI

CCI-000169

Version

WN12-SO-000009

Vuln IDs

V-226277
V-14230

Rule IDs

SV-226277r794513_rule
SV-52944

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. This setting allows administrators to enable more precise auditing capabilities.

Checks: C-27979r476675_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: \System\CurrentControlSet\Control\Lsa\ Value Name: SCENoApplyLegacyAuditPolicy Value Type: REG_DWORD Value: 1

Fix: F-27967r476676_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" to "Enabled".

b

Ejection of removable NTFS media must be restricted to Administrators.

CM-6 - Medium - CCI-000366 - V-226278 - SV-226278r794583_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-SO-000011

Vuln IDs

V-226278
V-1171

Rule IDs

SV-226278r794583_rule
SV-52875

Removable hard drives, if they are not properly configured, can be formatted and ejected by users who are not members of the Administrators Group. Formatting and ejecting removable NTFS media must only be done by administrators.

Checks: C-27980r476678_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\Microsoft\Windows NT\CurrentVersion\Winlogon\ Value Name: AllocateDASD Value Type: REG_SZ Value: 0

Fix: F-27968r476679_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".

b

Outgoing secure channel traffic must be encrypted or signed.

SC-8 - Medium - CCI-002418 - V-226279 - SV-226279r794566_rule

RMF Control

SC-8

Severity

M

CCI

Version

WN12-SO-000012

Vuln IDs

V-226279
V-6831

Rule IDs

SV-226279r794566_rule
SV-52934

Requests sent on the secure channel are authenticated, and sensitive information (such as passwords) is encrypted, but not all information is encrypted. If this policy is enabled, outgoing secure channel traffic will be encrypted and signed.

Checks: C-27981r476681_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: \System\CurrentControlSet\Services\Netlogon\Parameters\ Value Name: RequireSignOrSeal Value Type: REG_DWORD Value: 1

Fix: F-27969r476682_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".

b

Outgoing secure channel traffic must be encrypted when possible.

SC-8 - Medium - CCI-002418 - V-226280 - SV-226280r794567_rule

RMF Control

SC-8

Severity

M

CCI

Version

WN12-SO-000013

Vuln IDs

V-226280
V-1163

Rule IDs

SV-226280r794567_rule
SV-52871

Requests sent on the secure channel are authenticated, and sensitive information (such as passwords) is encrypted, but not all information is encrypted. If this policy is enabled, outgoing secure channel traffic will be encrypted.

Checks: C-27982r476684_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: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ Value Name: SealSecureChannel Value Type: REG_DWORD Value: 1 If the value for "Domain Member: Digitally encrypt or sign secure channel data (always)" is set to "Enabled", this can be NA (see V-6831).

Fix: F-27970r476685_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".

b

Outgoing secure channel traffic must be signed when possible.

SC-8 - Medium - CCI-002418 - V-226281 - SV-226281r794568_rule

RMF Control

SC-8

Severity

M

CCI

Version

WN12-SO-000014

Vuln IDs

V-226281
V-1164

Rule IDs

SV-226281r794568_rule
SV-52872

Requests sent on the secure channel are authenticated, and sensitive information (such as passwords) is encrypted, but the channel is not integrity checked. If this policy is enabled, outgoing secure channel traffic will be signed.

Checks: C-27983r476687_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: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ Value Name: SignSecureChannel Value Type: REG_DWORD Value: 1 If the value for "Domain Member: Digitally encrypt or sign secure channel data (always)" is set to "Enabled", this can be NA (see V-6831).

Fix: F-27971r476688_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".

a

The computer account password must not be prevented from being reset.

CM-6 - Low - CCI-000366 - V-226282 - SV-226282r794584_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN12-SO-000015

Vuln IDs

V-226282
V-1165

Rule IDs

SV-226282r794584_rule
SV-52873

Computer account passwords are changed automatically on a regular basis. Disabling automatic password changes can make the system more vulnerable to malicious access. Frequent password changes can be a significant safeguard for your system. A new password for the computer account will be generated every 30 days.

Checks: C-27984r476690_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: \System\CurrentControlSet\Services\Netlogon\Parameters\ Value Name: DisablePasswordChange Value Type: REG_DWORD Value: 0

Fix: F-27972r476691_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Domain member: Disable machine account password changes" to "Disabled".

a

The maximum age for machine account passwords must be set to requirements.

CM-6 - Low - CCI-000366 - V-226283 - SV-226283r794585_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN12-SO-000016

Vuln IDs

V-226283
V-3373

Rule IDs

SV-226283r794585_rule
SV-52887

Computer account passwords are changed automatically on a regular basis. This setting controls the maximum password age that a machine account may have. This setting must be set to no more than 30 days, ensuring the machine changes its password monthly.

Checks: C-27985r476693_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: \System\CurrentControlSet\Services\Netlogon\Parameters\ Value Name: MaximumPasswordAge Value Type: REG_DWORD Value: 30 (or less, but not 0)

Fix: F-27973r476694_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Domain member: Maximum machine account password age" to "30" or less (excluding "0" which is unacceptable).

b

The system must be configured to require a strong session key.

SC-8 - Medium - CCI-002418 - V-226284 - SV-226284r794569_rule

RMF Control

SC-8

Severity

M

CCI

Version

WN12-SO-000017

Vuln IDs

V-226284
V-3374

Rule IDs

SV-226284r794569_rule
SV-52888

A computer connecting to a domain controller will establish a secure channel. Requiring strong session keys enforces 128-bit encryption between systems.

Checks: C-27986r476696_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: \System\CurrentControlSet\Services\Netlogon\Parameters\ Value Name: RequireStrongKey Value Type: REG_DWORD Value: 1 This setting may prevent a system from being joined to a domain if not configured consistently between systems.

Fix: F-27974r476697_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".

a

The system must be configured to prevent the display of the last username on the logon screen.

CM-6 - Low - CCI-000366 - V-226285 - SV-226285r794586_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN12-SO-000018

Vuln IDs

V-226285
V-11806

Rule IDs

SV-226285r794586_rule
SV-52941

Displaying the username of the last logged on user provides half of the userid/password equation that an unauthorized person would need to gain access. The username of the last user to log on to a system must not be displayed.

Checks: C-27987r476699_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\Microsoft\Windows\CurrentVersion\Policies\System\ Value Name: DontDisplayLastUserName Value Type: REG_DWORD Value: 1

Fix: F-27975r476700_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Interactive logon: Do not display last user name" to "Enabled".

b

The Ctrl+Alt+Del security attention sequence for logons must be enabled.

CM-6 - Medium - CCI-000366 - V-226286 - SV-226286r794587_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-SO-000019

Vuln IDs

V-226286
V-1154

Rule IDs

SV-226286r794587_rule
SV-52866

Disabling the Ctrl+Alt+Del security attention sequence can compromise system security. Because only Windows responds to the Ctrl+Alt+Del security sequence, a user can be assured that any passwords entered following that sequence are sent only to Windows. If the sequence requirement is eliminated, malicious programs can request and receive a user's Windows password. Disabling this sequence also suppresses a custom logon banner.

Checks: C-27988r476702_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\Microsoft\Windows\CurrentVersion\Policies\System\ Value Name: DisableCAD Value Type: REG_DWORD Value: 0

Fix: F-27976r476703_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".

b

The machine inactivity limit must be set to 15 minutes, locking the system with the screensaver.

AC-11 - Medium - CCI-000057 - V-226287 - SV-226287r794511_rule

RMF Control

AC-11

Severity

M

CCI

CCI-000057

Version

WN12-SO-000021

Vuln IDs

V-226287
V-36773

Rule IDs

SV-226287r794511_rule
SV-51596

Unattended systems are susceptible to unauthorized use and should be locked when unattended. The screen saver should be set at a maximum of 15 minutes and be password protected. This protects critical and sensitive data from exposure to unauthorized personnel with physical access to the computer.

Checks: C-27989r476705_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\Microsoft\Windows\CurrentVersion\Policies\System\ Value Name: InactivityTimeoutSecs Value Type: REG_DWORD Value: 0x00000384 (900) (or less, excluding "0" which is effectively disabled)

Fix: F-27977r476706_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Interactive logon: Machine inactivity limit" to "900" seconds" or less, excluding "0" which is effectively disabled.

b

The required legal notice must be configured to display before console logon.

AC-8 - Medium - CCI-000048 - V-226288 - SV-226288r794509_rule

RMF Control

AC-8

Severity

M

CCI

CCI-000048

Version

WN12-SO-000022

Vuln IDs

V-226288
V-1089

Rule IDs

SV-226288r794509_rule
SV-52845

Failure to display the logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources.

Checks: C-27990r476708_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\Microsoft\Windows\CurrentVersion\Policies\System\ Value Name: LegalNoticeText Value Type: REG_SZ Value: See message text below 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.

Fix: F-27978r476709_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" to the following: 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.

a

The Windows dialog box title for the legal banner must be configured.

AC-8 - Low - CCI-000048 - V-226289 - SV-226289r794510_rule

RMF Control

AC-8

Severity

L

CCI

CCI-000048

Version

WN12-SO-000023

Vuln IDs

V-226289
V-26359

Rule IDs

SV-226289r794510_rule
SV-53121

Failure to display the logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources.

Checks: C-27991r476711_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\Microsoft\Windows\CurrentVersion\Policies\System\ Value Name: LegalNoticeCaption Value Type: REG_SZ Value: See message title options below "DoD Notice and Consent Banner", "US Department of Defense Warning Statement", or a site-defined equivalent. If a site-defined title is used, it can in no case contravene or modify the language of the banner text required in V-1089. Automated tools may only search for the titles defined above. If a site-defined title is used, a manual review will be required.

Fix: F-27979r476712_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Interactive Logon: Message title for users attempting to log on" to "DoD Notice and Consent Banner", "US Department of Defense Warning Statement", or a site-defined equivalent. If a site-defined title is used, it can in no case contravene or modify the language of the banner text required in V-1089.

a

Caching of logon credentials must be limited.

CM-6 - Low - CCI-000366 - V-226290 - SV-226290r794588_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN12-SO-000024

Vuln IDs

V-226290
V-1090

Rule IDs

SV-226290r794588_rule
SV-52846

The default Windows configuration caches the last logon credentials for users who log on interactively to a system. This feature is provided for system availability reasons, such as the user's machine being disconnected from the network or domain controllers being unavailable. Even though the credential cache is well-protected, if a system is attacked, an unauthorized individual may isolate the password to a domain user account using a password-cracking program and gain access to the domain.

Checks: C-27992r476714_chk

If the system is not a member of a domain, this is NA. 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\Microsoft\Windows NT\CurrentVersion\Winlogon\ Value Name: CachedLogonsCount Value Type: REG_SZ Value: 4 (or less)

Fix: F-27980r476715_fix

If the system is not a member of a domain, this is NA. Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Interactive Logon: Number of previous logons to cache (in case Domain Controller is not available)" to "4" logons or less.

a

Users must be warned in advance of their passwords expiring.

CM-6 - Low - CCI-000366 - V-226291 - SV-226291r794589_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN12-SO-000025

Vuln IDs

V-226291
V-1172

Rule IDs

SV-226291r794589_rule
SV-52876

Creating strong passwords that can be remembered by users requires some thought. By giving the user advance warning, the user has time to construct a sufficiently strong password. This setting configures the system to display a warning to users telling them how many days are left before their password expires.

Checks: C-27993r476717_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\Microsoft\Windows NT\CurrentVersion\Winlogon\ Value Name: PasswordExpiryWarning Value Type: REG_DWORD Value: 14 (or greater)

Fix: F-27981r476718_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Interactive Logon: Prompt user to change password before expiration" to "14" days or more.

b

The Smart Card removal option must be configured to Force Logoff or Lock Workstation.

CM-6 - Medium - CCI-000366 - V-226292 - SV-226292r794590_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-SO-000027

Vuln IDs

V-226292
V-1157

Rule IDs

SV-226292r794590_rule
SV-52867

Unattended systems are susceptible to unauthorized use and must be locked. Configuring a system to lock when a smart card is removed will ensure the system is inaccessible when unattended.

Checks: C-27994r476720_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\Microsoft\Windows NT\CurrentVersion\Winlogon\ Value Name: SCRemoveOption Value Type: REG_SZ Value: 1 (Lock Workstation) or 2 (Force Logoff) 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 must be documented with the ISSO.

Fix: F-27982r476721_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".

b

The Windows SMB client must be configured to always perform SMB packet signing.

SC-8 - Medium - CCI-002418 - V-226293 - SV-226293r794570_rule

RMF Control

SC-8

Severity

M

CCI

Version

WN12-SO-000028

Vuln IDs

V-226293
V-6832

Rule IDs

SV-226293r794570_rule
SV-52935

The server message block (SMB) protocol provides the basis for many network operations. Digitally signed SMB packets aid in preventing man-in-the-middle attacks. If this policy is enabled, the SMB client will only communicate with an SMB server that performs SMB packet signing.

Checks: C-27995r476723_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: \System\CurrentControlSet\Services\LanmanWorkstation\Parameters\ Value Name: RequireSecuritySignature Value Type: REG_DWORD Value: 1

Fix: F-27983r476724_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".

b

The Windows SMB client must be enabled to perform SMB packet signing when possible.

SC-8 - Medium - CCI-002418 - V-226294 - SV-226294r794571_rule

RMF Control

SC-8

Severity

M

CCI

Version

WN12-SO-000029

Vuln IDs

V-226294
V-1166

Rule IDs

SV-226294r794571_rule
SV-52874

The server message block (SMB) protocol provides the basis for many network operations. If this policy is enabled, the SMB client will request packet signing when communicating with an SMB server that is enabled or required to perform SMB packet signing.

Checks: C-27996r476726_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: \System\CurrentControlSet\Services\LanmanWorkstation\Parameters\ Value Name: EnableSecuritySignature Value Type: REG_DWORD Value: 1

Fix: F-27984r476727_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".

b

Unencrypted passwords must not be sent to third-party SMB Servers.

IA-5 - Medium - CCI-000197 - V-226295 - SV-226295r794528_rule

RMF Control

IA-5

Severity

M

CCI

CCI-000197

Version

WN12-SO-000030

Vuln IDs

V-226295
V-1141

Rule IDs

SV-226295r794528_rule
SV-52861

Some non-Microsoft SMB servers only support unencrypted (plain text) password authentication. Sending plain text passwords across the network, when authenticating to an SMB server, reduces the overall security of the environment. Check with the vendor of the SMB server to see if there is a way to support encrypted password authentication.

Checks: C-27997r476729_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: \SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ Value Name: EnablePlainTextPassword Value Type: REG_DWORD Value: 0

Fix: F-27985r476730_fix

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

a

The amount of idle time required before suspending a session must be properly set.

SC-10 - Low - CCI-001133 - V-226296 - SV-226296r794608_rule

RMF Control

SC-10

Severity

L

CCI

Version

WN12-SO-000031

Vuln IDs

V-226296
V-1174

Rule IDs

SV-226296r794608_rule
SV-52878

Open sessions can increase the avenues of attack on a system. This setting is used to control when a computer disconnects an inactive SMB session. If client activity resumes, the session is automatically reestablished. This protects critical and sensitive network data from exposure to unauthorized personnel with physical access to the computer.

Checks: C-27998r476732_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: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\ Value Name: autodisconnect Value Type: REG_DWORD Value: 0x0000000f (15) (or less)

Fix: F-27986r476733_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Microsoft Network Server: Amount of idle time required before suspending session" to "15" minutes or less.

b

The Windows SMB server must be configured to always perform SMB packet signing.

SC-8 - Medium - CCI-002418 - V-226297 - SV-226297r794572_rule

RMF Control

SC-8

Severity

M

CCI

Version

WN12-SO-000032

Vuln IDs

V-226297
V-6833

Rule IDs

SV-226297r794572_rule
SV-52936

The server message block (SMB) protocol provides the basis for many network operations. Digitally signed SMB packets aid in preventing man-in-the-middle attacks. If this policy is enabled, the SMB server will only communicate with an SMB client that performs SMB packet signing.

Checks: C-27999r476735_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: \System\CurrentControlSet\Services\LanManServer\Parameters\ Value Name: RequireSecuritySignature Value Type: REG_DWORD Value: 1

Fix: F-27987r476736_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".

b

The Windows SMB server must perform SMB packet signing when possible.

SC-8 - Medium - CCI-002418 - V-226298 - SV-226298r794573_rule

RMF Control

SC-8

Severity

M

CCI

Version

WN12-SO-000033

Vuln IDs

V-226298
V-1162

Rule IDs

SV-226298r794573_rule
SV-52870

The server message block (SMB) protocol provides the basis for many network operations. Digitally signed SMB packets aid in preventing man-in-the-middle attacks. If this policy is enabled, the SMB server will negotiate SMB packet signing as requested by the client.

Checks: C-28000r476738_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: \System\CurrentControlSet\Services\LanManServer\Parameters\ Value Name: EnableSecuritySignature Value Type: REG_DWORD Value: 1

Fix: F-27988r476739_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".

a

Users must be forcibly disconnected when their logon hours expire.

SC-10 - Low - CCI-001133 - V-226299 - SV-226299r794609_rule

RMF Control

SC-10

Severity

L

CCI

Version

WN12-SO-000034

Vuln IDs

V-226299
V-1136

Rule IDs

SV-226299r794609_rule
SV-52860

Users must not be permitted to remain logged on to the network after they have exceeded their permitted logon hours. In many cases, this indicates that a user forgot to log off before leaving for the day. However, it may also indicate that a user is attempting unauthorized access at a time when the system may be less closely monitored. Forcibly disconnecting users when logon hours expire protects critical and sensitive network data from exposure to unauthorized personnel with physical access to the computer.

Checks: C-28001r476741_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: \System\CurrentControlSet\Services\LanManServer\Parameters\ Value Name: EnableForcedLogoff Value Type: REG_DWORD Value: 1

Fix: F-27989r476742_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Microsoft network server: Disconnect clients when logon hours expire" to "Enabled".

b

The service principal name (SPN) target name validation level must be turned off.

CM-6 - Medium - CCI-000366 - V-226300 - SV-226300r794591_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-SO-000035

Vuln IDs

V-226300
V-21950

Rule IDs

SV-226300r794591_rule
SV-53175

If a service principle name (SPN) is provided by the client, it is validated against the server's list of SPNs. Implementation may disrupt file and print sharing capabilities.

Checks: C-28002r476744_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: \System\CurrentControlSet\Services\LanmanServer\Parameters\ Value Name: SmbServerNameHardeningLevel Type: REG_DWORD Value: 0

Fix: F-27990r476745_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Microsoft network server: Server SPN target name validation level" to "Off".

b

Automatic logons must be disabled.

CM-6 - Medium - CCI-000366 - V-226301 - SV-226301r794593_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-SO-000036

Vuln IDs

V-226301
V-1145

Rule IDs

SV-226301r794593_rule
SV-52107

Allowing a system to automatically log on when the machine is booted could give access to any unauthorized individual who restarts the computer. Automatic logon with administrator privileges would give full access to an unauthorized individual.

Checks: C-28003r476747_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\Microsoft\Windows NT\CurrentVersion\Winlogon\ Value Name: AutoAdminLogon Type: REG_SZ Value: 0

Fix: F-27991r794592_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "MSS: (AutoAdminLogon) Enable Automatic Logon (not recommended)" to "Disabled". Ensure no passwords are stored in the "DefaultPassword" registry value noted below: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \Software\Microsoft\Windows NT\CurrentVersion\Winlogon\ Value Name: DefaultPassword (See "Updating the Windows Security Options File" in the STIG Overview document if MSS settings are not visible in the system's policy tools.) Severity Override Guidance: If the DefaultName or DefaultDomainName in the same registry path contain an administrator account name and the DefaultPassword contains a value, this is a CAT I finding.

a

IPv6 source routing must be configured to the highest protection level.

CM-6 - Low - CCI-000366 - V-226302 - SV-226302r794594_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN12-SO-000037

Vuln IDs

V-226302
V-21955

Rule IDs

SV-226302r794594_rule
SV-53180

Configuring the system to disable IPv6 source routing protects against spoofing.

Checks: C-28004r476750_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: \SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\ Value Name: DisableIPSourceRouting Type: REG_DWORD Value: 2

Fix: F-27992r476751_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "MSS: (DisableIPSourceRouting IPv6) IP source routing protection level (protects against packet spoofing)" to "Highest protection, source routing is completely disabled". (See "Updating the Windows Security Options File" in the STIG Overview document if MSS settings are not visible in the system's policy tools.)

a

The system must be configured to prevent IP source routing.

CM-6 - Low - CCI-000366 - V-226303 - SV-226303r794595_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN12-SO-000038

Vuln IDs

V-226303
V-4110

Rule IDs

SV-226303r794595_rule
SV-52924

Configuring the system to disable IP source routing protects against spoofing.

Checks: C-28005r476753_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: \System\CurrentControlSet\Services\Tcpip\Parameters\ Value Name: DisableIPSourceRouting Value Type: REG_DWORD Value: 2

Fix: F-27993r476754_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "MSS: (DisableIPSourceRouting) IP source routing protection level (protects against packet spoofing)" to "Highest protection, source routing is completely disabled". (See "Updating the Windows Security Options File" in the STIG Overview document if MSS settings are not visible in the system's policy tools.)

a

The system must be configured to prevent Internet Control Message Protocol (ICMP) redirects from overriding Open Shortest Path First (OSPF) generated routes.

CM-6 - Low - CCI-000366 - V-226304 - SV-226304r794596_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN12-SO-000039

Vuln IDs

V-226304
V-4111

Rule IDs

SV-226304r794596_rule
SV-52925

Allowing ICMP redirect of routes can lead to traffic not being routed properly. When disabled, this forces ICMP to be routed via shortest path first.

Checks: C-28006r476756_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: \System\CurrentControlSet\Services\Tcpip\Parameters\ Value Name: EnableICMPRedirect Value Type: REG_DWORD Value: 0

Fix: F-27994r476757_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "MSS: (EnableICMPRedirect) Allow ICMP redirects to override OSPF generated routes" to "Disabled". (See "Updating the Windows Security Options File" in the STIG Overview document if MSS settings are not visible in the system's policy tools.)

a

The system must be configured to limit how often keep-alive packets are sent.

SC-5 - Low - CCI-002385 - V-226305 - SV-226305r794561_rule

RMF Control

SC-5

Severity

L

CCI

Version

WN12-SO-000041

Vuln IDs

V-226305
V-4113

Rule IDs

SV-226305r794561_rule
SV-52927

This setting controls how often TCP sends a keep-alive packet in attempting to verify that an idle connection is still intact. A higher value could allow an attacker to cause a denial of service with numerous connections.

Checks: C-28007r476759_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: \System\CurrentControlSet\Services\Tcpip\Parameters\ Value Name: KeepAliveTime Value Type: REG_DWORD Value: 300000 (or less)

Fix: F-27995r476760_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "MSS: (KeepAliveTime) How often keep-alive packets are sent in milliseconds" to "300000 or 5 minutes (recommended)" or less. (See "Updating the Windows Security Options File" in the STIG Overview document if MSS settings are not visible in the system's policy tools.)

a

IPSec Exemptions must be limited.

CM-6 - Low - CCI-000366 - V-226306 - SV-226306r794597_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN12-SO-000042

Vuln IDs

V-226306
V-14232

Rule IDs

SV-226306r794597_rule
SV-52945

IPSec exemption filters allow specific traffic that may be needed by the system for such things as Kerberos authentication. This setting configures Windows for specific IPSec exemptions.

Checks: C-28008r476762_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: \System\CurrentControlSet\Services\IPSEC\ Value Name: NoDefaultExempt Value Type: REG_DWORD Value: 3

Fix: F-27996r476763_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "MSS: (NoDefaultExempt) Configure IPSec exemptions for various types of network traffic" to "Only ISAKMP is exempt (recommended for Windows Server 2003)". (See "Updating the Windows Security Options File" in the STIG Overview document if MSS settings are not visible in the system's policy tools.)

a

The system must be configured to ignore NetBIOS name release requests except from WINS servers.

SC-5 - Low - CCI-002385 - V-226307 - SV-226307r794562_rule

RMF Control

SC-5

Severity

L

CCI

Version

WN12-SO-000043

Vuln IDs

V-226307
V-4116

Rule IDs

SV-226307r794562_rule
SV-52928

Configuring the system to ignore name release requests, except from WINS servers, prevents a denial of service (DoS) attack. The DoS consists of sending a NetBIOS name release request to the server for each entry in the server's cache, causing a response delay in the normal operation of the servers WINS resolution capability.

Checks: C-28009r476765_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: \SYSTEM\CurrentControlSet\Services\Netbt\Parameters\ Value Name: NoNameReleaseOnDemand Value Type: REG_DWORD Value: 1

Fix: F-27997r476766_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "MSS: (NoNameReleaseOnDemand) Allow the computer to ignore NetBIOS name release requests except from WINS servers" to "Enabled". (See "Updating the Windows Security Options File" in the STIG Overview document if MSS settings are not visible in the system's policy tools.)

a

The system must be configured to disable the Internet Router Discovery Protocol (IRDP).

SC-5 - Low - CCI-002385 - V-226308 - SV-226308r794563_rule

RMF Control

SC-5

Severity

L

CCI

Version

WN12-SO-000044

Vuln IDs

V-226308
V-4112

Rule IDs

SV-226308r794563_rule
SV-52926

The Internet Router Discovery Protocol (IRDP) is used to detect and configure default gateway addresses on the computer. If a router is impersonated on a network, traffic could be routed through the compromised system.

Checks: C-28010r476768_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: \System\CurrentControlSet\Services\Tcpip\Parameters\ Value Name: PerformRouterDiscovery Value Type: REG_DWORD Value: 0

Fix: F-27998r476769_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "MSS: (PerformRouterDiscovery) Allow IRDP to detect and configure Default Gateway addresses (could lead to DoS)" to "Disabled". (See "Updating the Windows Security Options File" in the STIG Overview document if MSS settings are not visible in the system's policy tools.)

b

The system must be configured to use Safe DLL Search Mode.

CM-6 - Medium - CCI-000366 - V-226309 - SV-226309r794598_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-SO-000045

Vuln IDs

V-226309
V-3479

Rule IDs

SV-226309r794598_rule
SV-52920

The default search behavior, when an application calls a function in a Dynamic Link Library (DLL), is to search the current directory, followed by the directories contained in the system's path environment variable. An unauthorized DLL, inserted into an application's working directory, could allow malicious code to be run on the system. Setting this policy value forces the system to search the %Systemroot% for the DLL before searching the current directory or the rest of the path.

Checks: C-28011r476771_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: \System\CurrentControlSet\Control\Session Manager\ Value Name: SafeDllSearchMode Value Type: REG_DWORD Value: 1

Fix: F-27999r476772_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". (See "Updating the Windows Security Options File" in the STIG Overview document if MSS settings are not visible in the system's policy tools.)

a

The system must be configured to have password protection take effect within a limited time frame when the screen saver becomes active.

CM-6 - Low - CCI-000366 - V-226310 - SV-226310r794599_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN12-SO-000046

Vuln IDs

V-226310
V-4442

Rule IDs

SV-226310r794599_rule
SV-52930

Allowing more than several seconds makes the computer vulnerable to a potential attack from someone walking up to the console to attempt to log on to the system before the lock takes effect.

Checks: C-28012r476774_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\Microsoft\Windows NT\CurrentVersion\Winlogon\ Value Name: ScreenSaverGracePeriod Value Type: REG_SZ Value: 5 (or less)

Fix: F-28000r476775_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "MSS: (ScreenSaverGracePeriod) The time in seconds before the screen saver grace period expires (0 recommended)" to "5" or less. (See "Updating the Windows Security Options File" in the STIG Overview document if MSS settings are not visible in the system's policy tools.)

a

IPv6 TCP data retransmissions must be configured to prevent resources from becoming exhausted.

SC-5 - Low - CCI-002385 - V-226311 - SV-226311r794564_rule

RMF Control

SC-5

Severity

L

CCI

Version

WN12-SO-000047

Vuln IDs

V-226311
V-21956

Rule IDs

SV-226311r794564_rule
SV-53181

Configuring Windows to limit the number of times that IPv6 TCP retransmits unacknowledged data segments before aborting the attempt helps prevent resources from becoming exhausted.

Checks: C-28013r476777_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: \SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\ Value Name: TcpMaxDataRetransmissions Value Type: REG_DWORD Value: 3 (or less)

Fix: F-28001r476778_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "MSS: (TcpMaxDataRetransmissions IPv6) How many times unacknowledged data is retransmitted (3 recommended, 5 is default)" to "3" or less. (See "Updating the Windows Security Options File" in the STIG Overview document if MSS settings are not visible in the system's policy tools.)

a

The system must limit how many times unacknowledged TCP data is retransmitted.

SC-5 - Low - CCI-002385 - V-226312 - SV-226312r794565_rule

RMF Control

SC-5

Severity

L

CCI

Version

WN12-SO-000048

Vuln IDs

V-226312
V-4438

Rule IDs

SV-226312r794565_rule
SV-52929

In a SYN flood attack, the attacker sends a continuous stream of SYN packets to a server, and the server leaves the half-open connections open until it is overwhelmed and is no longer able to respond to legitimate requests.

Checks: C-28014r476780_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: \SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ Value Name: TcpMaxDataRetransmissions Value Type: REG_DWORD Value: 3 (or less)

Fix: F-28002r476781_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "MSS: (TcpMaxDataRetransmissions) How many times unacknowledged data is retransmitted (3 recommended, 5 is default)" to "3" or less. (See "Updating the Windows Security Options File" in the STIG Overview document if MSS settings are not visible in the system's policy tools.)

a

The system must generate an audit event when the audit log reaches a percentage of full threshold.

AU-5 - Low - CCI-000139 - V-226313 - SV-226313r794512_rule

RMF Control

AU-5

Severity

L

CCI

CCI-000139

Version

WN12-SO-000049

Vuln IDs

V-226313
V-4108

Rule IDs

SV-226313r794512_rule
SV-52923

When the audit log reaches a given percent full, an audit event is written to the security log. It is recorded as a successful audit event under the category of System. This option may be especially useful if the audit logs are set to be cleared manually.

Checks: C-28015r476783_chk

If the system is configured to write to an audit server, or is configured to automatically archive full logs, this is NA. 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: \System\CurrentControlSet\Services\Eventlog\Security\ Value Name: WarningLevel Value Type: REG_DWORD Value: 90 (or less)

Fix: F-28003r476784_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "MSS: (WarningLevel) Percentage threshold for the security event log at which the system will generate a warning" to "90" or less. (See "Updating the Windows Security Options File" in the STIG Overview document if MSS settings are not visible in the system's policy tools.)

c

Anonymous SID/Name translation must not be allowed.

CM-6 - High - CCI-000366 - V-226314 - SV-226314r794600_rule

RMF Control

CM-6

Severity

H

CCI

Version

WN12-SO-000050

Vuln IDs

V-226314
V-3337

Rule IDs

SV-226314r794600_rule
SV-52882

Allowing anonymous SID/Name translation can provide sensitive information for accessing a system. Only authorized users must be able to perform such translations.

Checks: C-28016r476786_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options. If the value for "Network access: Allow anonymous SID/Name translation" is not set to "Disabled", this is a finding.

Fix: F-28004r476787_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network access: Allow anonymous SID/Name translation" to "Disabled".

c

Anonymous enumeration of SAM accounts must not be allowed.

CM-6 - High - CCI-000366 - V-226315 - SV-226315r794601_rule

RMF Control

CM-6

Severity

H

CCI

Version

WN12-SO-000051

Vuln IDs

V-226315
V-26283

Rule IDs

SV-226315r794601_rule
SV-53122

Anonymous enumeration of SAM accounts allows anonymous log on users (null session connections) to list all accounts names, thus providing a list of potential points to attack the system.

Checks: C-28017r476789_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: \System\CurrentControlSet\Control\Lsa\ Value Name: RestrictAnonymousSAM Value Type: REG_DWORD Value: 1

Fix: F-28005r476790_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network access: Do not allow anonymous enumeration of SAM accounts" to "Enabled".

c

Anonymous enumeration of shares must be restricted.

SC-4 - High - CCI-001090 - V-226316 - SV-226316r794544_rule

RMF Control

SC-4

Severity

H

CCI

Version

WN12-SO-000052

Vuln IDs

V-226316
V-1093

Rule IDs

SV-226316r794544_rule
SV-52847

Allowing anonymous logon users (null session connections) to list all account names and enumerate all shared resources can provide a map of potential points to attack the system.

Checks: C-28018r476792_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: \System\CurrentControlSet\Control\Lsa\ Value Name: RestrictAnonymous Value Type: REG_DWORD Value: 1

Fix: F-28006r476793_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network access: Do not allow anonymous enumeration of SAM accounts and shares" to "Enabled".

b

The system must be configured to prevent anonymous users from having the same rights as the Everyone group.

CM-6 - Medium - CCI-000366 - V-226317 - SV-226317r794602_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-SO-000054

Vuln IDs

V-226317
V-3377

Rule IDs

SV-226317r794602_rule
SV-52890

Access by anonymous users must be restricted. If this setting is enabled, then anonymous users have the same rights and permissions as the built-in Everyone group. Anonymous users must not have these permissions or rights.

Checks: C-28019r476795_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: \System\CurrentControlSet\Control\Lsa\ Value Name: EveryoneIncludesAnonymous Value Type: REG_DWORD Value: 0

Fix: F-28007r476796_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".

c

Named pipes that can be accessed anonymously must be configured with limited values on domain controllers.

SC-4 - High - CCI-001090 - V-226318 - SV-226318r794545_rule

RMF Control

SC-4

Severity

H

CCI

Version

WN12-SO-000055-DC

Vuln IDs

V-226318
V-3338

Rule IDs

SV-226318r794545_rule
SV-51138

Named pipes that can be accessed anonymously provide the potential for gaining unauthorized system access. Pipes are internal system communications processes. They are identified internally by ID numbers that vary between systems. To make access to these processes easier, these pipes are given names that do not vary between systems. This setting controls which of these pipes anonymous users may access.

Checks: C-28020r476798_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: \System\CurrentControlSet\Services\LanManServer\Parameters\ Value Name: NullSessionPipes Value Type: REG_MULTI_SZ Value: netlogon, samr, lsarpc The default configuration of systems promoted to domain controllers may include a blank entry in the first line prior to "netlogon", "samr", and "lsarpc". This will appear in the registry as a blank entry when viewing the registry key summary; however the value data for "NullSessionPipes" will contain the default entries. Legitimate applications may add entries to this registry value. If an application requires these entries to function properly and is documented with the ISSO, this would not be a finding. Documentation must contain supporting information from the vendor's instructions.

Fix: F-28008r476799_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network access: Named pipes that can be accessed anonymously" to only include "netlogon, samr, lsarpc".

c

Unauthorized remotely accessible registry paths must not be configured.

SC-4 - High - CCI-001090 - V-226319 - SV-226319r794546_rule

RMF Control

SC-4

Severity

H

CCI

Version

WN12-SO-000056

Vuln IDs

V-226319
V-3339

Rule IDs

SV-226319r794546_rule
SV-52883

The registry is integral to the function, security, and stability of the Windows system. Some processes may require remote access to the registry. This setting controls which registry paths are accessible from a remote computer. These registry paths must be limited, as they could give unauthorized individuals access to the registry.

Checks: C-28021r476801_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: \System\CurrentControlSet\Control\SecurePipeServers\Winreg\AllowedExactPaths\ Value Name: Machine Value Type: REG_MULTI_SZ Value: see below System\CurrentControlSet\Control\ProductOptions System\CurrentControlSet\Control\Server Applications Software\Microsoft\Windows NT\CurrentVersion Legitimate applications may add entries to this registry value. If an application requires these entries to function properly and is documented with the ISSO, this would not be a finding. Documentation must contain supporting information from the vendor's instructions.

Fix: F-28009r476802_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network access: Remotely accessible registry paths" with the following entries: System\CurrentControlSet\Control\ProductOptions System\CurrentControlSet\Control\Server Applications Software\Microsoft\Windows NT\CurrentVersion

c

Unauthorized remotely accessible registry paths and sub-paths must not be configured.

SC-4 - High - CCI-001090 - V-226320 - SV-226320r794547_rule

RMF Control

SC-4

Severity

H

CCI

Version

WN12-SO-000057

Vuln IDs

V-226320
V-4443

Rule IDs

SV-226320r794547_rule
SV-52931

The registry is integral to the function, security, and stability of the Windows system. Some processes may require remote access to the registry. This setting controls which registry paths and sub-paths are accessible from a remote computer. These registry paths must be limited, as they could give unauthorized individuals access to the registry.

Checks: C-28022r476804_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: \System\CurrentControlSet\Control\SecurePipeServers\Winreg\AllowedPaths\ Value Name: Machine Value Type: REG_MULTI_SZ Value: see below Software\Microsoft\OLAP Server Software\Microsoft\Windows NT\CurrentVersion\Perflib Software\Microsoft\Windows NT\CurrentVersion\Print Software\Microsoft\Windows NT\CurrentVersion\Windows System\CurrentControlSet\Control\ContentIndex System\CurrentControlSet\Control\Print\Printers System\CurrentControlSet\Control\Terminal Server System\CurrentControlSet\Control\Terminal Server\UserConfig System\CurrentControlSet\Control\Terminal Server\DefaultUserConfiguration System\CurrentControlSet\Services\Eventlog System\CurrentControlSet\Services\Sysmonlog Legitimate applications may add entries to this registry value. If an application requires these entries to function properly and is documented with the ISSO, this would not be a finding. Documentation must contain supporting information from the vendor's instructions.

Fix: F-28010r476805_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network access: Remotely accessible registry paths and sub-paths" with the following entries: Software\Microsoft\OLAP Server Software\Microsoft\Windows NT\CurrentVersion\Perflib Software\Microsoft\Windows NT\CurrentVersion\Print Software\Microsoft\Windows NT\CurrentVersion\Windows System\CurrentControlSet\Control\ContentIndex System\CurrentControlSet\Control\Print\Printers System\CurrentControlSet\Control\Terminal Server System\CurrentControlSet\Control\Terminal Server\UserConfig System\CurrentControlSet\Control\Terminal Server\DefaultUserConfiguration System\CurrentControlSet\Services\Eventlog System\CurrentControlSet\Services\Sysmonlog

c

Anonymous access to Named Pipes and Shares must be restricted.

SC-4 - High - CCI-001090 - V-226321 - SV-226321r794548_rule

RMF Control

SC-4

Severity

H

CCI

Version

WN12-SO-000058

Vuln IDs

V-226321
V-6834

Rule IDs

SV-226321r794548_rule
SV-52937

Allowing anonymous access to named pipes or shares provides the potential for unauthorized system access. This setting restricts access to those defined in "Network access: Named Pipes that can be accessed anonymously" and "Network access: Shares that can be accessed anonymously", both of which must be blank under other requirements.

Checks: C-28023r476807_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: \System\CurrentControlSet\Services\LanManServer\Parameters\ Value Name: RestrictNullSessAccess Value Type: REG_DWORD Value: 1

Fix: F-28011r476808_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network access: Restrict anonymous access to Named Pipes and Shares" to "Enabled".

c

Network shares that can be accessed anonymously must not be allowed.

SC-4 - High - CCI-001090 - V-226322 - SV-226322r794549_rule

RMF Control

SC-4

Severity

H

CCI

Version

WN12-SO-000059

Vuln IDs

V-226322
V-3340

Rule IDs

SV-226322r794549_rule
SV-52884

Anonymous access to network shares provides the potential for gaining unauthorized system access by network users. This could lead to the exposure or corruption of sensitive data.

Checks: C-28024r476810_chk

If the following registry value does not exist, this is not a finding: If the following registry value does exist and is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \System\CurrentControlSet\Services\LanManServer\Parameters\ Value Name: NullSessionShares Value Type: REG_MULTI_SZ Value: (Blank)

Fix: F-28012r476811_fix

Ensure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network access: Shares that can be accessed anonymously" contains no entries (blank).

b

The system must be configured to use the Classic security model.

SC-4 - Medium - CCI-001090 - V-226323 - SV-226323r794550_rule

RMF Control

SC-4

Severity

M

CCI

Version

WN12-SO-000060

Vuln IDs

V-226323
V-3378

Rule IDs

SV-226323r794550_rule
SV-52891

Windows includes two network-sharing security models - Classic and Guest only. With the Classic model, local accounts must be password protected; otherwise, anyone can use guest user accounts to access shared system resources.

Checks: C-28025r476813_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: \System\CurrentControlSet\Control\Lsa\ Value Name: ForceGuest Value Type: REG_DWORD Value: 0

Fix: F-28013r476814_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".

b

Services using Local System that use Negotiate when reverting to NTLM authentication must use the computer identity vs. authenticating anonymously.

IA-3 - Medium - CCI-000778 - V-226324 - SV-226324r794537_rule

RMF Control

IA-3

Severity

M

CCI

CCI-000778

Version

WN12-SO-000061

Vuln IDs

V-226324
V-21951

Rule IDs

SV-226324r794537_rule
SV-53176

Services using Local System that use Negotiate when reverting to NTLM authentication may gain unauthorized access if allowed to authenticate anonymously vs. using the computer identity.

Checks: C-28026r476816_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: \System\CurrentControlSet\Control\LSA\ Value Name: UseMachineId Type: REG_DWORD Value: 1

Fix: F-28014r476817_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network security: Allow Local System to use computer identity for NTLM" to "Enabled".

b

NTLM must be prevented from falling back to a Null session.

CM-6 - Medium - CCI-000366 - V-226325 - SV-226325r794603_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-SO-000062

Vuln IDs

V-226325
V-21952

Rule IDs

SV-226325r794603_rule
SV-53177

NTLM sessions that are allowed to fall back to Null (unauthenticated) sessions may gain unauthorized access.

Checks: C-28027r476819_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: \System\CurrentControlSet\Control\LSA\MSV1_0\ Value Name: allownullsessionfallback Type: REG_DWORD Value: 0

Fix: F-28015r476820_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network security: Allow LocalSystem NULL session fallback" to "Disabled".

b

PKU2U authentication using online identities must be prevented.

CM-6 - Medium - CCI-000366 - V-226326 - SV-226326r794604_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-SO-000063

Vuln IDs

V-226326
V-21953

Rule IDs

SV-226326r794604_rule
SV-53178

PKU2U is a peer-to-peer authentication protocol. This setting prevents online identities from authenticating to domain-joined systems. Authentication will be centrally managed with Windows user accounts.

Checks: C-28028r476822_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: \System\CurrentControlSet\Control\LSA\pku2u\ Value Name: AllowOnlineID Type: REG_DWORD Value: 0

Fix: F-28016r476823_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network security: Allow PKU2U authentication requests to this computer to use online identities" to "Disabled".

b

Kerberos encryption types must be configured to prevent the use of DES and RC4 encryption suites.

IA-7 - Medium - CCI-000803 - V-226327 - SV-226327r794539_rule

RMF Control

IA-7

Severity

M

CCI

CCI-000803

Version

WN12-SO-000064

Vuln IDs

V-226327
V-21954

Rule IDs

SV-226327r794539_rule
SV-53179

Certain encryption types are no longer considered secure. The DES and RC4 encryption suites must not be used for Kerberos encryption. Note: Removing the previously allowed RC4_HMAC_MD5 encryption suite may have operational impacts and must be thoroughly tested for the environment before changing. This includes but is not limited to parent\child trusts where RC4 is still enabled; selecting "The other domain supports Kerberos AES Encryption" may be required on the domain trusts to allow client communication across the trust relationship.

Checks: C-28029r476825_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\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters\ Value Name: SupportedEncryptionTypes Value Type: REG_DWORD Value: 0x7ffffff8 (2147483640) Note: Removing the previously allowed RC4_HMAC_MD5 encryption suite may have operational impacts and must be thoroughly tested for the environment before changing. This includes but is not limited to parent\child trusts where RC4 is still enabled; selecting "The other domain supports Kerberos AES Encryption" may be required on the domain trusts to allow client communication across the trust relationship.

Fix: F-28017r476826_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Network security: Configure encryption types allowed for Kerberos" to "Enabled" with only the following selected: AES128_HMAC_SHA1 AES256_HMAC_SHA1 Future encryption types Note: Removing the previously allowed RC4_HMAC_MD5 encryption suite may have operational impacts and must be thoroughly tested for the environment before changing. This includes but is not limited to parent\child trusts where RC4 is still enabled; selecting "The other domain supports Kerberos AES Encryption" may be required on the domain trusts to allow client communication across the trust relationship.

c

The system must be configured to prevent the storage of the LAN Manager hash of passwords.

IA-5 - High - CCI-000196 - V-226328 - SV-226328r794527_rule

RMF Control

IA-5

Severity

H

CCI

CCI-000196

Version

WN12-SO-000065

Vuln IDs

V-226328
V-3379

Rule IDs

SV-226328r794527_rule
SV-52892

The LAN Manager hash uses a weak encryption algorithm and there are several tools available that use this hash to retrieve account passwords. This setting controls whether or not a LAN Manager hash of the password is stored in the SAM the next time the password is changed.

Checks: C-28030r476828_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: \System\CurrentControlSet\Control\Lsa\ Value Name: NoLMHash Value Type: REG_DWORD Value: 1

Fix: F-28018r476829_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network security: Do not store LAN Manager hash value on next password change" to "Enabled".

b

The system must be configured to force users to log off when their allowed logon hours expire.

SC-10 - Medium - CCI-001133 - V-226329 - SV-226329r794610_rule

RMF Control

SC-10

Severity

M

CCI

Version

WN12-SO-000066

Vuln IDs

V-226329
V-3380

Rule IDs

SV-226329r794610_rule
SV-52893

Limiting logon hours can help protect data by only allowing access during specified times. This setting controls whether or not users are forced to log off when their allowed logon hours expire. If logon hours are set for users, this must be enforced.

Checks: C-28031r476831_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options. If the value for "Network security: Force logoff when logon hours expire" is not set to "Enabled", this is a finding.

Fix: F-28019r476832_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network security: Force logoff when logon hours expire" to "Enabled".

c

The LanMan authentication level must be set to send NTLMv2 response only, and to refuse LM and NTLM.

CM-6 - High - CCI-000366 - V-226330 - SV-226330r794605_rule

RMF Control

CM-6

Severity

H

CCI

Version

WN12-SO-000067

Vuln IDs

V-226330
V-1153

Rule IDs

SV-226330r794605_rule
SV-52865

The Kerberos v5 authentication protocol is the default for authentication of users who are logging on to domain accounts. NTLM, which is less secure, is retained in later Windows versions for compatibility with clients and servers that are running earlier versions of Windows or applications that still use it. It is also used to authenticate logons to stand-alone computers that are running later versions.

Checks: C-28032r476834_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: \System\CurrentControlSet\Control\Lsa\ Value Name: LmCompatibilityLevel Value Type: REG_DWORD Value: 5

Fix: F-28020r476835_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network security: LAN Manager authentication level" to "Send NTLMv2 response only. Refuse LM & NTLM".

b

The system must be configured to the required LDAP client signing level.

CM-6 - Medium - CCI-000366 - V-226331 - SV-226331r794606_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-SO-000068

Vuln IDs

V-226331
V-3381

Rule IDs

SV-226331r794606_rule
SV-52894

This setting controls the signing requirements for LDAP clients. This setting must be set to Negotiate signing or Require signing, depending on the environment and type of LDAP server in use.

Checks: C-28033r476837_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: \System\CurrentControlSet\Services\LDAP\ Value Name: LDAPClientIntegrity Value Type: REG_DWORD Value: 1

Fix: F-28021r476838_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.

b

The system must be configured to meet the minimum session security requirement for NTLM SSP-based clients.

CM-6 - Medium - CCI-000366 - V-226332 - SV-226332r794678_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-SO-000069

Vuln IDs

V-226332
V-3382

Rule IDs

SV-226332r794678_rule
SV-52895

Microsoft has implemented a variety of security support providers for use with RPC sessions. All of the options must be enabled to ensure the maximum security level.

Checks: C-28034r476840_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: \System\CurrentControlSet\Control\Lsa\MSV1_0\ Value Name: NTLMMinClientSec Value Type: REG_DWORD Value: 0x20080000 (537395200)

Fix: F-28022r476841_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" and "Require 128-bit encryption" (all options selected).

b

The system must be configured to meet the minimum session security requirement for NTLM SSP-based servers.

CM-6 - Medium - CCI-000366 - V-226333 - SV-226333r794679_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-SO-000070

Vuln IDs

V-226333
V-3666

Rule IDs

SV-226333r794679_rule
SV-52922

Microsoft has implemented a variety of security support providers for use with RPC sessions. All of the options must be enabled to ensure the maximum security level.

Checks: C-28035r476843_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: \System\CurrentControlSet\Control\Lsa\MSV1_0\ Value Name: NTLMMinServerSec Value Type: REG_DWORD Value: 0x20080000 (537395200)

Fix: F-28023r476844_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" and "Require 128-bit encryption" (all options selected).

a

The shutdown option must not be available from the logon dialog box.

CM-6 - Low - CCI-000366 - V-226334 - SV-226334r794680_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN12-SO-000073

Vuln IDs

V-226334
V-1075

Rule IDs

SV-226334r794680_rule
SV-52840

Displaying the shutdown button may allow individuals to shut down a system anonymously. Only authenticated users should be allowed to shut down the system. Preventing display of this button in the logon dialog box ensures that individuals who shut down the system are authorized and tracked in the system's Security event log.

Checks: C-28036r476846_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\Microsoft\Windows\CurrentVersion\Policies\System\ Value Name: ShutdownWithoutLogon Value Type: REG_DWORD Value: 0

Fix: F-28024r476847_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Shutdown: Allow system to be shutdown without having to log on" to "Disabled".

b

The system must be configured to use FIPS-compliant algorithms for encryption, hashing, and signing.

SC-13 - Medium - CCI-002450 - V-226335 - SV-226335r794676_rule

RMF Control

SC-13

Severity

M

CCI

CCI-002450

Version

WN12-SO-000074

Vuln IDs

V-226335
V-3383

Rule IDs

SV-226335r794676_rule
SV-52896

This setting ensures that the system uses algorithms that are FIPS-compliant for encryption, hashing, and signing. FIPS-compliant algorithms meet specific standards established by the U.S. Government and must be the algorithms used for all OS encryption functions.

Checks: C-28037r476849_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: \SYSTEM\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\ Value Name: Enabled 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-28025r476850_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".

b

The system must be configured to require case insensitivity for non-Windows subsystems.

CM-6 - Medium - CCI-000366 - V-226336 - SV-226336r794681_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-SO-000075

Vuln IDs

V-226336
V-3385

Rule IDs

SV-226336r794681_rule
SV-52897

This setting controls the behavior of non-Windows subsystems when dealing with the case of arguments or commands. Case sensitivity could lead to the access of files or commands that must be restricted. To prevent this from happening, case insensitivity restrictions must be required.

Checks: C-28038r476852_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: \System\CurrentControlSet\Control\Session Manager\Kernel\ Value Name: ObCaseInsensitive Value Type: REG_DWORD Value: 1

Fix: F-28026r476853_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "System objects: Require case insensitivity for non-Windows subsystems" to "Enabled".

a

The default permissions of global system objects must be increased.

CM-6 - Low - CCI-000366 - V-226337 - SV-226337r794682_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN12-SO-000076

Vuln IDs

V-226337
V-1173

Rule IDs

SV-226337r794682_rule
SV-52877

Windows systems maintain a global list of shared system resources such as DOS device names, mutexes, and semaphores. Each type of object is created with a default DACL that specifies who can access the objects with what permissions. If this policy is enabled, the default DACL is stronger, allowing nonadministrative users to read shared objects, but not modify shared objects that they did not create.

Checks: C-28039r476855_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: \System\CurrentControlSet\Control\Session Manager\ Value Name: ProtectionMode Value Type: REG_DWORD Value: 1

Fix: F-28027r476856_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "System objects: Strengthen default permissions of internal system objects (e.g. Symbolic Links)" to "Enabled".

b

User Account Control approval mode for the built-in Administrator must be enabled.

IA-11 - Medium - CCI-002038 - V-226338 - SV-226338r794673_rule

RMF Control

IA-11

Severity

M

CCI

Version

WN12-SO-000077

Vuln IDs

V-226338
V-14234

Rule IDs

SV-226338r794673_rule
SV-52946

User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting configures the built-in Administrator account so that it runs in Admin Approval Mode. Satisfies: SRG-OS-000373-GPOS-00158

Checks: C-28040r476858_chk

UAC requirements are NA on Server Core installations. 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\Microsoft\Windows\CurrentVersion\Policies\System\ Value Name: FilterAdministratorToken Value Type: REG_DWORD Value: 1

Fix: F-28028r476859_fix

UAC requirements are NA on Server Core installations. Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "User Account Control: Admin Approval Mode for the Built-in Administrator account" to "Enabled".

b

User Account Control must, at minimum, prompt administrators for consent.

SC-3 - Medium - CCI-001084 - V-226339 - SV-226339r794642_rule

RMF Control

SC-3

Severity

M

CCI

Version

WN12-SO-000078

Vuln IDs

V-226339
V-14235

Rule IDs

SV-226339r794642_rule
SV-52947

User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting configures the elevation requirements for logged on administrators to complete a task that requires raised privileges.

Checks: C-28041r476861_chk

UAC requirements are NA on Server Core installations. 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\Microsoft\Windows\CurrentVersion\Policies\System\ Value Name: ConsentPromptBehaviorAdmin Value Type: REG_DWORD Value: 4 (Prompt for consent) 3 (Prompt for credentials) 2 (Prompt for consent on the secure desktop) 1 (Prompt for credentials on the secure desktop)

Fix: F-28029r476862_fix

UAC requirements are NA on Server Core installations. Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode" to "Prompt for consent". More secure options for this setting would also be acceptable (e.g., Prompt for credentials, Prompt for consent (or credentials) on the secure desktop).

b

User Account Control must automatically deny standard user requests for elevation.

IA-11 - Medium - CCI-002038 - V-226340 - SV-226340r794674_rule

RMF Control

IA-11

Severity

M

CCI

Version

WN12-SO-000079

Vuln IDs

V-226340
V-14236

Rule IDs

SV-226340r794674_rule
SV-52948

User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting controls the behavior of elevation when requested by a standard user account. Satisfies: SRG-OS-000373-GPOS-00158

Checks: C-28042r476864_chk

UAC requirements are NA on Server Core installations. 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\Microsoft\Windows\CurrentVersion\Policies\System\ Value Name: ConsentPromptBehaviorUser Value Type: REG_DWORD Value: 0

Fix: F-28030r476865_fix

UAC requirements are NA on Server Core installations. Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "User Account Control: Behavior of the elevation prompt for standard users" to "Automatically deny elevation requests".

b

User Account Control must be configured to detect application installations and prompt for elevation.

SC-3 - Medium - CCI-001084 - V-226341 - SV-226341r794643_rule

RMF Control

SC-3

Severity

M

CCI

Version

WN12-SO-000080

Vuln IDs

V-226341
V-14237

Rule IDs

SV-226341r794643_rule
SV-52949

User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting requires Windows to respond to application installation requests by prompting for credentials.

Checks: C-28043r476867_chk

UAC requirements are NA on Server Core installations. 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\Microsoft\Windows\CurrentVersion\Policies\System\ Value Name: EnableInstallerDetection Value Type: REG_DWORD Value: 1

Fix: F-28031r476868_fix

UAC requirements are NA on Server Core installations. Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "User Account Control: Detect application installations and prompt for elevation" to "Enabled".

b

Windows must elevate all applications in User Account Control, not just signed ones.

SC-3 - Medium - CCI-001084 - V-226342 - SV-226342r794644_rule

RMF Control

SC-3

Severity

M

CCI

Version

WN12-SO-000081

Vuln IDs

V-226342
V-16008

Rule IDs

SV-226342r794644_rule
SV-53142

User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting configures whether Windows elevates all applications, or only signed ones.

Checks: C-28044r476870_chk

UAC requirements are NA on Server Core installations. 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\Microsoft\Windows\CurrentVersion\Policies\System\ Value Name: ValidateAdminCodeSignatures Value Type: REG_DWORD Value: 0

Fix: F-28032r476871_fix

UAC requirements are NA on Server Core installations. Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "User Account Control: Only elevate executables that are signed and validated" to "Disabled".

b

User Account Control must only elevate UIAccess applications that are installed in secure locations.

SC-3 - Medium - CCI-001084 - V-226343 - SV-226343r794645_rule

RMF Control

SC-3

Severity

M

CCI

Version

WN12-SO-000082

Vuln IDs

V-226343
V-14239

Rule IDs

SV-226343r794645_rule
SV-52950

User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting configures Windows to only allow applications installed in a secure location on the file system, such as the Program Files or the Windows\System32 folders, to run with elevated privileges.

Checks: C-28045r476873_chk

UAC requirements are NA on Server Core installations. 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\Microsoft\Windows\CurrentVersion\Policies\System\ Value Name: EnableSecureUIAPaths Value Type: REG_DWORD Value: 1

Fix: F-28033r476874_fix

UAC requirements are NA on Server Core installations. Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "User Account Control: Only elevate UIAccess applications that are installed in secure locations" to "Enabled".

b

User Account Control must run all administrators in Admin Approval Mode, enabling UAC.

IA-11 - Medium - CCI-002038 - V-226344 - SV-226344r794675_rule

RMF Control

IA-11

Severity

M

CCI

Version

WN12-SO-000083

Vuln IDs

V-226344
V-14240

Rule IDs

SV-226344r794675_rule
SV-52951

User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting enables UAC. Satisfies: SRG-OS-000373-GPOS-00158

Checks: C-28046r476876_chk

UAC requirements are NA on Server Core installations. 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\Microsoft\Windows\CurrentVersion\Policies\System\ Value Name: EnableLUA Value Type: REG_DWORD Value: 1

Fix: F-28034r476877_fix

UAC requirements are NA on Server Core installations. Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "User Account Control: Run all administrators in Admin Approval Mode" to "Enabled".

b

User Account Control must switch to the secure desktop when prompting for elevation.

SC-3 - Medium - CCI-001084 - V-226345 - SV-226345r794646_rule

RMF Control

SC-3

Severity

M

CCI

Version

WN12-SO-000084

Vuln IDs

V-226345
V-14241

Rule IDs

SV-226345r794646_rule
SV-52952

User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting ensures that the elevation prompt is only used in secure desktop mode.

Checks: C-28047r476879_chk

UAC requirements are NA on Server Core installations. 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\Microsoft\Windows\CurrentVersion\Policies\System\ Value Name: PromptOnSecureDesktop Value Type: REG_DWORD Value: 1

Fix: F-28035r476880_fix

UAC requirements are NA on Server Core installations. Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "User Account Control: Switch to the secure desktop when prompting for elevation" to "Enabled".

b

User Account Control must virtualize file and registry write failures to per-user locations.

SC-3 - Medium - CCI-001084 - V-226346 - SV-226346r794647_rule

RMF Control

SC-3

Severity

M

CCI

Version

WN12-SO-000085

Vuln IDs

V-226346
V-14242

Rule IDs

SV-226346r794647_rule
SV-52953

User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting configures non-UAC-compliant applications to run in virtualized file and registry entries in per-user locations, allowing them to run.

Checks: C-28048r476882_chk

UAC requirements are NA on Server Core installations. 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\Microsoft\Windows\CurrentVersion\Policies\System\ Value Name: EnableVirtualization Value Type: REG_DWORD Value: 1

Fix: F-28036r476883_fix

UAC requirements are NA on Server Core installations. Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "User Account Control: Virtualize file and registry write failures to per-user locations" to "Enabled".

b

UIAccess applications must not be allowed to prompt for elevation without using the secure desktop.

SC-3 - Medium - CCI-001084 - V-226347 - SV-226347r794648_rule

RMF Control

SC-3

Severity

M

CCI

Version

WN12-SO-000086

Vuln IDs

V-226347
V-15991

Rule IDs

SV-226347r794648_rule
SV-52223

User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting prevents User Interface Accessibility programs from disabling the secure desktop for elevation prompts.

Checks: C-28049r476885_chk

UAC requirements are NA on Server Core installations. 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\Microsoft\Windows\CurrentVersion\Policies\System\ Value Name: EnableUIADesktopToggle Value Type: REG_DWORD Value: 0

Fix: F-28037r476886_fix

UAC requirements are NA on Server Core installations. Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "User Account Control: Allow UIAccess applications to prompt for elevation without using the secure desktop" to "Disabled".

a

Optional Subsystems must not be permitted to operate on the system.

CM-7 - Low - CCI-000381 - V-226348 - SV-226348r794632_rule

RMF Control

CM-7

Severity

L

CCI

Version

WN12-SO-000088

Vuln IDs

V-226348
V-4445

Rule IDs

SV-226348r794632_rule
SV-52219

The POSIX subsystem is an Institute of Electrical and Electronic Engineers (IEEE) standard that defines a set of operating system services. The POSIX Subsystem is required if the server supports applications that use that subsystem. The subsystem introduces a security risk relating to processes that can potentially persist across logins. That is, if a user starts a process and then logs out, there is a potential that the next user who logs in to the system could access the previous users process. This is dangerous because the process started by the first user may retain that users system privileges, and anything the second user does with that process will be performed with the privileges of the first user.

Checks: C-28050r476888_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: \System\CurrentControlSet\Control\Session Manager\Subsystems\ Value Name: Optional Value Type: REG_MULTI_SZ Value: (Blank)

Fix: F-28038r476889_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "System settings: Optional subsystems" to "Blank" (Configured with no entries).

a

The print driver installation privilege must be restricted to administrators.

CM-11 - Low - CCI-001812 - V-226349 - SV-226349r794671_rule

RMF Control

CM-11

Severity

L

CCI

Version

WN12-SO-000089

Vuln IDs

V-226349
V-1151

Rule IDs

SV-226349r794671_rule
SV-52214

Allowing users to install drivers can introduce malware or cause the instability of a system. Print driver installation should be restricted to administrators.

Checks: C-28051r476891_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: \System\CurrentControlSet\Control\Print\Providers\LanMan Print Services\Servers\ Value Name: AddPrinterDrivers Value Type: REG_DWORD Value: 1

Fix: F-28039r476892_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Devices: Prevent users from installing printer drivers" to "Enabled".

b

Domain controllers must require LDAP access signing.

SC-8 - Medium - CCI-002418 - V-226350 - SV-226350r794677_rule

RMF Control

SC-8

Severity

M

CCI

Version

WN12-SO-000090-DC

Vuln IDs

V-226350
V-4407

Rule IDs

SV-226350r794677_rule
SV-51140

Unsigned network traffic is susceptible to man in the middle attacks where an intruder captures packets between the server and the client and modifies them before forwarding them to the client. In the case of an LDAP server, this means that an attacker could cause a client to make decisions based on false records from the LDAP directory. You can lower the risk of an attacker pulling this off in a corporate network by implementing strong physical security measures to protect the network infrastructure. Furthermore, implementing Internet Protocol security (IPSec) authentication header mode (AH), which performs mutual authentication and packet integrity for Internet Protocol (IP) traffic, can make all types of man in the middle attacks extremely difficult.

Checks: C-28052r476894_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: \System\CurrentControlSet\Services\NTDS\Parameters\ Value Name: LDAPServerIntegrity Value Type: REG_DWORD Value: 2

Fix: F-28040r476895_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".

a

Domain controllers must be configured to allow reset of machine account passwords.

CM-6 - Low - CCI-000366 - V-226351 - SV-226351r794683_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN12-SO-000091-DC

Vuln IDs

V-226351
V-4408

Rule IDs

SV-226351r794683_rule
SV-51141

Enabling this setting on all domain controllers in a domain prevents domain members from changing their computer account passwords. If these passwords are weak or compromised, the inability to change them may leave these computers vulnerable.

Checks: C-28053r476897_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: \System\CurrentControlSet\Services\Netlogon\Parameters\ Value Name: RefusePasswordChange Value Type: REG_DWORD Value: 0

Fix: F-28041r476898_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Domain controller: Refuse machine account password changes" to "Disabled".

b

Users must be required to enter a password to access private keys stored on the computer.

IA-5 - Medium - CCI-000186 - V-226352 - SV-226352r794622_rule

RMF Control

IA-5

Severity

M

CCI

CCI-000186

Version

WN12-SO-000092

Vuln IDs

V-226352
V-57639

Rule IDs

SV-226352r794622_rule
SV-72049

If the private key is discovered, an attacker can use the key to authenticate as an authorized user and gain access to the network infrastructure. The cornerstone of the PKI is the private key used to encrypt or digitally sign information. If the private key is stolen, this will lead to the compromise of the authentication and non-repudiation gained through PKI because the attacker can use the private key to digitally sign documents and pretend to be the authorized user. Both the holders of a digital certificate and the issuing authority must protect the computers, storage devices, or whatever they use to keep the private keys.

Checks: C-28054r476900_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\Cryptography\ Value Name: ForceKeyProtection Type: REG_DWORD Value: 2

Fix: F-28042r476901_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 on the computer" to "User must enter a password each time they use a key".

b

The Fax service must be disabled if installed.

CM-7 - Medium - CCI-000381 - V-226353 - SV-226353r794633_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-SV-000100

Vuln IDs

V-226353
V-26600

Rule IDs

SV-226353r794633_rule
SV-52236

Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption.

Checks: C-28055r476903_chk

Verify the Fax (fax) service is not installed or is disabled. Run "Services.msc". If the following is installed and not disabled, this is a finding: Fax (fax)

Fix: F-28043r476904_fix

Remove or disable the Fax (fax) service.

b

The Microsoft FTP service must not be installed unless required.

CM-7 - Medium - CCI-000382 - V-226354 - SV-226354r794640_rule

RMF Control

CM-7

Severity

M

CCI

CCI-000382

Version

WN12-SV-000101

Vuln IDs

V-226354
V-26602

Rule IDs

SV-226354r794640_rule
SV-52237

Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption.

Checks: C-28056r476906_chk

If the server has the role of an FTP server, this is NA. Run "Services.msc". If the "Microsoft FTP Service" (Service name: FTPSVC) is installed and not disabled, this is a finding.

Fix: F-28044r476907_fix

Remove or disable the "Microsoft FTP Service" (Service name: FTPSVC). To remove the "FTP Server" role from a system: Start "Server Manager" Select the server with the "FTP Server" role. Scroll down to "ROLES AND FEATURES" in the left pane. Select "Remove Roles and Features" from the drop down "TASKS" list. Select the appropriate server on the "Server Selection" page, click "Next". De-select "FTP Server" under "Web Server (IIS). Click "Next" and "Remove" as prompted.

b

The Peer Networking Identity Manager service must be disabled if installed.

CM-7 - Medium - CCI-000381 - V-226355 - SV-226355r794634_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-SV-000103

Vuln IDs

V-226355
V-26604

Rule IDs

SV-226355r794634_rule
SV-52238

Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption.

Checks: C-28057r476909_chk

Verify the Peer Network Identity Manager (p2pimsvc) service is not installed or is disabled. Run "Services.msc". If the following is installed and not disabled, this is a finding: Peer Networking Identity Manager (p2pimsvc)

Fix: F-28045r476910_fix

Remove or disable the Peer Networking Identity Manager (p2pimsvc) service.

b

The Simple TCP/IP Services service must be disabled if installed.

CM-7 - Medium - CCI-000381 - V-226356 - SV-226356r794635_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-SV-000104

Vuln IDs

V-226356
V-26605

Rule IDs

SV-226356r794635_rule
SV-52239

Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption.

Checks: C-28058r476912_chk

Verify the Simple TCP/IP (simptcp) service is not installed or is disabled. Run "Services.msc". If the following is installed and not disabled, this is a finding: Simple TCP/IP Services (simptcp)

Fix: F-28046r476913_fix

Remove or disable the Simple TCP/IP Services (simptcp) service.

b

The Telnet service must be disabled if installed.

CM-7 - Medium - CCI-000382 - V-226357 - SV-226357r794641_rule

RMF Control

CM-7

Severity

M

CCI

CCI-000382

Version

WN12-SV-000105

Vuln IDs

V-226357
V-26606

Rule IDs

SV-226357r794641_rule
SV-52240

Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption.

Checks: C-28059r476915_chk

Verify the Telnet (tlntsvr) service is not installed or is disabled. Run "Services.msc". If the following is installed and not disabled, this is a finding: Telnet (tlntsvr)

Fix: F-28047r476916_fix

Remove or disable the Telnet (tlntsvr) service.

b

The Smart Card Removal Policy service must be configured to automatic.

CM-6 - Medium - CCI-000366 - V-226358 - SV-226358r794684_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-SV-000106

Vuln IDs

V-226358
V-40206

Rule IDs

SV-226358r794684_rule
SV-52165

The automatic start of the Smart Card Removal Policy service is required to support the smart card removal behavior requirement.

Checks: C-28060r476918_chk

Verify the Smart Card Removal Policy service is configured to "Automatic". Run "Services.msc". If the Startup Type for Smart Card Removal Policy is not set to Automatic, this is a finding.

Fix: F-28048r476919_fix

Configure the Startup Type for the Smart Card Removal Policy service to "Automatic".

b

A screen saver must be enabled on the system.

AC-11 - Medium - CCI-000060 - V-226359 - SV-226359r794620_rule

RMF Control

AC-11

Severity

M

CCI

CCI-000060

Version

WN12-UC-000001

Vuln IDs

V-226359
V-36656

Rule IDs

SV-226359r794620_rule
SV-51758

Unattended systems are susceptible to unauthorized use and must be locked when unattended. Enabling a password-protected screen saver to engage after a specified period of time helps protects critical and sensitive data from exposure to unauthorized personnel with physical access to the computer.

Checks: C-28061r476921_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_CURRENT_USER Registry Path: \Software\Policies\Microsoft\Windows\Control Panel\Desktop\ Value Name: ScreenSaveActive Type: REG_SZ Value: 1 Applications requiring continuous, real-time screen display (e.g., network management products) require the following and must be documented with the ISSO: -The logon session does not have administrator rights. -The display station (e.g., keyboard, monitor, etc.) is located in a controlled access area.

Fix: F-28049r476922_fix

Configure the policy value for User Configuration -> Administrative Templates -> Control Panel -> Personalization -> "Enable screen saver" to "Enabled".

b

The screen saver must be password protected.

AC-11 - Medium - CCI-000056 - V-226360 - SV-226360r794619_rule

RMF Control

AC-11

Severity

M

CCI

CCI-000056

Version

WN12-UC-000003

Vuln IDs

V-226360
V-36657

Rule IDs

SV-226360r794619_rule
SV-51760

Unattended systems are susceptible to unauthorized use and must be locked when unattended. Enabling a password-protected screen saver to engage after a specified period of time helps protects critical and sensitive data from exposure to unauthorized personnel with physical access to the computer.

Checks: C-28062r476924_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_CURRENT_USER Registry Path: \Software\Policies\Microsoft\Windows\Control Panel\Desktop\ Value Name: ScreenSaverIsSecure Type: REG_SZ Value: 1

Fix: F-28050r476925_fix

Configure the policy value for User Configuration -> Administrative Templates -> Control Panel -> Personalization -> "Password protect the screen saver" to "Enabled".

a

Notifications from Windows Push Network Service must be turned off.

CM-7 - Low - CCI-000381 - V-226361 - SV-226361r794636_rule

RMF Control

CM-7

Severity

L

CCI

Version

WN12-UC-000005

Vuln IDs

V-226361
V-36776

Rule IDs

SV-226361r794636_rule
SV-51762

The Windows Push Notification Service (WNS) allows third-party vendors to send updates for toasts, tiles, and badges.

Checks: C-28063r476927_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_CURRENT_USER Registry Path: \SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\PushNotifications\ Value Name: NoCloudApplicationNotification Type: REG_DWORD Value: 1

Fix: F-28051r476928_fix

Configure the policy value for User Configuration -> Administrative Templates -> Start Menu and Taskbar -> Notifications -> "Turn off notifications network usage" to "Enabled".

a

Toast notifications to the lock screen must be turned off.

CM-7 - Low - CCI-000381 - V-226362 - SV-226362r794637_rule

RMF Control

CM-7

Severity

L

CCI

Version

WN12-UC-000006

Vuln IDs

V-226362
V-36777

Rule IDs

SV-226362r794637_rule
SV-51763

Toast notifications that are displayed on the lock screen could display sensitive information to unauthorized personnel. Turning off this feature will limit access to the information to a logged on user.

Checks: C-28064r476930_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_CURRENT_USER Registry Path: \SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\PushNotifications\ Value Name: NoToastApplicationNotificationOnLockScreen Type: REG_DWORD Value: 1

Fix: F-28052r476931_fix

Configure the policy value for User Configuration -> Administrative Templates -> Start Menu and Taskbar -> Notifications -> "Turn off toast notifications on the lock screen" to "Enabled".

b

The Windows Help Experience Improvement Program must be disabled.

CM-7 - Medium - CCI-000381 - V-226363 - SV-226363r794638_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-UC-000007

Vuln IDs

V-226363
V-16021

Rule IDs

SV-226363r794638_rule
SV-53144

Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. This setting ensures the Windows Help Experience Improvement Program is disabled to prevent information from being passed to the vendor.

Checks: C-28065r476933_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_CURRENT_USER Registry Path: \Software\Policies\Microsoft\Assistance\Client\1.0\ Value Name: NoImplicitFeedback Type: REG_DWORD Value: 1

Fix: F-28053r476934_fix

Configure the policy value for User Configuration -> Administrative Templates -> System -> Internet Communication Management -> Internet Communication Settings -> "Turn off Help Experience Improvement Program" to "Enabled".

b

Windows Help Ratings feedback must be turned off.

CM-7 - Medium - CCI-000381 - V-226364 - SV-226364r794639_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN12-UC-000008

Vuln IDs

V-226364
V-16048

Rule IDs

SV-226364r794639_rule
SV-53145

Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. This setting ensures users cannot provide ratings feedback to Microsoft for Help content.

Checks: C-28066r476936_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_CURRENT_USER Registry Path: \Software\Policies\Microsoft\Assistance\Client\1.0\ Value Name: NoExplicitFeedback Type: REG_DWORD Value: 1

Fix: F-28054r476937_fix

Configure the policy value for User Configuration -> Administrative Templates -> System -> Internet Communication Management -> Internet Communication Settings -> "Turn off Help Ratings" to "Enabled".

b

Zone information must be preserved when saving attachments.

CM-6 - Medium - CCI-000366 - V-226365 - SV-226365r794685_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-UC-000009

Vuln IDs

V-226365
V-14268

Rule IDs

SV-226365r794685_rule
SV-53002

Preserving zone of origin (internet, intranet, local, restricted) information on file attachments allows Windows to determine risk.

Checks: C-28067r476939_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_CURRENT_USER Registry Path: \Software\Microsoft\Windows\CurrentVersion\Policies\Attachments\ Value Name: SaveZoneInformation Type: REG_DWORD Value: 2

Fix: F-28055r476940_fix

Configure the policy value for User Configuration -> Administrative Templates -> Windows Components -> Attachment Manager -> "Do not preserve zone information in file attachments" to "Disabled".

b

Mechanisms for removing zone information from file attachments must be hidden.

CM-6 - Medium - CCI-000366 - V-226366 - SV-226366r794686_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-UC-000010

Vuln IDs

V-226366
V-14269

Rule IDs

SV-226366r794686_rule
SV-53004

Preserving zone of origin (internet, intranet, local, restricted) information on file attachments allows Windows to determine risk. This setting prevents users from manually removing zone information from saved file attachments.

Checks: C-28068r476942_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_CURRENT_USER Registry Path: \Software\Microsoft\Windows\CurrentVersion\Policies\Attachments\ Value Name: HideZoneInfoOnProperties Type: REG_DWORD Value: 1

Fix: F-28056r476943_fix

Configure the policy value for User Configuration -> Administrative Templates -> Windows Components -> Attachment Manager -> "Hide mechanisms to remove zone information" to "Enabled".

b

The system must notify antivirus when file attachments are opened.

CM-6 - Medium - CCI-000366 - V-226367 - SV-226367r794687_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-UC-000011

Vuln IDs

V-226367
V-14270

Rule IDs

SV-226367r794687_rule
SV-53006

Attaching malicious files is a known avenue of attack. This setting configures the system to notify antivirus programs when a user opens a file attachment.

Checks: C-28069r476945_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_CURRENT_USER Registry Path: \Software\Microsoft\Windows\CurrentVersion\Policies\Attachments\ Value Name: ScanWithAntiVirus Type: REG_DWORD Value: 3

Fix: F-28057r476946_fix

Configure the policy value for User Configuration -> Administrative Templates -> Windows Components -> Attachment Manager -> "Notify antivirus programs when opening attachments" to "Enabled".

b

Users must be prevented from sharing files in their profiles.

CM-6 - Medium - CCI-000366 - V-226368 - SV-226368r794688_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN12-UC-000012

Vuln IDs

V-226368
V-15727

Rule IDs

SV-226368r794688_rule
SV-53140

Allowing users to share files in their profiles may provide unauthorized access or result in the exposure of sensitive data.

Checks: C-28070r476948_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_CURRENT_USER Registry Path: \Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\ Value Name: NoInPlaceSharing Type: REG_DWORD Value: 1

Fix: F-28058r476949_fix

Configure the policy value for User Configuration -> Administrative Templates -> Windows Components -> Network Sharing -> "Prevent users from sharing files within their profile" to "Enabled".

b

Media Player must be configured to prevent automatic Codec downloads.

CM-11 - Medium - CCI-001812 - V-226369 - SV-226369r794672_rule

RMF Control

CM-11

Severity

M

CCI

Version

WN12-UC-000013

Vuln IDs

V-226369
V-3481

Rule IDs

SV-226369r794672_rule
SV-52921

The Windows Media Player uses software components, referred to as Codecs, to play back media files. By default, when an unknown file type is opened with the Media Player, it will search the Internet for the appropriate Codec and automatically download it. To ensure platform consistency and to protect against new vulnerabilities associated with media types, all Codecs must be installed by the System Administrator.

Checks: C-28071r476951_chk

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

Fix: F-28059r476952_fix

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

b

The Access Credential Manager as a trusted caller user right must not be assigned to any groups or accounts.

AC-6 - Medium - CCI-002235 - V-226370 - SV-226370r794649_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN12-UR-000001

Vuln IDs

V-226370
V-26469

Rule IDs

SV-226370r794649_rule
SV-53120

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Access Credential Manager as a trusted caller" user right may be able to retrieve the credentials of other accounts from Credential Manager.

Checks: C-28072r476954_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups are granted the "Access Credential Manager as a trusted caller" user right, this is a finding.

Fix: F-28060r476955_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Access Credential Manager as a trusted caller" to be defined but containing no entries (blank).

b

Unauthorized accounts must not have the Access this computer from the network user right on domain controllers.

AC-3 - Medium - CCI-000213 - V-226371 - SV-226371r794624_rule

RMF Control

AC-3

Severity

M

CCI

Version

WN12-UR-000002-DC

Vuln IDs

V-226371
V-26470

Rule IDs

SV-226371r794624_rule
SV-51142

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Access this computer from the network" right may access resources on the system and should be limited to those requiring it.

Checks: C-28073r476957_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment. If any accounts or groups other than the following are granted the "Access this computer from the network" right, this is a finding: Administrators Authenticated Users Enterprise Domain Controllers

Fix: F-28061r794623_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Access this computer from the network" to only include the following accounts or groups: Administrators Authenticated Users Enterprise Domain Controllers Severity Override Guidance: If an application requires this user right, this can be downgraded to not a finding if the following conditions are met: - Vendor documentation must support the requirement for having the user right. - The requirement must be documented with the ISSO. - The application account must meet requirements for application account passwords, such as length (V-36661) and required changes frequency (V-36662).

c

The Act as part of the operating system user right must not be assigned to any groups or accounts.

AC-6 - High - CCI-002235 - V-226372 - SV-226372r794650_rule

RMF Control

AC-6

Severity

H

CCI

Version

WN12-UR-000003

Vuln IDs

V-226372
V-1102

Rule IDs

SV-226372r794650_rule
SV-52108

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Act as part of the operating system" user right can assume the identity of any user and gain access to resources that user is authorized to access. Any accounts with this right can take complete control of a system.

Checks: C-28074r476960_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups (to include administrators), are granted the "Act as part of the operating system" user right, this is a finding. If an application requires this user right, this would not be a finding. Vendor documentation must support the requirement for having the user right. The requirement must be documented with the ISSO. The application account must meet requirements for application account passwords, such as length (WN12-00-000010) and required frequency of changes (WN12-00-000011).

Fix: F-28062r476961_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Act as part of the operating system" to be defined but containing no entries (blank).

b

The Allow log on locally user right must only be assigned to the Administrators group.

AC-3 - Medium - CCI-000213 - V-226373 - SV-226373r794625_rule

RMF Control

AC-3

Severity

M

CCI

Version

WN12-UR-000005

Vuln IDs

V-226373
V-26472

Rule IDs

SV-226373r794625_rule
SV-52110

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Allow log on locally" user right can log on interactively to a system.

Checks: C-28075r476963_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Allow log on locally" user right, this is a finding: Administrators If an application requires this user right, this would not be a finding. Vendor documentation must support the requirement for having the user right. The requirement must be documented with the ISSO. The application account must meet requirements for application account passwords, such as length (WN12-00-000010) and required frequency of changes (WN12-00-000011).

Fix: F-28063r476964_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Allow log on locally" to only include the following accounts or groups: Administrators

b

The Back up files and directories user right must only be assigned to the Administrators group.

AC-6 - Medium - CCI-002235 - V-226374 - SV-226374r794651_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN12-UR-000007

Vuln IDs

V-226374
V-26474

Rule IDs

SV-226374r794651_rule
SV-52111

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Back up files and directories" user right can circumvent file and directory permissions and could allow access to sensitive data.

Checks: C-28077r476968_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Back up files and directories" user right, this is a finding: Administrators If an application requires this user right, this would not be a finding. Vendor documentation must support the requirement for having the user right. The requirement must be documented with the ISSO. The application account must meet requirements for application account passwords, such as length (WN12-00-000010) and required frequency of changes (WN12-00-000011).

Fix: F-28065r476969_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Back up files and directories" to only include the following accounts or groups: Administrators

b

The Create a pagefile user right must only be assigned to the Administrators group.

AC-6 - Medium - CCI-002235 - V-226375 - SV-226375r794652_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN12-UR-000011

Vuln IDs

V-226375
V-26478

Rule IDs

SV-226375r794652_rule
SV-53063

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Create a pagefile" user right can change the size of a pagefile, which could affect system performance.

Checks: C-28078r476971_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Create a pagefile" user right, this is a finding: Administrators

Fix: F-28066r476972_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Create a pagefile" to only include the following accounts or groups: Administrators

c

The Create a token object user right must not be assigned to any groups or accounts.

AC-6 - High - CCI-002235 - V-226376 - SV-226376r794653_rule

RMF Control

AC-6

Severity

H

CCI

Version

WN12-UR-000012

Vuln IDs

V-226376
V-26479

Rule IDs

SV-226376r794653_rule
SV-52113

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. The "Create a token object" user right allows a process to create an access token. This could be used to provide elevated rights and compromise a system.

Checks: C-28079r476974_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups are granted the "Create a token object" user right, this is a finding. If an application requires this user right, this would not be a finding. Vendor documentation must support the requirement for having the user right. The requirement must be documented with the ISSO. The application account must meet requirements for application account passwords, such as length (WN12-00-000010) and required frequency of changes (WN12-00-000011).

Fix: F-28067r476975_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Create a token object" to be defined but containing no entries (blank).

b

The Create global objects user right must only be assigned to Administrators, Service, Local Service, and Network Service.

AC-6 - Medium - CCI-002235 - V-226377 - SV-226377r794654_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN12-UR-000013

Vuln IDs

V-226377
V-26480

Rule IDs

SV-226377r794654_rule
SV-52114

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Create global objects" user right can create objects that are available to all sessions, which could affect processes in other users' sessions.

Checks: C-28080r476977_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Create global objects" user right, this is a finding: Administrators Service Local Service Network Service If an application requires this user right, this would not be a finding. Vendor documentation must support the requirement for having the user right. The requirement must be documented with the ISSO. The application account must meet requirements for application account passwords, such as length (WN12-00-000010) and required frequency of changes (WN12-00-000011).

Fix: F-28068r476978_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Create global objects" to only include the following accounts or groups: Administrators Service Local Service Network Service

b

The Create permanent shared objects user right must not be assigned to any groups or accounts.

AC-6 - Medium - CCI-002235 - V-226378 - SV-226378r794655_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN12-UR-000014

Vuln IDs

V-226378
V-26481

Rule IDs

SV-226378r794655_rule
SV-53059

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Create permanent shared objects" user right could expose sensitive data by creating shared objects.

Checks: C-28081r476980_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups are granted the "Create permanent shared objects" user right, this is a finding.

Fix: F-28069r476981_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Create permanent shared objects" to be defined but containing no entries (blank).

b

The Create symbolic links user right must only be assigned to the Administrators group.

AC-6 - Medium - CCI-002235 - V-226379 - SV-226379r794656_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN12-UR-000015

Vuln IDs

V-226379
V-26482

Rule IDs

SV-226379r794656_rule
SV-53054

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Create symbolic links" user right can create pointers to other objects, which could potentially expose the system to attack.

Checks: C-28082r476983_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Create symbolic links" user right, this is a finding: Administrators Systems that have the Hyper-V role will also have "Virtual Machines" given this user right (this may be displayed as "NT Virtual Machine\Virtual Machines"). This is not a finding.

Fix: F-28070r476984_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Create symbolic links" to only include the following accounts or groups: Administrators Systems that have the Hyper-V role will also have "Virtual Machines" given this user right. If this needs to be added manually, enter it as "NT Virtual Machine\Virtual Machines".

c

The Debug programs user right must only be assigned to the Administrators group.

AC-6 - High - CCI-002235 - V-226380 - SV-226380r794657_rule

RMF Control

AC-6

Severity

H

CCI

Version

WN12-UR-000016

Vuln IDs

V-226380
V-18010

Rule IDs

SV-226380r794657_rule
SV-52115

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Debug programs" user right can attach a debugger to any process or to the kernel, providing complete access to sensitive and critical operating system components. This right is given to Administrators in the default configuration.

Checks: C-28083r476986_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Debug programs" user right, this is a finding: Administrators If an application requires this user right, this would not be a finding. Vendor documentation must support the requirement for having the user right. The requirement must be documented with the ISSO. The application account must meet requirements for application account passwords, such as length (WN12-00-000010) and required frequency of changes (WN12-00-000011).

Fix: F-28071r476987_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Debug programs" to only include the following accounts or groups: Administrators

b

The Deny access to this computer from the network user right on domain controllers must be configured to prevent unauthenticated access.

AC-3 - Medium - CCI-000213 - V-226381 - SV-226381r794626_rule

RMF Control

AC-3

Severity

M

CCI

Version

WN12-UR-000017-DC

Vuln IDs

V-226381
V-1155

Rule IDs

SV-226381r794626_rule
SV-51144

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. The "Deny access to this computer from the network" user right defines the accounts that are prevented from logging on from the network. The Guests group must be assigned this right to prevent unauthenticated access.

Checks: C-28084r476989_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment. If the following accounts or groups are not defined for the "Deny access to this computer from the network" user right, this is a finding: Guests Group

Fix: F-28072r476990_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Deny access to this computer from the network" to include the following: Guests Group

b

The Deny log on as a batch job user right on domain controllers must be configured to prevent unauthenticated access.

AC-3 - Medium - CCI-000213 - V-226382 - SV-226382r794627_rule

RMF Control

AC-3

Severity

M

CCI

Version

WN12-UR-000018-DC

Vuln IDs

V-226382
V-26483

Rule IDs

SV-226382r794627_rule
SV-51145

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. The "Deny log on as a batch job" user right defines accounts that are prevented from logging on to the system as a batch job, such as Task Scheduler. The Guests group must be assigned to prevent unauthenticated access.

Checks: C-28085r476992_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment. If the following accounts or groups are not defined for the "Deny log on as a batch job" user right, this is a finding: Guests Group

Fix: F-28073r476993_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

b

The Deny log on as a service user right must be configured to include no accounts or groups (blank) on domain controllers.

AC-3 - Medium - CCI-000213 - V-226383 - SV-226383r794628_rule

RMF Control

AC-3

Severity

M

CCI

Version

WN12-UR-000019-DC

Vuln IDs

V-226383
V-26484

Rule IDs

SV-226383r794628_rule
SV-51146

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. The "Deny log on as a service" user right defines accounts that are denied log on as a service. Incorrect configurations could prevent services from starting and result in a DoS.

Checks: C-28086r476995_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment. If any accounts or groups are defined for the "Deny log on as a service" user right, this is a finding.

Fix: F-28074r476996_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).

b

The Deny log on locally user right on domain controllers must be configured to prevent unauthenticated access.

AC-3 - Medium - CCI-000213 - V-226384 - SV-226384r794629_rule

RMF Control

AC-3

Severity

M

CCI

Version

WN12-UR-000020-DC

Vuln IDs

V-226384
V-26485

Rule IDs

SV-226384r794629_rule
SV-51147

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. The "Deny log on locally" user right defines accounts that are prevented from logging on interactively. The Guests group must be assigned this right to prevent unauthenticated access.

Checks: C-28087r476998_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment. If the following accounts or groups are not defined for the "Deny log on locally" user right, this is a finding: Guests Group

Fix: F-28075r476999_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

b

The Deny log on through Remote Desktop Services user right on domain controllers must be configured to prevent unauthenticated access.

AC-3 - Medium - CCI-000213 - V-226385 - SV-226385r794630_rule

RMF Control

AC-3

Severity

M

CCI

Version

WN12-UR-000021-DC

Vuln IDs

V-226385
V-26486

Rule IDs

SV-226385r794630_rule
SV-51148

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. The "Deny log on through Remote Desktop Services" user right defines the accounts that are prevented from logging on using Remote Desktop Services. The Guests group must be assigned this right to prevent unauthenticated access.

Checks: C-28088r477001_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment. If the following accounts or groups are not defined for the "Deny log on through Remote Desktop Services" user right, this is a finding: Guests Group

Fix: F-28076r477002_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Deny log on through Remote Desktop Services" to include the following: Guests Group

b

Unauthorized accounts must not have the Enable computer and user accounts to be trusted for delegation user right on domain controllers.

AC-6 - Medium - CCI-002235 - V-226386 - SV-226386r794658_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN12-UR-000022-DC

Vuln IDs

V-226386
V-26487

Rule IDs

SV-226386r794658_rule
SV-51149

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. The "Enable computer and user accounts to be trusted for delegation" user right allows the "Trusted for Delegation" setting to be changed. This could potentially allow unauthorized users to impersonate other users.

Checks: C-28089r477004_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment. If any accounts or groups other than the following are granted the "Enable computer and user accounts to be trusted for delegation" user right, this is a finding: Administrators

Fix: F-28077r477005_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Enable computer and user accounts to be trusted for delegation" to only include the following accounts or groups: Administrators

b

The Force shutdown from a remote system user right must only be assigned to the Administrators group.

AC-6 - Medium - CCI-002235 - V-226387 - SV-226387r794659_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN12-UR-000023

Vuln IDs

V-226387
V-26488

Rule IDs

SV-226387r794659_rule
SV-53050

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Force shutdown from a remote system" user right can remotely shut down a system, which could result in a DoS.

Checks: C-28090r477007_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Force shutdown from a remote system" user right, this is a finding: Administrators

Fix: F-28078r477008_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Force shutdown from a remote system" to only include the following accounts or groups: Administrators

b

The Generate security audits user right must only be assigned to Local Service and Network Service.

AC-6 - Medium - CCI-002235 - V-226388 - SV-226388r794660_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN12-UR-000024

Vuln IDs

V-226388
V-26489

Rule IDs

SV-226388r794660_rule
SV-52116

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. The "Generate security audits" user right specifies users and processes that can generate Security Log audit records, which must only be the system service accounts defined.

Checks: C-28091r477010_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Generate security audits" user right, this is a finding: Local Service Network Service If an application requires this user right, this would not be a finding. Vendor documentation must support the requirement for having the user right. The requirement must be documented with the ISSO. The application account must meet requirements for application account passwords, such as length (WN12-00-000010) and required frequency of changes (WN12-00-000011).

Fix: F-28079r477011_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Generate security audits" to only include the following accounts or groups: Local Service Network Service

b

The Impersonate a client after authentication user right must only be assigned to Administrators, Service, Local Service, and Network Service.

AC-6 - Medium - CCI-002235 - V-226389 - SV-226389r794661_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN12-UR-000025

Vuln IDs

V-226389
V-26490

Rule IDs

SV-226389r794661_rule
SV-52117

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. The "Impersonate a client after authentication" user right allows a program to impersonate another user or account to run on their behalf. An attacker could potentially use this to elevate privileges.

Checks: C-28092r477013_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Impersonate a client after authentication" user right, this is a finding: Administrators Service Local Service Network Service If an application requires this user right, this would not be a finding. Vendor documentation must support the requirement for having the user right. The requirement must be documented with the ISSO. The application account must meet requirements for application account passwords, such as length (WN12-00-000010) and required frequency of changes (WN12-00-000011).

Fix: F-28080r477014_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Impersonate a client after authentication" to only include the following accounts or groups: Administrators Service Local Service Network Service

b

The Increase scheduling priority user right must only be assigned to the Administrators group.

AC-6 - Medium - CCI-002235 - V-226390 - SV-226390r794662_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN12-UR-000027

Vuln IDs

V-226390
V-26492

Rule IDs

SV-226390r794662_rule
SV-52118

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Increase scheduling priority" user right can change a scheduling priority causing performance issues or a DoS.

Checks: C-28093r477016_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Increase scheduling priority" user right, this is a finding: Administrators If an application requires this user right, this would not be a finding. Vendor documentation must support the requirement for having the user right. The requirement must be documented with the ISSO. The application account must meet requirements for application account passwords, such as length (WN12-00-000010) and required frequency of changes (WN12-00-000011).

Fix: F-28081r477017_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Increase scheduling priority" to only include the following accounts or groups: Administrators

b

The Load and unload device drivers user right must only be assigned to the Administrators group.

AC-6 - Medium - CCI-002235 - V-226391 - SV-226391r794663_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN12-UR-000028

Vuln IDs

V-226391
V-26493

Rule IDs

SV-226391r794663_rule
SV-53043

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. The "Load and unload device drivers" user right allows device drivers to dynamically be loaded on a system by a user. This could potentially be used to install malicious code by an attacker.

Checks: C-28094r477019_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Load and unload device drivers" user right, this is a finding: Administrators

Fix: F-28082r477020_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Load and unload device drivers" to only include the following accounts or groups: Administrators

b

The Lock pages in memory user right must not be assigned to any groups or accounts.

AC-6 - Medium - CCI-002235 - V-226392 - SV-226392r794664_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN12-UR-000029

Vuln IDs

V-226392
V-26494

Rule IDs

SV-226392r794664_rule
SV-52119

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. The "Lock pages in memory" user right allows physical memory to be assigned to processes, which could cause performance issues or a DoS.

Checks: C-28095r477022_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups are granted the "Lock pages in memory" user right, this is a finding. If an application requires this user right, this would not be a finding. Vendor documentation must support the requirement for having the user right. The requirement must be documented with the ISSO. The application account must meet requirements for application account passwords, such as length (WN12-00-000010) and required frequency of changes (WN12-00-000011).

Fix: F-28083r477023_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Lock pages in memory" to be defined but containing no entries (blank).

b

The Manage auditing and security log user right must only be assigned to the Administrators group.

AU-9 - Medium - CCI-000162 - V-226393 - SV-226393r794621_rule

RMF Control

AU-9

Severity

M

CCI

Version

WN12-UR-000032

Vuln IDs

V-226393
V-26496

Rule IDs

SV-226393r794621_rule
SV-53039

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Manage auditing and security log" user right can manage the security log and change auditing configurations. This could be used to clear evidence of tampering.

Checks: C-28096r477025_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Manage auditing and security log" user right, this is a finding: Administrators If the organization has an Auditors group, the assignment of this group to the user right would not be a finding. If an application requires this user right, this would not be a finding. Vendor documentation must support the requirement for having the user right. The requirement must be documented with the ISSO. The application account must meet requirements for application account passwords, such as length (WN12-00-000010) and required frequency of changes (WN12-00-000011).

Fix: F-28084r477026_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Manage auditing and security log" to only include the following accounts or groups: Administrators

b

The Modify firmware environment values user right must only be assigned to the Administrators group.

AC-6 - Medium - CCI-002235 - V-226394 - SV-226394r794665_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN12-UR-000034

Vuln IDs

V-226394
V-26498

Rule IDs

SV-226394r794665_rule
SV-53029

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Modify firmware environment values" user right can change hardware configuration environment variables. This could result in hardware failures or a DoS.

Checks: C-28097r477028_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Modify firmware environment values" user right, this is a finding: Administrators

Fix: F-28085r477029_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Modify firmware environment values" to only include the following accounts or groups: Administrators

b

The Perform volume maintenance tasks user right must only be assigned to the Administrators group.

AC-6 - Medium - CCI-002235 - V-226395 - SV-226395r794666_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN12-UR-000035

Vuln IDs

V-226395
V-26499

Rule IDs

SV-226395r794666_rule
SV-53025

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Perform volume maintenance tasks" user right can manage volume and disk configurations. They could potentially delete volumes, resulting in data loss or a DoS.

Checks: C-28098r477031_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Perform volume maintenance tasks" user right, this is a finding: Administrators

Fix: F-28086r477032_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Perform volume maintenance tasks" to only include the following accounts or groups: Administrators

b

The Profile single process user right must only be assigned to the Administrators group.

AC-6 - Medium - CCI-002235 - V-226396 - SV-226396r794667_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN12-UR-000036

Vuln IDs

V-226396
V-26500

Rule IDs

SV-226396r794667_rule
SV-53022

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Profile single process" user right can monitor nonsystem processes performance. An attacker could potentially use this to identify processes to attack.

Checks: C-28099r477034_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Profile single process" user right, this is a finding: Administrators

Fix: F-28087r477035_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Profile single process" to only include the following accounts or groups: Administrators

b

The Restore files and directories user right must only be assigned to the Administrators group.

AC-6 - Medium - CCI-002235 - V-226397 - SV-226397r794668_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN12-UR-000040

Vuln IDs

V-226397
V-26504

Rule IDs

SV-226397r794668_rule
SV-52122

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Restore files and directories" user right can circumvent file and directory permissions and could allow access to sensitive data. It could also be used to overwrite more current data.

Checks: C-28100r477037_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Restore files and directories" user right, this is a finding: Administrators If an application requires this user right, this would not be a finding. Vendor documentation must support the requirement for having the user right. The requirement must be documented with the ISSO. The application account must meet requirements for application account passwords, such as length (WN12-00-000010) and required frequency of changes (WN12-00-000011).

Fix: F-28088r477038_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Restore files and directories" to only include the following accounts or groups: Administrators

b

The Take ownership of files or other objects user right must only be assigned to the Administrators group.

AC-6 - Medium - CCI-002235 - V-226398 - SV-226398r794669_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN12-UR-000042

Vuln IDs

V-226398
V-26506

Rule IDs

SV-226398r794669_rule
SV-52123

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Take ownership of files or other objects" user right can take ownership of objects and make changes.

Checks: C-28101r477040_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Take ownership of files or other objects" user right, this is a finding: Administrators If an application requires this user right, this would not be a finding. Vendor documentation must support the requirement for having the user right. The requirement must be documented with the ISSO. The application account must meet requirements for application account passwords, such as length (WN12-00-000010) and required frequency of changes (WN12-00-000011).

Fix: F-28089r477041_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Take ownership of files or other objects" to only include the following accounts or groups: Administrators

b

Unauthorized accounts must not have the Add workstations to domain user right.

AC-6 - Medium - CCI-002235 - V-226399 - SV-226399r794670_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN12-UR-000044-DC

Vuln IDs

V-226399
V-30016

Rule IDs

SV-226399r794670_rule
SV-51143

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Add workstations to domain" right may add computers to a domain. This could result in unapproved or incorrectly configured systems being added to a domain.

Checks: C-28102r477043_chk

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment. If any accounts or groups other than the following are granted the "Add workstations to domain" right, this is a finding: Administrators

Fix: F-28090r477044_fix

Configure the policy value for Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Add workstations to domain" to only include the following accounts or groups: Administrators

b

The Allow log on through Remote Desktop Services user right must only be assigned to the Administrators group.

AC-3 - Medium - CCI-000213 - V-226400 - SV-226400r794631_rule

RMF Control

AC-3

Severity

M

CCI