Microsoft Windows Server 2012/2012 R2 Member Server Security Technical Implementation Guide

  • Version/Release: V3R7
  • Published: 2023-08-21
  • Expand All:
  • Severity:
  • Sort:
Compare

Select any two versions of this STIG to compare the individual requirements

View

Select any old version/release of this STIG to view the previous requirements

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.
b
Server systems must be located in a controlled access area, accessible only to authorized personnel.
CM-6 - Medium - CCI-000366 - V-225239 - SV-225239r877377_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-00-000001
Vuln IDs
  • V-225239
  • V-1070
Rule IDs
  • SV-225239r877377_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-26938r471059_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-26926r471060_fix

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

b
Users with administrative privilege must be documented.
CM-6 - Medium - CCI-000366 - V-225240 - SV-225240r569185_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-00-000004
Vuln IDs
  • V-225240
  • V-36658
Rule IDs
  • SV-225240r569185_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-26939r471062_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-26927r471063_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-225241 - SV-225241r569185_rule
RMF Control
CM-6
Severity
High
CCI
CCI-000366
Version
WN12-00-000005
Vuln IDs
  • V-225241
  • V-36659
Rule IDs
  • SV-225241r569185_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-26940r471065_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-26928r471066_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-225242 - SV-225242r569185_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-00-000006
Vuln IDs
  • V-225242
  • V-36666
Rule IDs
  • SV-225242r569185_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-26941r471068_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-26929r471069_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-225243 - SV-225243r793246_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-00-000007
Vuln IDs
  • V-225243
  • V-14225
Rule IDs
  • SV-225243r793246_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-26942r471071_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-26930r793245_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 on domain-joined member servers to accomplish this. The AO still has the overall authority to use another equivalent capability to accomplish the check.

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-225244 - SV-225244r569185_rule
RMF Control
CM-6
Severity
High
CCI
CCI-000366
Version
WN12-00-000008
Vuln IDs
  • V-225244
  • V-36451
Rule IDs
  • SV-225244r569185_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-26943r471074_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-26931r471075_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-225245 - SV-225245r569185_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-00-000009-01
Vuln IDs
  • V-225245
  • V-1168
Rule IDs
  • SV-225245r569185_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-26944r471077_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-26932r471078_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-225246 - SV-225246r569185_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-00-000009-02
Vuln IDs
  • V-225246
  • V-40198
Rule IDs
  • SV-225246r569185_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-26945r471080_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-26933r471081_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-225247 - SV-225247r569185_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000205
Version
WN12-00-000010
Vuln IDs
  • V-225247
  • V-36661
Rule IDs
  • SV-225247r569185_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-26946r471083_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-26934r471084_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-225248 - SV-225248r569185_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-00-000011
Vuln IDs
  • V-225248
  • V-36662
Rule IDs
  • SV-225248r569185_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-26947r471086_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-26935r471087_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-225249 - SV-225249r569185_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000764
Version
WN12-00-000012
Vuln IDs
  • V-225249
  • V-1072
Rule IDs
  • SV-225249r569185_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-26948r471089_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-26936r471090_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-225250 - SV-225250r569185_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
WN12-00-000013
Vuln IDs
  • V-225250
  • V-1128
Rule IDs
  • SV-225250r569185_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-26949r471092_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-26937r471093_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-225251 - SV-225251r569185_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
WN12-00-000014
Vuln IDs
  • V-225251
  • V-1076
Rule IDs
  • SV-225251r569185_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-26950r471095_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-26938r471096_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-225252 - SV-225252r569185_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
WN12-00-000015
Vuln IDs
  • V-225252
  • V-36733
Rule IDs
  • SV-225252r569185_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-26951r471098_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-26939r471099_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-225253 - SV-225253r569185_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
WN12-00-000016
Vuln IDs
  • V-225253
  • V-40172
Rule IDs
  • SV-225253r569185_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-26952r471101_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-26940r471102_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-225254 - SV-225254r569185_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
WN12-00-000017
Vuln IDs
  • V-225254
  • V-40173
Rule IDs
  • SV-225254r569185_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-26953r471104_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-26941r471105_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-225255 - SV-225255r890489_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-001774
Version
WN12-00-000018
Vuln IDs
  • V-225255
  • V-57637
Rule IDs
  • SV-225255r890489_rule
  • SV-72047
Utilizing an allowlist 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 allowlisting.
Checks: C-26954r890487_chk

Verify the operating system employs a deny-all, permit-by-exception policy to allow the execution of authorized software programs. If an application allowlisting program is not in use on the system, this is a finding. Configuration of allowlisting applications will vary by the program. AppLocker is an allowlisting 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 at the following link: https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-application-control/applocker/applocker-policies-deployment-guide

Fix: F-26942r890488_fix

Configure an application allowlisting program to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs. Configuration of allowlisting applications will vary by the program. AppLocker is an allowlisting 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 at the following link: https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-application-control/applocker/applocker-policies-deployment-guide

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-225256 - SV-225256r852180_rule
RMF Control
SC-8
Severity
Medium
CCI
CCI-002420
Version
WN12-00-000019
Vuln IDs
  • V-225256
  • V-57641
Rule IDs
  • SV-225256r852180_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-26955r471110_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-26943r471111_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-225257 - SV-225257r852181_rule
RMF Control
SC-28
Severity
Medium
CCI
CCI-001199
Version
WN12-00-000020
Vuln IDs
  • V-225257
  • V-57645
Rule IDs
  • SV-225257r852181_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-26956r471113_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-26944r471114_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-225258 - SV-225258r569185_rule
RMF Control
CM-6
Severity
High
CCI
CCI-000366
Version
WN12-00-000100
Vuln IDs
  • V-225258
  • V-1074
Rule IDs
  • SV-225258r569185_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-26957r471116_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-26945r471117_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-225259 - SV-225259r569185_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
WN12-00-000160
Vuln IDs
  • V-225259
  • V-73805
Rule IDs
  • SV-225259r569185_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-26958r471119_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-26946r471120_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-225260 - SV-225260r569185_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
WN12-00-000170
Vuln IDs
  • V-225260
  • V-73519
Rule IDs
  • SV-225260r569185_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-26959r471122_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-26947r471123_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-225261 - SV-225261r569185_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
WN12-00-000180
Vuln IDs
  • V-225261
  • V-73523
Rule IDs
  • SV-225261r569185_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-26960r471125_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-26948r471126_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-225262 - SV-225262r569185_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-00-000190
Vuln IDs
  • V-225262
  • V-75915
Rule IDs
  • SV-225262r569185_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-26961r471128_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-26949r471129_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-225263 - SV-225263r569185_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-00-000200
Vuln IDs
  • V-225263
  • V-80473
Rule IDs
  • SV-225263r569185_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-26962r471131_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-26950r471132_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 Windows Management Framework (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-225264 - SV-225264r569185_rule
RMF Control
AU-3
Severity
Medium
CCI
CCI-000135
Version
WN12-00-000210
Vuln IDs
  • V-225264
  • V-80475
Rule IDs
  • SV-225264r569185_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-26963r471134_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-26951r471135_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-225265 - SV-225265r569185_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
WN12-00-000220
Vuln IDs
  • V-225265
  • V-80477
Rule IDs
  • SV-225265r569185_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-26964r471137_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-26952r471138_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-225266 - SV-225266r852182_rule
RMF Control
AC-7
Severity
Medium
CCI
CCI-002238
Version
WN12-AC-000001
Vuln IDs
  • V-225266
  • V-1099
Rule IDs
  • SV-225266r852182_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-26965r471140_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-26953r471141_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-225267 - SV-225267r569185_rule
RMF Control
AC-7
Severity
Medium
CCI
CCI-000044
Version
WN12-AC-000002
Vuln IDs
  • V-225267
  • V-1097
Rule IDs
  • SV-225267r569185_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-26966r471143_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-26954r471144_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-225268 - SV-225268r852183_rule
RMF Control
AC-7
Severity
Medium
CCI
CCI-000044
Version
WN12-AC-000003
Vuln IDs
  • V-225268
  • V-1098
Rule IDs
  • SV-225268r852183_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-26967r471146_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-26955r471147_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-225269 - SV-225269r569185_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000200
Version
WN12-AC-000004
Vuln IDs
  • V-225269
  • V-1107
Rule IDs
  • SV-225269r569185_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-26968r471149_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-26956r471150_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-225270 - SV-225270r569185_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000199
Version
WN12-AC-000005
Vuln IDs
  • V-225270
  • V-1104
Rule IDs
  • SV-225270r569185_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-26969r471152_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-26957r471153_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-225271 - SV-225271r569185_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000198
Version
WN12-AC-000006
Vuln IDs
  • V-225271
  • V-1105
Rule IDs
  • SV-225271r569185_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-26970r471155_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-26958r471156_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-225272 - SV-225272r569185_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000205
Version
WN12-AC-000007
Vuln IDs
  • V-225272
  • V-6836
Rule IDs
  • SV-225272r569185_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-26971r471158_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-26959r471159_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-225273 - SV-225273r569185_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000192
Version
WN12-AC-000008
Vuln IDs
  • V-225273
  • V-1150
Rule IDs
  • SV-225273r569185_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-26972r471161_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-26960r471162_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-225274 - SV-225274r877397_rule
RMF Control
IA-5
Severity
High
CCI
CCI-000196
Version
WN12-AC-000009
Vuln IDs
  • V-225274
  • V-2372
Rule IDs
  • SV-225274r877397_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-26973r471164_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-26961r471165_fix

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

b
The system must be configured to audit Account Logon - Credential Validation successes.
AU-12 - Medium - CCI-000172 - V-225275 - SV-225275r569185_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
WN12-AU-000001
Vuln IDs
  • V-225275
  • V-26529
Rule IDs
  • SV-225275r569185_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-26974r471167_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-26962r471168_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-225276 - SV-225276r569185_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
WN12-AU-000002
Vuln IDs
  • V-225276
  • V-26530
Rule IDs
  • SV-225276r569185_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-26975r471170_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-26963r471171_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
The system must be configured to audit Account Management - Other Account Management Events successes.
AU-12 - Medium - CCI-000172 - V-225277 - SV-225277r852184_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
WN12-AU-000015
Vuln IDs
  • V-225277
  • V-26533
Rule IDs
  • SV-225277r852184_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-26976r471173_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-26964r471174_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-225278 - SV-225278r852185_rule
RMF Control
AC-2
Severity
Medium
CCI
CCI-000018
Version
WN12-AU-000017
Vuln IDs
  • V-225278
  • V-26535
Rule IDs
  • SV-225278r852185_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-26977r471176_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-26965r471177_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-225279 - SV-225279r852186_rule
RMF Control
AC-2
Severity
Medium
CCI
CCI-000018
Version
WN12-AU-000019
Vuln IDs
  • V-225279
  • V-26537
Rule IDs
  • SV-225279r852186_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-26978r471179_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-26966r471180_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-225280 - SV-225280r852187_rule
RMF Control
AC-2
Severity
Medium
CCI
CCI-000018
Version
WN12-AU-000020
Vuln IDs
  • V-225280
  • V-26538
Rule IDs
  • SV-225280r852187_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-26979r471182_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-26967r471183_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-225281 - SV-225281r569185_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
WN12-AU-000023
Vuln IDs
  • V-225281
  • V-26539
Rule IDs
  • SV-225281r569185_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-26980r471185_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-26968r471186_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 failures.
AU-12 - Medium - CCI-000172 - V-225283 - SV-225283r569185_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
WN12-AU-000031
Vuln IDs
  • V-225283
  • V-78059
Rule IDs
  • SV-225283r569185_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-26982r471191_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-26970r471192_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 Logon/Logoff - Logoff successes.
AC-17 - Medium - CCI-000067 - V-225284 - SV-225284r569185_rule
RMF Control
AC-17
Severity
Medium
CCI
CCI-000067
Version
WN12-AU-000045
Vuln IDs
  • V-225284
  • V-26540
Rule IDs
  • SV-225284r569185_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-26983r471194_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-26971r471195_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-225285 - SV-225285r569185_rule
RMF Control
AC-17
Severity
Medium
CCI
CCI-000067
Version
WN12-AU-000047
Vuln IDs
  • V-225285
  • V-26541
Rule IDs
  • SV-225285r569185_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-26984r471197_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-26972r471198_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-225286 - SV-225286r569185_rule
RMF Control
AC-17
Severity
Medium
CCI
CCI-000067
Version
WN12-AU-000048
Vuln IDs
  • V-225286
  • V-26542
Rule IDs
  • SV-225286r569185_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-26985r471200_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-26973r471201_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-225287 - SV-225287r569185_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
WN12-AU-000053
Vuln IDs
  • V-225287
  • V-26543
Rule IDs
  • SV-225287r569185_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-26986r471203_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-26974r471204_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-225288 - SV-225288r569185_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
WN12-AU-000059
Vuln IDs
  • V-225288
  • V-40202
Rule IDs
  • SV-225288r569185_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-26987r471206_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-26975r471207_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-225289 - SV-225289r569185_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
WN12-AU-000060
Vuln IDs
  • V-225289
  • V-40200
Rule IDs
  • SV-225289r569185_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-26988r471209_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-26976r471210_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-225290 - SV-225290r569185_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
WN12-AU-000081
Vuln IDs
  • V-225290
  • V-36668
Rule IDs
  • SV-225290r569185_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-26989r471212_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-26977r471213_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-225291 - SV-225291r569185_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
WN12-AU-000082
Vuln IDs
  • V-225291
  • V-36667
Rule IDs
  • SV-225291r569185_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-26990r471215_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-26978r471216_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-225292 - SV-225292r569185_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
WN12-AU-000085
Vuln IDs
  • V-225292
  • V-26546
Rule IDs
  • SV-225292r569185_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-26991r471218_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-26979r471219_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-225293 - SV-225293r852188_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
WN12-AU-000086
Vuln IDs
  • V-225293
  • V-26547
Rule IDs
  • SV-225293r852188_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-26992r471221_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-26980r471222_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-225294 - SV-225294r852189_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
WN12-AU-000087
Vuln IDs
  • V-225294
  • V-26548
Rule IDs
  • SV-225294r852189_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-26993r471224_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-26981r471225_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-225295 - SV-225295r569185_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
WN12-AU-000089
Vuln IDs
  • V-225295
  • V-57633
Rule IDs
  • SV-225295r569185_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-26994r471227_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-26982r471228_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-225296 - SV-225296r852190_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
WN12-AU-000101
Vuln IDs
  • V-225296
  • V-26549
Rule IDs
  • SV-225296r852190_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-26995r471230_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-26983r471231_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-225297 - SV-225297r852191_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
WN12-AU-000102
Vuln IDs
  • V-225297
  • V-26550
Rule IDs
  • SV-225297r852191_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-26996r471233_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-26984r471234_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-225298 - SV-225298r569185_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
WN12-AU-000103
Vuln IDs
  • V-225298
  • V-26551
Rule IDs
  • SV-225298r569185_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-26997r471236_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-26985r471237_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-225299 - SV-225299r569185_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
WN12-AU-000104
Vuln IDs
  • V-225299
  • V-26552
Rule IDs
  • SV-225299r569185_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-26998r471239_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-26986r471240_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-225300 - SV-225300r852192_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
WN12-AU-000105
Vuln IDs
  • V-225300
  • V-78061
Rule IDs
  • SV-225300r852192_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-26999r471242_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-26987r471243_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-225301 - SV-225301r852193_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
WN12-AU-000106
Vuln IDs
  • V-225301
  • V-78063
Rule IDs
  • SV-225301r852193_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-27000r471245_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-26988r471246_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-225302 - SV-225302r852194_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
WN12-AU-000107
Vuln IDs
  • V-225302
  • V-26553
Rule IDs
  • SV-225302r852194_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-27001r471248_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-26989r471249_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-225303 - SV-225303r852195_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
WN12-AU-000109
Vuln IDs
  • V-225303
  • V-26555
Rule IDs
  • SV-225303r852195_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-27002r471251_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-26990r471252_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-225304 - SV-225304r852196_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
WN12-AU-000111
Vuln IDs
  • V-225304
  • V-26557
Rule IDs
  • SV-225304r852196_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-27003r471254_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-26991r471255_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-225305 - SV-225305r852197_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
WN12-AU-000112
Vuln IDs
  • V-225305
  • V-26558
Rule IDs
  • SV-225305r852197_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-27004r471257_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-26992r471258_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-225306 - SV-225306r569185_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-AU-000200
Vuln IDs
  • V-225306
  • V-36670
Rule IDs
  • SV-225306r569185_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-27005r471260_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-26993r471261_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-225307 - SV-225307r569185_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-AU-000201
Vuln IDs
  • V-225307
  • V-36671
Rule IDs
  • SV-225307r569185_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-27006r471263_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-26994r471264_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-225308 - SV-225308r877390_rule
RMF Control
AU-4
Severity
Medium
CCI
CCI-001851
Version
WN12-AU-000203-01
Vuln IDs
  • V-225308
  • V-36672
Rule IDs
  • SV-225308r877390_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-27007r471266_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-26995r471267_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-225309 - SV-225309r877390_rule
RMF Control
AU-4
Severity
Medium
CCI
CCI-001851
Version
WN12-AU-000203-02
Vuln IDs
  • V-225309
  • V-57719
Rule IDs
  • SV-225309r877390_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-27008r471269_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-26996r471270_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-225310 - SV-225310r569185_rule
RMF Control
AU-9
Severity
Medium
CCI
CCI-000162
Version
WN12-AU-000204
Vuln IDs
  • V-225310
  • V-36722
Rule IDs
  • SV-225310r569185_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-27009r471272_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-26997r471273_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-225311 - SV-225311r569185_rule
RMF Control
AU-9
Severity
Medium
CCI
CCI-000162
Version
WN12-AU-000205
Vuln IDs
  • V-225311
  • V-36723
Rule IDs
  • SV-225311r569185_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-27010r471275_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-26998r471276_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-225312 - SV-225312r569185_rule
RMF Control
AU-9
Severity
Medium
CCI
CCI-000162
Version
WN12-AU-000206
Vuln IDs
  • V-225312
  • V-36724
Rule IDs
  • SV-225312r569185_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-27011r471278_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-26999r471279_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
Event Viewer must be protected from unauthorized modification and deletion.
AU-9 - Medium - CCI-001494 - V-225313 - SV-225313r569185_rule
RMF Control
AU-9
Severity
Medium
CCI
CCI-001494
Version
WN12-AU-000213
Vuln IDs
  • V-225313
  • V-57721
Rule IDs
  • SV-225313r569185_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-27012r471281_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-27000r471282_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-225314 - SV-225314r569185_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
WN12-CC-000001
Vuln IDs
  • V-225314
  • V-15696
Rule IDs
  • SV-225314r569185_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-27013r471284_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-27001r471285_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-225315 - SV-225315r569185_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
WN12-CC-000002
Vuln IDs
  • V-225315
  • V-15697
Rule IDs
  • SV-225315r569185_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-27014r471287_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-27002r471288_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-225316 - SV-225316r569185_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
WN12-CC-000003
Vuln IDs
  • V-225316
  • V-15666
Rule IDs
  • SV-225316r569185_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-27015r471290_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-27003r471291_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-225317 - SV-225317r569185_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
WN12-CC-000004
Vuln IDs
  • V-225317
  • V-15667
Rule IDs
  • SV-225317r569185_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-27016r471293_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-27004r471294_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-225318 - SV-225318r569185_rule
RMF Control
SC-3
Severity
Low
CCI
CCI-001084
Version
WN12-CC-000005
Vuln IDs
  • V-225318
  • V-21960
Rule IDs
  • SV-225318r569185_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-27017r471296_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-27005r471297_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-225319 - SV-225319r569185_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
WN12-CC-000006
Vuln IDs
  • V-225319
  • V-21961
Rule IDs
  • SV-225319r569185_rule
  • SV-53183
Routing all Direct Access traffic through the internal network allows monitoring and prevents split tunneling.
Checks: C-27018r471299_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-27006r471300_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-225324 - SV-225324r569185_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
WN12-CC-000011
Vuln IDs
  • V-225324
  • V-36673
Rule IDs
  • SV-225324r569185_rule
  • SV-51605
IP stateless autoconfiguration could configure routes that circumvent preferred routes if not limited.
Checks: C-27023r471314_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-27011r471315_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-225325 - SV-225325r569185_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
WN12-CC-000012
Vuln IDs
  • V-225325
  • V-15698
Rule IDs
  • SV-225325r569185_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-27024r471317_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-27012r471318_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-225326 - SV-225326r569185_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
WN12-CC-000013
Vuln IDs
  • V-225326
  • V-15699
Rule IDs
  • SV-225326r569185_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-27025r471320_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-27013r471321_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-225327 - SV-225327r852200_rule
RMF Control
CM-11
Severity
Low
CCI
CCI-001812
Version
WN12-CC-000016
Vuln IDs
  • V-225327
  • V-21963
Rule IDs
  • SV-225327r852200_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-27026r471323_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-27014r471324_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-225328 - SV-225328r852201_rule
RMF Control
CM-11
Severity
Low
CCI
CCI-001812
Version
WN12-CC-000018
Vuln IDs
  • V-225328
  • V-36677
Rule IDs
  • SV-225328r852201_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-27027r471326_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-27015r471327_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-225329 - SV-225329r569185_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
WN12-CC-000019
Vuln IDs
  • V-225329
  • V-15700
Rule IDs
  • SV-225329r569185_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-27028r471329_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-27016r471330_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-225330 - SV-225330r569185_rule
RMF Control
CM-7
Severity
Low
CCI
CCI-000381
Version
WN12-CC-000020
Vuln IDs
  • V-225330
  • V-15702
Rule IDs
  • SV-225330r569185_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-27029r471332_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-27017r471333_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-225331 - SV-225331r569185_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
WN12-CC-000021
Vuln IDs
  • V-225331
  • V-15701
Rule IDs
  • SV-225331r569185_rule
  • SV-53099
A system restore point allows a rollback if an issue is encountered when a new device driver is installed.
Checks: C-27030r471335_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-27018r471336_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-225332 - SV-225332r569185_rule
RMF Control
CM-7
Severity
Low
CCI
CCI-000381
Version
WN12-CC-000022
Vuln IDs
  • V-225332
  • V-21964
Rule IDs
  • SV-225332r569185_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-27031r471338_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-27019r471339_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-225333 - SV-225333r569185_rule
RMF Control
CM-7
Severity
Low
CCI
CCI-000381
Version
WN12-CC-000023
Vuln IDs
  • V-225333
  • V-28504
Rule IDs
  • SV-225333r569185_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-27032r471341_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-27020r471342_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-225334 - SV-225334r852202_rule
RMF Control
CM-11
Severity
Low
CCI
CCI-001812
Version
WN12-CC-000024
Vuln IDs
  • V-225334
  • V-21965
Rule IDs
  • SV-225334r852202_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-27033r471344_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-27021r471345_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-225335 - SV-225335r852203_rule
RMF Control
CM-11
Severity
Low
CCI
CCI-001812
Version
WN12-CC-000025
Vuln IDs
  • V-225335
  • V-36678
Rule IDs
  • SV-225335r852203_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-27034r471347_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-27022r471348_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-225336 - SV-225336r852204_rule
RMF Control
CM-11
Severity
Low
CCI
CCI-001812
Version
WN12-CC-000026
Vuln IDs
  • V-225336
  • V-15703
Rule IDs
  • SV-225336r852204_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-27035r471350_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-27023r471351_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-225337 - SV-225337r569185_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-CC-000027
Vuln IDs
  • V-225337
  • V-36679
Rule IDs
  • SV-225337r569185_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-27036r471353_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-27024r471354_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-225338 - SV-225338r569185_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-CC-000028
Vuln IDs
  • V-225338
  • V-4448
Rule IDs
  • SV-225338r569185_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-27037r471356_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-27025r471357_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-225339 - SV-225339r569185_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-CC-000029
Vuln IDs
  • V-225339
  • V-3469
Rule IDs
  • SV-225339r569185_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-27038r471359_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-27026r471360_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-225340 - SV-225340r569185_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-CC-000030
Vuln IDs
  • V-225340
  • V-36680
Rule IDs
  • SV-225340r569185_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-27039r471362_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-27027r471363_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-225341 - SV-225341r569185_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
WN12-CC-000032
Vuln IDs
  • V-225341
  • V-14260
Rule IDs
  • SV-225341r569185_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-27040r471365_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-27028r471366_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-225342 - SV-225342r569185_rule
RMF Control
CM-7
Severity
Low
CCI
CCI-000381
Version
WN12-CC-000033
Vuln IDs
  • V-225342
  • V-15672
Rule IDs
  • SV-225342r569185_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-27041r471368_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-27029r471369_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-225343 - SV-225343r569185_rule
RMF Control
CM-7
Severity
Low
CCI
CCI-000381
Version
WN12-CC-000035
Vuln IDs
  • V-225343
  • V-15704
Rule IDs
  • SV-225343r569185_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-27042r471371_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-27030r471372_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-225344 - SV-225344r569185_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
WN12-CC-000038
Vuln IDs
  • V-225344
  • V-15674
Rule IDs
  • SV-225344r569185_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-27043r471374_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-27031r471375_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-225345 - SV-225345r569185_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
WN12-CC-000039
Vuln IDs
  • V-225345
  • V-14259
Rule IDs
  • SV-225345r569185_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-27044r471377_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-27032r471378_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-225346 - SV-225346r569185_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
WN12-CC-000045
Vuln IDs
  • V-225346
  • V-16020
Rule IDs
  • SV-225346r569185_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-27045r471380_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-27033r471381_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-225347 - SV-225347r852205_rule
RMF Control
CM-11
Severity
Medium
CCI
CCI-001812
Version
WN12-CC-000047
Vuln IDs
  • V-225347
  • V-14261
Rule IDs
  • SV-225347r852205_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-27046r471383_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-27034r471384_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-225348 - SV-225348r569185_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
WN12-CC-000048
Vuln IDs
  • V-225348
  • V-36681
Rule IDs
  • SV-225348r569185_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-27047r471386_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-27035r471387_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-225349 - SV-225349r569185_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
WN12-CC-000051
Vuln IDs
  • V-225349
  • V-36684
Rule IDs
  • SV-225349r569185_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-27048r471389_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-27036r471390_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-225350 - SV-225350r569185_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
WN12-CC-000052
Vuln IDs
  • V-225350
  • V-36687
Rule IDs
  • SV-225350r569185_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-27049r471392_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-27037r471393_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-225351 - SV-225351r852206_rule
RMF Control
IA-11
Severity
Medium
CCI
CCI-002038
Version
WN12-CC-000054
Vuln IDs
  • V-225351
  • V-15705
Rule IDs
  • SV-225351r852206_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-27050r471395_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-27038r471396_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-225352 - SV-225352r852207_rule
RMF Control
IA-11
Severity
Medium
CCI
CCI-002038
Version
WN12-CC-000055
Vuln IDs
  • V-225352
  • V-15706
Rule IDs
  • SV-225352r852207_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-27051r471398_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-27039r471399_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-225353 - SV-225353r569185_rule
RMF Control
SC-4
Severity
Medium
CCI
CCI-001090
Version
WN12-CC-000058
Vuln IDs
  • V-225353
  • V-3470
Rule IDs
  • SV-225353r569185_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-27052r471401_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-27040r471402_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-225354 - SV-225354r569185_rule
RMF Control
SC-4
Severity
High
CCI
CCI-001090
Version
WN12-CC-000059
Vuln IDs
  • V-225354
  • V-3343
Rule IDs
  • SV-225354r569185_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-27053r471404_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-27041r471405_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-225355 - SV-225355r569185_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
WN12-CC-000062
Vuln IDs
  • V-225355
  • V-15707
Rule IDs
  • SV-225355r569185_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-27054r471407_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-27042r471408_fix

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

b
Unauthenticated RPC clients must be restricted from connecting to the RPC server.
IA-3 - Medium - CCI-001967 - V-225356 - SV-225356r877039_rule
RMF Control
IA-3
Severity
Medium
CCI
CCI-001967
Version
WN12-CC-000064-MS
Vuln IDs
  • V-225356
  • V-14253
Rule IDs
  • SV-225356r877039_rule
  • SV-52988
Configuring RPC to restrict unauthenticated RPC clients from connecting to the RPC server will prevent anonymous connections.
Checks: C-27055r471410_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\Rpc\ Value Name: RestrictRemoteClients Type: REG_DWORD Value: 1

Fix: F-27043r471411_fix

Configure the policy value for Computer Configuration -> Administrative Templates -> System -> Remote Procedure Call -> "Restrict Unauthenticated RPC clients" to "Enabled" and "Authenticated".

a
The detection of compatibility issues for applications and drivers must be turned off.
CM-7 - Low - CCI-000381 - V-225357 - SV-225357r569185_rule
RMF Control
CM-7
Severity
Low
CCI
CCI-000381
Version
WN12-CC-000065
Vuln IDs
  • V-225357
  • V-36696
Rule IDs
  • SV-225357r569185_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-27056r471413_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-27044r471414_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-225358 - SV-225358r569185_rule
RMF Control
CM-7
Severity
Low
CCI
CCI-000381
Version
WN12-CC-000066
Vuln IDs
  • V-225358
  • V-21967
Rule IDs
  • SV-225358r569185_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-27057r471416_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-27045r471417_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-225359 - SV-225359r569185_rule
RMF Control
CM-7
Severity
Low
CCI
CCI-000381
Version
WN12-CC-000067
Vuln IDs
  • V-225359
  • V-21969
Rule IDs
  • SV-225359r569185_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-27058r471419_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-27046r471420_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-225360 - SV-225360r569185_rule
RMF Control
CM-7
Severity
Low
CCI
CCI-000381
Version
WN12-CC-000068
Vuln IDs
  • V-225360
  • V-21970
Rule IDs
  • SV-225360r569185_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-27059r471422_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-27047r471423_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-225361 - SV-225361r877038_rule
RMF Control
AU-8
Severity
Low
CCI
CCI-001891
Version
WN12-CC-000069
Vuln IDs
  • V-225361
  • V-3472
Rule IDs
  • SV-225361r877038_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-27060r857219_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, which are identified at: https://www.cnmoc.usff.navy.mil/Organization/United-States-Naval-Observatory/Precise-Time-Department/Network-Time-Protocol-NTP/ 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-27048r857220_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, which are identified at: https://www.cnmoc.usff.navy.mil/Organization/United-States-Naval-Observatory/Precise-Time-Department/Network-Time-Protocol-NTP/ 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-225362 - SV-225362r569185_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
WN12-CC-000070
Vuln IDs
  • V-225362
  • V-36697
Rule IDs
  • SV-225362r569185_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-27061r471428_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-27049r471429_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-225363 - SV-225363r569185_rule
RMF Control
CM-7
Severity
Low
CCI
CCI-000381
Version
WN12-CC-000071
Vuln IDs
  • V-225363
  • V-21971
Rule IDs
  • SV-225363r569185_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-27062r471431_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-27050r471432_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-225364 - SV-225364r852210_rule
RMF Control
CM-7
Severity
High
CCI
CCI-001764
Version
WN12-CC-000072
Vuln IDs
  • V-225364
  • V-21973
Rule IDs
  • SV-225364r852210_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-27063r471434_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-27051r471435_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-225365 - SV-225365r852211_rule
RMF Control
CM-7
Severity
High
CCI
CCI-001764
Version
WN12-CC-000073
Vuln IDs
  • V-225365
  • V-22692
Rule IDs
  • SV-225365r852211_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-27064r471437_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-27052r471438_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-225366 - SV-225366r852212_rule
RMF Control
CM-7
Severity
High
CCI
CCI-001764
Version
WN12-CC-000074
Vuln IDs
  • V-225366
  • V-2374
Rule IDs
  • SV-225366r852212_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-27065r471440_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-27053r471441_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-225367 - SV-225367r569185_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
WN12-CC-000075
Vuln IDs
  • V-225367
  • V-36698
Rule IDs
  • SV-225367r569185_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-27066r471443_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-27054r471444_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-225368 - SV-225368r569185_rule
RMF Control
IA-6
Severity
Medium
CCI
CCI-000206
Version
WN12-CC-000076
Vuln IDs
  • V-225368
  • V-36700
Rule IDs
  • SV-225368r569185_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-27067r471446_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-27055r471447_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-225369 - SV-225369r569185_rule
RMF Control
SC-3
Severity
Medium
CCI
CCI-001084
Version
WN12-CC-000077
Vuln IDs
  • V-225369
  • V-14243
Rule IDs
  • SV-225369r569185_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-27068r471449_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-27056r471450_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-225370 - SV-225370r877391_rule
RMF Control
AU-4
Severity
Medium
CCI
CCI-001849
Version
WN12-CC-000084
Vuln IDs
  • V-225370
  • V-26579
Rule IDs
  • SV-225370r877391_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-27069r471452_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-27057r471453_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-225371 - SV-225371r877391_rule
RMF Control
AU-4
Severity
Medium
CCI
CCI-001849
Version
WN12-CC-000085
Vuln IDs
  • V-225371
  • V-26580
Rule IDs
  • SV-225371r877391_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-27070r471455_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-27058r471456_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-225372 - SV-225372r877391_rule
RMF Control
AU-4
Severity
Medium
CCI
CCI-001849
Version
WN12-CC-000086
Vuln IDs
  • V-225372
  • V-26581
Rule IDs
  • SV-225372r877391_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-27071r471458_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-27059r471459_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-225373 - SV-225373r877391_rule
RMF Control
AU-4
Severity
Medium
CCI
CCI-001849
Version
WN12-CC-000087
Vuln IDs
  • V-225373
  • V-26582
Rule IDs
  • SV-225373r877391_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-27072r471461_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-27060r471462_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-225374 - SV-225374r569185_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
WN12-CC-000088
Vuln IDs
  • V-225374
  • V-36707
Rule IDs
  • SV-225374r569185_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-27073r471464_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-27061r471465_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-225375 - SV-225375r852217_rule
RMF Control
SI-16
Severity
Medium
CCI
CCI-002824
Version
WN12-CC-000089
Vuln IDs
  • V-225375
  • V-21980
Rule IDs
  • SV-225375r852217_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-27074r471467_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-27062r471468_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-225376 - SV-225376r852218_rule
RMF Control
SC-5
Severity
Low
CCI
CCI-002385
Version
WN12-CC-000090
Vuln IDs
  • V-225376
  • V-15718
Rule IDs
  • SV-225376r852218_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-27075r471470_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-27063r471471_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-225377 - SV-225377r569185_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-CC-000091
Vuln IDs
  • V-225377
  • V-15683
Rule IDs
  • SV-225377r569185_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-27076r471473_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-27064r471474_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-225378 - SV-225378r569185_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
WN12-CC-000095
Vuln IDs
  • V-225378
  • V-36708
Rule IDs
  • SV-225378r569185_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-27077r471476_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-27065r471477_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-225379 - SV-225379r852219_rule
RMF Control
IA-11
Severity
Medium
CCI
CCI-002038
Version
WN12-CC-000096
Vuln IDs
  • V-225379
  • V-14247
Rule IDs
  • SV-225379r852219_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-27078r471479_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-27066r471480_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-225380 - SV-225380r569185_rule
RMF Control
SC-4
Severity
Medium
CCI
CCI-001090
Version
WN12-CC-000098
Vuln IDs
  • V-225380
  • V-14249
Rule IDs
  • SV-225380r569185_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-27079r471482_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-27067r471483_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-225381 - SV-225381r852220_rule
RMF Control
IA-11
Severity
Medium
CCI
CCI-002038
Version
WN12-CC-000099
Vuln IDs
  • V-225381
  • V-3453
Rule IDs
  • SV-225381r852220_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-27080r471485_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-27068r471486_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-225382 - SV-225382r877398_rule
RMF Control
AC-17
Severity
Medium
CCI
CCI-000068
Version
WN12-CC-000100
Vuln IDs
  • V-225382
  • V-3454
Rule IDs
  • SV-225382r877398_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-27081r471488_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-27069r471489_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-225383 - SV-225383r569185_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-CC-000103
Vuln IDs
  • V-225383
  • V-3456
Rule IDs
  • SV-225383r569185_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-27082r471491_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-27070r471492_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-225384 - SV-225384r569185_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-CC-000104
Vuln IDs
  • V-225384
  • V-3455
Rule IDs
  • SV-225384r569185_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-27083r471494_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-27071r471495_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-225385 - SV-225385r569185_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-CC-000105
Vuln IDs
  • V-225385
  • V-15682
Rule IDs
  • SV-225385r569185_rule
  • SV-53040
Attachments from RSS feeds may not be secure. This setting will prevent attachments from being downloaded from RSS feeds.
Checks: C-27084r471497_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-27072r471498_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-225386 - SV-225386r569185_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
WN12-CC-000106
Vuln IDs
  • V-225386
  • V-36709
Rule IDs
  • SV-225386r569185_rule
  • SV-51749
Basic authentication uses plain text passwords that could be used to compromise a system.
Checks: C-27085r471500_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-27073r471501_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-225387 - SV-225387r569185_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
WN12-CC-000109
Vuln IDs
  • V-225387
  • V-36710
Rule IDs
  • SV-225387r569185_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-27086r471503_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-27074r471504_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-225388 - SV-225388r569185_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-CC-000110
Vuln IDs
  • V-225388
  • V-36711
Rule IDs
  • SV-225388r569185_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-27087r471506_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-27075r471507_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-225389 - SV-225389r852222_rule
RMF Control
CM-11
Severity
Medium
CCI
CCI-001812
Version
WN12-CC-000115
Vuln IDs
  • V-225389
  • V-15685
Rule IDs
  • SV-225389r852222_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-27088r471509_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-27076r471510_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-225390 - SV-225390r852223_rule
RMF Control
CM-11
Severity
High
CCI
CCI-001812
Version
WN12-CC-000116
Vuln IDs
  • V-225390
  • V-34974
Rule IDs
  • SV-225390r852223_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-27089r471512_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-27077r471513_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-225391 - SV-225391r569185_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-CC-000117
Vuln IDs
  • V-225391
  • V-15684
Rule IDs
  • SV-225391r569185_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-27090r471515_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-27078r471516_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-225392 - SV-225392r852224_rule
RMF Control
CM-11
Severity
Low
CCI
CCI-001812
Version
WN12-CC-000118
Vuln IDs
  • V-225392
  • V-15686
Rule IDs
  • SV-225392r852224_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-27091r471518_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-27079r471519_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-225393 - SV-225393r569185_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
WN12-CC-000120
Vuln IDs
  • V-225393
  • V-15722
Rule IDs
  • SV-225393r569185_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-27092r471521_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-27080r471522_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-225394 - SV-225394r569185_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
WN12-CC-000121
Vuln IDs
  • V-225394
  • V-15687
Rule IDs
  • SV-225394r569185_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-27093r471524_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-27081r471525_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-225395 - SV-225395r852225_rule
RMF Control
CM-11
Severity
Medium
CCI
CCI-001812
Version
WN12-CC-000122
Vuln IDs
  • V-225395
  • V-3480
Rule IDs
  • SV-225395r852225_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-27094r471527_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-27082r471528_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-225396 - SV-225396r877395_rule
RMF Control
MA-4
Severity
High
CCI
CCI-000877
Version
WN12-CC-000123
Vuln IDs
  • V-225396
  • V-36712
Rule IDs
  • SV-225396r877395_rule
  • SV-51752
Basic authentication uses plain text passwords that could be used to compromise a system.
Checks: C-27095r471530_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-27083r471531_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-225397 - SV-225397r877382_rule
RMF Control
MA-4
Severity
Medium
CCI
CCI-002890
Version
WN12-CC-000124
Vuln IDs
  • V-225397
  • V-36713
Rule IDs
  • SV-225397r877382_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-27096r471533_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-27084r471534_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-225398 - SV-225398r877395_rule
RMF Control
MA-4
Severity
Medium
CCI
CCI-000877
Version
WN12-CC-000125
Vuln IDs
  • V-225398
  • V-36714
Rule IDs
  • SV-225398r877395_rule
  • SV-51754
Digest authentication is not as strong as other options and may be subject to man-in-the-middle attacks.
Checks: C-27097r471536_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-27085r471537_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-225399 - SV-225399r877395_rule
RMF Control
MA-4
Severity
High
CCI
CCI-000877
Version
WN12-CC-000126
Vuln IDs
  • V-225399
  • V-36718
Rule IDs
  • SV-225399r877395_rule
  • SV-51755
Basic authentication uses plain text passwords that could be used to compromise a system.
Checks: C-27098r471539_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-27086r471540_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-225400 - SV-225400r877382_rule
RMF Control
MA-4
Severity
Medium
CCI
CCI-002890
Version
WN12-CC-000127
Vuln IDs
  • V-225400
  • V-36719
Rule IDs
  • SV-225400r877382_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-27099r471542_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-27087r471543_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-225401 - SV-225401r852228_rule
RMF Control
IA-11
Severity
Medium
CCI
CCI-002038
Version
WN12-CC-000128
Vuln IDs
  • V-225401
  • V-36720
Rule IDs
  • SV-225401r852228_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-27100r471545_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-27088r471546_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-225402 - SV-225402r877394_rule
RMF Control
AC-17
Severity
Medium
CCI
CCI-001453
Version
WN12-CC-000130
Vuln IDs
  • V-225402
  • V-4447
Rule IDs
  • SV-225402r877394_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-27101r471548_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-27089r471549_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-225404 - SV-225404r852229_rule
RMF Control
AC-17
Severity
Medium
CCI
CCI-002314
Version
WN12-CC-000132
Vuln IDs
  • V-225404
  • V-15997
Rule IDs
  • SV-225404r852229_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-27103r471554_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-27091r471555_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-225405 - SV-225405r852230_rule
RMF Control
AC-17
Severity
Medium
CCI
CCI-002314
Version
WN12-CC-000133
Vuln IDs
  • V-225405
  • V-15998
Rule IDs
  • SV-225405r852230_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-27104r471557_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-27092r471558_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-225406 - SV-225406r852231_rule
RMF Control
AC-17
Severity
Medium
CCI
CCI-002314
Version
WN12-CC-000134
Vuln IDs
  • V-225406
  • V-16000
Rule IDs
  • SV-225406r852231_rule
  • SV-52230
Enabling the redirection of smart card devices allows their use within Remote Desktop sessions.
Checks: C-27105r471560_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-27093r471561_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-225407 - SV-225407r852232_rule
RMF Control
AC-17
Severity
Medium
CCI
CCI-002314
Version
WN12-CC-000135
Vuln IDs
  • V-225407
  • V-15999
Rule IDs
  • SV-225407r852232_rule
  • SV-52229
Preventing the redirection of Plug and Play devices in Remote Desktop sessions helps reduce possible exposure of sensitive data.
Checks: C-27106r471563_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-27094r471564_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-225408 - SV-225408r569185_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-CC-000136
Vuln IDs
  • V-225408
  • V-40204
Rule IDs
  • SV-225408r569185_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-27107r471566_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-27095r471567_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-225409 - SV-225409r569185_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
WN12-CC-000138
Vuln IDs
  • V-225409
  • V-43238
Rule IDs
  • SV-225409r569185_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-27108r471569_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-27096r471570_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-225410 - SV-225410r569185_rule
RMF Control
AU-3
Severity
Medium
CCI
CCI-000135
Version
WN12-CC-000139
Vuln IDs
  • V-225410
  • V-43239
Rule IDs
  • SV-225410r569185_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-27109r471572_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-27097r471573_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-225411 - SV-225411r569185_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
WN12-CC-000140
Vuln IDs
  • V-225411
  • V-43240
Rule IDs
  • SV-225411r569185_rule
  • SV-56346
Enabling interaction with the network selection UI allows users to change connections to available networks without signing into Windows.
Checks: C-27110r471575_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-27098r471576_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-225412 - SV-225412r569185_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
WN12-CC-000141
Vuln IDs
  • V-225412
  • V-43241
Rule IDs
  • SV-225412r569185_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-27111r471578_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-27099r471579_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-225413 - SV-225413r569185_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-CC-000142
Vuln IDs
  • V-225413
  • V-102619
Rule IDs
  • SV-225413r569185_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-27112r471581_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-27100r471582_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-225414 - SV-225414r569185_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-CC-000145
Vuln IDs
  • V-225414
  • V-43245
Rule IDs
  • SV-225414r569185_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-27113r471584_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-27101r471585_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-225415 - SV-225415r569185_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
WN12-CC-000150
Vuln IDs
  • V-225415
  • V-72753
Rule IDs
  • SV-225415r569185_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-27114r471587_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-27102r471588_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-225416 - SV-225416r569185_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-FW-000001
Vuln IDs
  • V-225416
  • V-42420
Rule IDs
  • SV-225416r569185_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-27115r471590_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-27103r471591_fix

Install and enable a host-based firewall on the system.

c
Systems must be maintained at a supported OS or service pack level.
CM-6 - High - CCI-000366 - V-225417 - SV-225417r921961_rule
RMF Control
CM-6
Severity
High
CCI
CCI-000366
Version
WN12-GE-000001
Vuln IDs
  • V-225417
  • V-1073
Rule IDs
  • SV-225417r921961_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-27116r921959_chk

Run "winver.exe". If the "About Windows" displays the following or less, this is a finding: "Microsoft Windows Server Version 6.3 (Build 9600)" Windows Server 2012 and 2012 R2 support ended on October 10, 2023. If Extended Security Updates (ESUs up to three years) have not been acquired, this is a finding.

Fix: F-27104r921960_fix

Update the system to a supported release or operating system.

c
Only administrators responsible for the member server must have Administrator rights on the system.
AC-6 - High - CCI-002235 - V-225418 - SV-225418r877392_rule
RMF Control
AC-6
Severity
High
CCI
CCI-002235
Version
WN12-GE-000004-MS
Vuln IDs
  • V-225418
  • V-1127
Rule IDs
  • SV-225418r877392_rule
  • SV-51511
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. For domain-joined member servers, the Domain Admins group must be replaced by a domain member server administrator group (see V-36433 in the Active Directory Domain STIG). Restricting highly privileged accounts from the local Administrators group helps mitigate the risk of privilege escalation resulting from credential theft attacks. Standard user accounts must not be members of the built-in Administrators group.
Checks: C-27117r471596_chk

Review the local Administrators group. Only the appropriate administrator groups or accounts responsible for administration of the system may be members of the group. For domain-joined member servers, the Domain Admins group must be replaced by a domain member server administrator 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-27105r471597_fix

Configure the system to include only administrator groups or accounts that are responsible for the system in the local Administrators group. For domain-joined member servers, replace the Domain Admins group with a domain member server administrator group. Remove any standard user accounts.

c
Local volumes must use a format that supports NTFS attributes.
AC-3 - High - CCI-000213 - V-225419 - SV-225419r569185_rule
RMF Control
AC-3
Severity
High
CCI
CCI-000213
Version
WN12-GE-000005
Vuln IDs
  • V-225419
  • V-1081
Rule IDs
  • SV-225419r569185_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-27118r471599_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-27106r471600_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-225420 - SV-225420r852234_rule
RMF Control
AC-3
Severity
Medium
CCI
CCI-002165
Version
WN12-GE-000006
Vuln IDs
  • V-225420
  • V-40178
Rule IDs
  • SV-225420r852234_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-27119r471602_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-27107r471603_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-225421 - SV-225421r852235_rule
RMF Control
AC-3
Severity
Medium
CCI
CCI-002165
Version
WN12-GE-000007
Vuln IDs
  • V-225421
  • V-40177
Rule IDs
  • SV-225421r852235_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-27120r471605_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-27108r471606_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-225422 - SV-225422r852236_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
WN12-GE-000008
Vuln IDs
  • V-225422
  • V-40179
Rule IDs
  • SV-225422r852236_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-27121r471608_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-27109r471609_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-225423 - SV-225423r569185_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-GE-000010
Vuln IDs
  • V-225423
  • V-1119
Rule IDs
  • SV-225423r569185_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-27122r471611_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-27110r471612_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-225424 - SV-225424r569185_rule
RMF Control
AC-3
Severity
Low
CCI
CCI-000213
Version
WN12-GE-000012
Vuln IDs
  • V-225424
  • V-1135
Rule IDs
  • SV-225424r569185_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-27123r471614_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-27111r471615_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-225425 - SV-225425r569185_rule
RMF Control
IA-4
Severity
Low
CCI
CCI-000795
Version
WN12-GE-000014
Vuln IDs
  • V-225425
  • V-1112
Rule IDs
  • SV-225425r569185_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-27124r471617_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-27112r471618_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-225426 - SV-225426r569185_rule
RMF Control
IA-2
Severity
High
CCI
CCI-000764
Version
WN12-GE-000015
Vuln IDs
  • V-225426
  • V-7002
Rule IDs
  • SV-225426r569185_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-27125r471620_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-27113r471621_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-225427 - SV-225427r857215_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000199
Version
WN12-GE-000016
Vuln IDs
  • V-225427
  • V-6840
Rule IDs
  • SV-225427r857215_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-27126r857214_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). 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-27114r471624_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-225428 - SV-225428r860012_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-GE-000017
Vuln IDs
  • V-225428
  • V-2907
Rule IDs
  • SV-225428r860012_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-27127r860011_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 McAfee Application Control and Change Control (MACC) module will meet the requirement for file integrity checking.

Fix: F-27115r857217_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-225429 - SV-225429r569185_rule
RMF Control
SC-4
Severity
Medium
CCI
CCI-001090
Version
WN12-GE-000018
Vuln IDs
  • V-225429
  • V-3245
Rule IDs
  • SV-225429r569185_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-27128r471629_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-27116r471630_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-225431 - SV-225431r569185_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-GE-000020
Vuln IDs
  • V-225431
  • V-15823
Rule IDs
  • SV-225431r569185_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-27130r471635_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-27118r471636_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-225432 - SV-225432r569185_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
WN12-GE-000021
Vuln IDs
  • V-225432
  • V-3487
Rule IDs
  • SV-225432r569185_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-27131r471638_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-27119r471639_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-225433 - SV-225433r793244_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-GE-000022
Vuln IDs
  • V-225433
  • V-3289
Rule IDs
  • SV-225433r793244_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-27132r793242_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-27120r793243_fix

Install a host-based Intrusion Detection System on each server. Severity Override Guidance: This finding can be downgraded to a CAT III if there is an active HIDS or firewall protecting the network.

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 not covered by ESS; and annually, for external scans by Computer Network Defense Service Provider (CNDSP).
SI-2 - Medium - CCI-001233 - V-225434 - SV-225434r793248_rule
RMF Control
SI-2
Severity
Medium
CCI
CCI-001233
Version
WN12-GE-000023
Vuln IDs
  • V-225434
  • V-36734
Rule IDs
  • SV-225434r793248_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-27133r793247_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-27121r641884_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-225435 - SV-225435r569185_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-GE-000024
Vuln IDs
  • V-225435
  • V-36735
Rule IDs
  • SV-225435r569185_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-27134r471647_chk

Verify the organization has an automated process to install security-related software updates. If it does not, this is a finding.

Fix: F-27122r471648_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-225436 - SV-225436r877395_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-GE-000025
Vuln IDs
  • V-225436
  • V-36736
Rule IDs
  • SV-225436r877395_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-27135r471650_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-27123r471651_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-225437 - SV-225437r569185_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-GE-000026
Vuln IDs
  • V-225437
  • V-1120
Rule IDs
  • SV-225437r569185_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-27136r471653_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-27124r471654_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-225438 - SV-225438r569185_rule
RMF Control
CM-6
Severity
High
CCI
CCI-000366
Version
WN12-GE-000027
Vuln IDs
  • V-225438
  • V-1121
Rule IDs
  • SV-225438r569185_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-27137r471656_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-27125r471657_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-225439 - SV-225439r569185_rule
RMF Control
AC-2
Severity
Medium
CCI
CCI-000016
Version
WN12-GE-000056
Vuln IDs
  • V-225439
  • V-57653
Rule IDs
  • SV-225439r569185_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-27138r471659_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-27126r471660_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-225440 - SV-225440r569185_rule
RMF Control
AC-2
Severity
Medium
CCI
CCI-001682
Version
WN12-GE-000057
Vuln IDs
  • V-225440
  • V-57655
Rule IDs
  • SV-225440r569185_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-27139r471662_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-27127r471663_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-225441 - SV-225441r922786_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000185
Version
WN12-PK-000001
Vuln IDs
  • V-225441
  • V-32272
Rule IDs
  • SV-225441r922786_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-27140r921962_chk

Verify the DoD Root CA certificates are installed as Trusted Root Certification Authorities. The certificates and thumbprints referenced below apply to unclassified systems; refer to 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 Subject: CN=DoD Root CA 6, OU=PKI, OU=DoD, O=U.S. Government, C=US Thumbprint : D37ECF61C0B4ED88681EF3630C4E2FC787B37AEF NotAfter: 1/24/2053 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 DoD Root CA 6 Thumbprint: D37ECF61C0B4ED88681EF3630C4E2FC787B37AEF Valid to: Friday, January 24, 2053

Fix: F-27128r922786_fix

Install the DoD Root CA certificates: DoD Root CA 3 DoD Root CA 4 DoD Root CA 5 DoD Root CA 6 The InstallRoot tool is available on Cyber Exchange at https://cyber.mil/pki-pke/tools-configuration-files. PKI can be found at https://crl.gds.disa.mil/.

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-225442 - SV-225442r894333_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000185
Version
WN12-PK-000003
Vuln IDs
  • V-225442
  • V-32274
Rule IDs
  • SV-225442r894333_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-27141r890493_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 : 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 : 49CBE933151872E17C8EAE7F0ABA97FB610F6477 Valid to: Wednesday, November 16, 2024

Fix: F-27129r890494_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 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. PKI can be found at https://crl.gds.disa.mil/.

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-225443 - SV-225443r894336_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000185
Version
WN12-PK-000004
Vuln IDs
  • V-225443
  • V-40237
Rule IDs
  • SV-225443r894336_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-27142r894334_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: 9B74964506C7ED9138070D08D5F8B969866560C8 NotAfter: 7/18/2025 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: 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: 9B74964506C7ED9138070D08D5F8B969866560C8 NotAfter: 7/18/2025 Certificate bundles published by the PKI can be found at https://crl.gds.disa.mil/.

Fix: F-27130r894335_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 - 9B74964506C7ED9138070D08D5F8B969866560C8 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. PKI can be found at https://crl.gds.disa.mil/.

c
Standard user accounts must only have Read permissions to the Winlogon registry key.
AC-6 - High - CCI-002235 - V-225444 - SV-225444r877392_rule
RMF Control
AC-6
Severity
High
CCI
CCI-002235
Version
WN12-RG-000001
Vuln IDs
  • V-225444
  • V-26070
Rule IDs
  • SV-225444r877392_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-27143r471674_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-27131r471675_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-225445 - SV-225445r877392_rule
RMF Control
AC-6
Severity
High
CCI
CCI-002235
Version
WN12-RG-000002
Vuln IDs
  • V-225445
  • V-32282
Rule IDs
  • SV-225445r877392_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-27144r471677_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-27132r471678_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

b
Local administrator accounts must have their privileged token filtered to prevent elevated privileges from being used over the network on domain systems.
SC-3 - Medium - CCI-001084 - V-225446 - SV-225446r569185_rule
RMF Control
SC-3
Severity
Medium
CCI
CCI-001084
Version
WN12-RG-000003-MS
Vuln IDs
  • V-225446
  • V-36439
Rule IDs
  • SV-225446r569185_rule
  • SV-51590
A compromised local administrator account can provide means for an attacker to move laterally between domain systems. With User Account Control enabled, filtering the privileged token for local administrator accounts will prevent the elevated privileges of these accounts from being used over the network.
Checks: C-27145r471680_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\CurrentVersion\Policies\System\ Value Name: LocalAccountTokenFilterPolicy Type: REG_DWORD Value: 0x00000000 (0) This setting may cause issues with some network scanning tools if local administrative accounts are used remotely. Scans should use domain accounts where possible. If a local administrative account must be used, temporarily enabling the privileged token by configuring the registry value to 1 may be required.

Fix: F-27133r471681_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> "Apply UAC restrictions to local accounts on network logons" to "Enabled". 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.

c
Anonymous access to the registry must be restricted.
AC-6 - High - CCI-002235 - V-225447 - SV-225447r877392_rule
RMF Control
AC-6
Severity
High
CCI
CCI-002235
Version
WN12-RG-000004
Vuln IDs
  • V-225447
  • V-1152
Rule IDs
  • SV-225447r877392_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-27146r471683_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-27134r471684_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-225448 - SV-225448r569185_rule
RMF Control
IA-8
Severity
Medium
CCI
CCI-000804
Version
WN12-SO-000003
Vuln IDs
  • V-225448
  • V-1113
Rule IDs
  • SV-225448r569185_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-27147r471686_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-27135r471687_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-225449 - SV-225449r569185_rule
RMF Control
CM-6
Severity
High
CCI
CCI-000366
Version
WN12-SO-000004
Vuln IDs
  • V-225449
  • V-3344
Rule IDs
  • SV-225449r569185_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-27148r471689_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-27136r471690_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-225450 - SV-225450r569185_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-SO-000005
Vuln IDs
  • V-225450
  • V-1115
Rule IDs
  • SV-225450r569185_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-27149r471692_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-27137r471693_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-225451 - SV-225451r569185_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
WN12-SO-000006
Vuln IDs
  • V-225451
  • V-1114
Rule IDs
  • SV-225451r569185_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-27150r471695_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-27138r471696_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-225452 - SV-225452r569185_rule
RMF Control
SC-5
Severity
Medium
CCI
CCI-001095
Version
WN12-SO-000007
Vuln IDs
  • V-225452
  • V-14228
Rule IDs
  • SV-225452r569185_rule
  • SV-53129