Microsoft Windows Server 2025

Version

WN25-00-000010

Vuln IDs

V-277985

Rule IDs

SV-277985r1128995_rule

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-82515r1128993_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-82420r1128994_fix

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

b

Windows Server 2025 passwords for the built-in Administrator account must be changed at least every 60 days.

Medium - CCI-004066 - V-277986 - SV-277986r1130124_rule

RMF Control

Severity

M

CCI

Version

WN25-00-000020

Vuln IDs

V-277986

Rule IDs

SV-277986r1130124_rule

The longer a password is in use, the greater the opportunity for someone to gain unauthorized knowledge of the password. The built-in Administrator account is not generally used and its password may not be changed as frequently as necessary. Changing the password for the built-in Administrator account on a regular basis will limit its exposure. 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-82516r1130123_chk

If there are no enabled local Administrator accounts, this is not applicable. Review the password last set date for the enabled local Administrator account. On the stand alone or domain-joined workstation: Open PowerShell. Enter "Get-LocalUser -Name * | Select-Object *". If the "PasswordLastSet" date is greater than "60" days old for the local Administrator account for administering the computer/domain, this is a finding. Verify LAPS is configured and operational. Navigate to Local Computer Policy >> Computer Configuration >> Administrative Templates >> System >> LAPS >> Password Settings >> Set to enabled. Password Complexity, large letters + small letters + numbers + special, Password Length 14, Password Age 60, Passphrase Length 6. If not configured as shown, this is a finding. Verify LAPS Operational logs >> Event Viewer >> Applications and Services Logs >> Microsoft >> Windows >> LAPS >> Operational. Verify LAPS policy process is completing. If it is not, this is a finding. If the server is not a member of a domain, this not applicable.

Fix: F-82421r1128997_fix

Change the built-in Administrator account password at least every 60 days. It is highly recommended to use Microsoft's LAPS, which may be used 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

Windows Server 2025 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-277987 - SV-277987r1129001_rule

RMF Control

CM-6

Severity

H

CCI

Version

WN25-00-000030

Vuln IDs

V-277987

Rule IDs

SV-277987r1129001_rule

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 require administrative accounts to not access the internet or use applications such as email. The policy must 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. Whitelisting can be used to enforce the policy to ensure compliance. Satisfies: SRG-OS-000480-GPOS-00227, SRG-OS-000205-GPOS-00083

Checks: C-82517r1128999_chk

Determine whether organization policy, at a minimum, 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. If it does not, this is a finding. The organization may use technical means such as whitelisting to prevent the use of browsers and mail applications to enforce this requirement.

Fix: F-82422r1129000_fix

Establish a policy, at minimum, to prohibit administrative accounts from using applications that access the internet, such as web browsers, or with potential internet sources, such as email. Ensure the policy is enforced. The organization may use technical means such as whitelisting to prevent the use of browsers and mail applications to enforce this requirement.

b

Windows Server 2025 members of the Backup Operators group must have separate accounts for backup duties and normal operational tasks.

CM-6 - Medium - CCI-000366 - V-277988 - SV-277988r1130126_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-00-000040

Vuln IDs

V-277988

Rule IDs

SV-277988r1130126_rule

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-82518r1130125_chk

If no accounts are members of the Backup Operators group, this is not applicable. 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-82423r1129003_fix

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

b

Windows Server 2025 manually managed application account passwords must be at least 15 characters in length.

IA-5 - Medium - CCI-000205 - V-277989 - SV-277989r1130128_rule

RMF Control

IA-5

Severity

M

CCI

CCI-000205

Version

WN25-00-000050

Vuln IDs

V-277989

Rule IDs

SV-277989r1130128_rule

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-82519r1130127_chk

Determine if manually managed application/service accounts exist. If none exist, this is not applicable. Verify the organization 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-82424r1129006_fix

Establish a 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 Server 2025 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-277990 - SV-277990r1130130_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-00-000060

Vuln IDs

V-277990

Rule IDs

SV-277990r1130130_rule

Setting application account passwords 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-82520r1130129_chk

Determine if manually managed application/service accounts exist. If none exist, this is not applicable. 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 PowerShell. Enter "Get-AdUser -Identity [application account name] -Properties PasswordLastSet | FT 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 or nondomain joined systems: Open 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-82425r1129009_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 whenever possible.

b

Windows Server 2025 shared user accounts must not be permitted.

IA-2 - Medium - CCI-000764 - V-277991 - SV-277991r1130132_rule

RMF Control

IA-2

Severity

M

CCI

CCI-000764

Version

WN25-00-000070

Vuln IDs

V-277991

Rule IDs

SV-277991r1130132_rule

Shared accounts (accounts where two or more people log on 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-82521r1130131_chk

Determine whether any shared accounts exist. If no shared accounts exist, this is not applicable. Shared accounts, such as required by an application, may be approved by the organization. This must be documented with the information system security officer (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-82426r1129012_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.

b

Windows Server 2025 must employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs.

CM-7 - Medium - CCI-001774 - V-277992 - SV-277992r1130135_rule

RMF Control

CM-7

Severity

M

CCI

CCI-001774

Version

WN25-00-000080

Vuln IDs

V-277992

Rule IDs

SV-277992r1130135_rule

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

Checks: C-82522r1130133_chk

Verify the operating system employs a deny-all, permit-by-exception policy to allow the execution of authorized software programs. If an application whitelisting program is not in use on the system, this is a finding. Configuration of whitelisting applications will vary by the program. AppLocker is a whitelisting application built in to Windows Server. 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 imported previously, execute the following first: Import-Module AppLocker Execute the following command, substituting c:\temp\file.xml with a location and file name appropriate for the system: Get-AppLockerPolicy -Effective -XML > c:\temp\file.xml This will produce an XML file with the effective settings that can be viewed in a browser or opened in a program such as Excel for review. Implementation guidance for AppLocker is available in the NSA paper "Application Whitelisting using Microsoft AppLocker" at the following link: https://www.iad.gov/iad/library/ia-guidance/tech-briefs/application-whitelisting-using-microsoft-applocker.cfm

Fix: F-82427r1130134_fix

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

b

Windows Server 2025 domain-joined systems must have a Trusted Platform Module (TPM) enabled and ready for use.

Medium - CCI-004910 - V-277993 - SV-277993r1130137_rule

RMF Control

Severity

M

CCI

CCI-004910

Version

WN25-00-000090

Vuln IDs

V-277993

Rule IDs

SV-277993r1130137_rule

Credential Guard uses virtualization-based security to protect data that could be used in credential theft attacks if compromised. A number of system requirements must be met for Credential Guard to be configured and enabled properly. Without a TPM enabled and ready for use, Credential Guard keys are stored in a less secure method using software.

Checks: C-82523r1130136_chk

For standalone or nondomain joined systems, this is not applicable. Verify the system has a TPM and it is ready for use. Run "tpm.msc". Review the sections in the center pane. "Status" must indicate it has been configured with a message such as "The TPM is ready for use" or "The TPM is on and ownership has been taken". TPM Manufacturer Information - Specific Version = 2.0 or 1.2 If a TPM is not found or is not ready for use, this is a finding.

Fix: F-82428r1129018_fix

Ensure domain-joined systems have a TPM that is configured for use. (Versions 2.0 or 1.2 support Credential Guard.) The TPM must be enabled in the firmware. Run "tpm.msc" for configuration options in Windows.

b

Windows Server 2025 must be maintained at a supported servicing level.

CM-6 - Medium - CCI-000366 - V-277994 - SV-277994r1129022_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-00-000100

Vuln IDs

V-277994

Rule IDs

SV-277994r1129022_rule

Systems at unsupported servicing levels will not receive security updates for new vulnerabilities, which leave them subject to exploitation. Systems must be maintained at a servicing level supported by the vendor with new security updates.

Checks: C-82524r1129020_chk

Open command prompt. Enter "winver.exe". If the "About Windows" dialog box does not display "Microsoft Windows Server Version 24H2 (Build .26100.xxx)" or greater, this is a finding. Preview versions must not be used in a production environment.

Fix: F-82429r1129021_fix

Update the system to a Version 24H2 (Build 16100.xxx) or greater.

b

Windows Server 2025 must use an antivirus program.

CM-6 - Medium - CCI-000366 - V-277995 - SV-277995r1129025_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-00-000110

Vuln IDs

V-277995

Rule IDs

SV-277995r1129025_rule

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-82525r1129023_chk

Verify an antivirus solution is installed on the system. The antivirus solution may be bundled with an approved host-based security solution. If there is no antivirus solution installed on the system, this is a finding. Verify if Microsoft Defender antivirus is in use or enabled: Open PowerShell. Enter "get-service | where {$_.DisplayName -Like "*Defender*"} | Select Status,DisplayName" Verify if third-party antivirus is in use or enabled: Open PowerShell. Enter "get-service | where {$_.DisplayName -Like "*mcafee*"} | Select Status,DisplayName Enter "get-service | where {$_.DisplayName -Like "*symantec*"} | Select Status,DisplayName

Fix: F-82430r1129024_fix

If no antivirus software is in use, install Microsoft Defender or third-party antivirus. Open PowerShell. Enter "Install-WindowsFeature -Name Windows-Defender". For third-party antivirus, install per antivirus instructions and disable Windows Defender. Open PowerShell. Enter "Uninstall-WindowsFeature -Name Windows-Defender".

b

Windows Server 2025 must have a host-based intrusion detection or prevention system.

CM-6 - Medium - CCI-000366 - V-277996 - SV-277996r1129028_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-00-000120

Vuln IDs

V-277996

Rule IDs

SV-277996r1129028_rule

A properly configured host-based intrusion detection system (HIDS) or host-based intrusion prevention system (HIPS) 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-82526r1129026_chk

Determine whether there is a HIDS or HIPS 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 meets the requirement. A HIDS 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 information system security officer (ISSO). If a HIDS is not installed on the system, this is a finding.

Fix: F-82431r1129027_fix

Install a HIDS or HIPS on each server.

c

Windows Server 2025 local volumes must use a format that supports NTFS attributes.

AC-3 - High - CCI-000213 - V-277997 - SV-277997r1129031_rule

RMF Control

AC-3

Severity

H

CCI

Version

WN25-00-000130

Vuln IDs

V-277997

Rule IDs

SV-277997r1129031_rule

The ability to set access permissions and auditing is critical to maintaining the security and proper access controls of a system. To support this, volumes must be formatted using a file system that supports NTFS attributes.

Checks: C-82527r1129029_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. "CSVFS" (Cluster Shared Volumes File Systems" is also acceptable and would not be a finding. This does not apply to system partitions such the Recovery and EFI System Partition.

Fix: F-82432r1129030_fix

Format volumes to use NTFS, ReFS, or CSVFS.

b

Windows Server 2025 permissions for the system drive root directory (usually C:\) must conform to minimum requirements.

AC-3 - Medium - CCI-002165 - V-277998 - SV-277998r1129034_rule

RMF Control

AC-3

Severity

M

CCI

CCI-002165

Version

WN25-00-000140

Vuln IDs

V-277998

Rule IDs

SV-277998r1129034_rule

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" (WN25-SO-000240). Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124

Checks: C-82528r1129032_chk

The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN25-SO-000240). Review the 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. If permissions are not as restrictive as the default permissions listed below, this is a finding. Viewing in File Explorer: View the Properties of the system drive's root directory. Select the "Security" tab, and then click "Advanced". 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 Alternately, use icacls: Open "command prompt (Admin)". Enter "icacls" followed by the directory: "icacls c:\" The following results must 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-82433r1129033_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" (WN25-SO-000240). 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

Windows Server 2025 permissions for program file directories must conform to minimum requirements.

AC-3 - Medium - CCI-002165 - V-277999 - SV-277999r1129037_rule

RMF Control

AC-3

Severity

M

CCI

CCI-002165

Version

WN25-00-000150

Vuln IDs

V-277999

Rule IDs

SV-277999r1129037_rule

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" (WN25-SO-000240). Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124

Checks: C-82529r1129035_chk

The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN25-SO-000240). Review the 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. Individual accounts must not be used to assign permissions. If permissions are not as restrictive as the default permissions listed below, this is a finding. Viewing in File Explorer: For each folder, view the Properties. Select the "Security" tab, and then click "Advanced". 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 ALL RESTRICTED 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 must be displayed for each when entered: c:\program files (c:\program files (x86)) 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) APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(RX) APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE) Successfully processed 1 files; Failed processing 0 files

Fix: F-82434r1129036_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" (WN25-SO-000240). 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 ALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files

b

Windows Server 2025 permissions for the Windows installation directory must conform to minimum requirements.

AC-3 - Medium - CCI-002165 - V-278000 - SV-278000r1129040_rule

RMF Control

AC-3

Severity

M

CCI

CCI-002165

Version

WN25-00-000160

Vuln IDs

V-278000

Rule IDs

SV-278000r1129040_rule

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" (WN25-SO-000240). Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124

Checks: C-82530r1129038_chk

The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN25-SO-000240). Review the 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. Individual accounts must not be used to assign permissions. If permissions are not as restrictive as the default permissions listed below, this is a finding: Viewing in File Explorer: For each folder, view the Properties. Select the "Security" tab, and then click "Advanced". 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 ALL RESTRICTED 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 must be displayed for each when entered: 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) APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(RX) APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE) Successfully processed 1 files; Failed processing 0 files

Fix: F-82435r1129039_fix

Maintain the default file ACLs and configure the Security Option "Network access: Let Everyone permissions apply to anonymous users" to "Disabled" (WN25-SO-000240). 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 ALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files

b

Windows Server 2025 default permissions for the HKEY_LOCAL_MACHINE registry hive must be maintained.

AC-6 - Medium - CCI-002235 - V-278001 - SV-278001r1129043_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN25-00-000170

Vuln IDs

V-278001

Rule IDs

SV-278001r1129043_rule

The registry is integral to the function, security, and stability of the Windows system. Changing the system's registry permissions allows the possibility of unauthorized and anonymous modification to the operating system.

Checks: C-82531r1129041_chk

Review the registry permissions for the keys of the HKEY_LOCAL_MACHINE hive noted below. If any nonprivileged groups such as Everyone, Users, or Authenticated Users have greater than Read permission, this is a finding. If permissions are not as restrictive as the default permissions listed below, this is a finding: Run "Regedit". Right-click on the registry areas noted below. Select "Permissions", and then click "Advanced". HKEY_LOCAL_MACHINE\SECURITY Type - "Allow" for all Inherited from - "None" for all Principal - Access - Applies to SYSTEM - Full Control - This key and subkeys Administrators - Special - This key and subkeys HKEY_LOCAL_MACHINE\SOFTWARE Type - "Allow" for all Inherited from - "None" for all Principal - Access - Applies to Users - Read - This key and subkeys Administrators - Full Control - This key and subkeys SYSTEM - Full Control - This key and subkeys CREATOR OWNER - Full Control - This key and subkeys ALL APPLICATION PACKAGES - Read - This key and subkeys HKEY_LOCAL_MACHINE\SYSTEM Type - "Allow" for all Inherited from - "None" for all Principal - Access - Applies to Users - Read - This key and subkeys Administrators - Full Control - This key and subkeys SYSTEM - Full Control - This key and subkeys CREATOR OWNER - Full Control - This key and Subkeys ALL APPLICATION PACKAGES - Read - This key and subkeys Server Operators - Read - This Key and subkeys (Domain controllers only) Other examples under the noted keys may also be sampled. There may be some instances where nonprivileged groups have greater than Read permission. Microsoft has given Read permission to the SOFTWARE and SYSTEM registry keys in Windows Server 2025 to the following SID. This is not a finding. S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4053264122-3456934681 If the defaults have not been changed, this is not a finding.

Fix: F-82436r1129042_fix

Maintain the default permissions for the HKEY_LOCAL_MACHINE registry hive. The default permissions of the higher-level keys are noted below: HKEY_LOCAL_MACHINE\SECURITY Type - "Allow" for all Inherited from - "None" for all Principal - Access - Applies to SYSTEM - Full Control - This key and subkeys Administrators - Special - This key and subkeys HKEY_LOCAL_MACHINE\SOFTWARE Type - "Allow" for all Inherited from - "None" for all Principal - Access - Applies to Users - Read - This key and subkeys Administrators - Full Control - This key and subkeys SYSTEM - Full Control - This key and subkeys CREATOR OWNER - Full Control - This key and subkeys ALL APPLICATION PACKAGES - Read - This key and subkeys HKEY_LOCAL_MACHINE\SYSTEM Type - "Allow" for all Inherited from - "None" for all Principal - Access - Applies to Users - Read - This key and subkeys Administrators - Full Control - This key and subkeys SYSTEM - Full Control - This key and subkeys CREATOR OWNER - Full Control - This key and subkeys ALL APPLICATION PACKAGES - Read - This key and subkeys Server Operators - Read - This Key and subkeys (Domain controllers only) Microsoft has given Read permission to the SOFTWARE and SYSTEM registry keys in Windows Server 2025 to the following SID: S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4053264122-3456934681

a

Windows Server 2025 nonadministrative accounts or groups must only have print permissions on printer shares.

AC-3 - Low - CCI-000213 - V-278002 - SV-278002r1130139_rule

RMF Control

AC-3

Severity

L

CCI

Version

WN25-00-000180

Vuln IDs

V-278002

Rule IDs

SV-278002r1130139_rule

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-82532r1130138_chk

Open "Printers & scanners" in "Settings". If there are no printers configured, this is not applicable. (Exclude Microsoft Print to PDF and Microsoft XPS Document Writer, which do not support sharing.) For each printer: Select the printer and "Manage". Select "Printer Properties". Select the "Sharing" tab. If "Share this printer" is checked, select the "Security" tab. If any standard user accounts or groups have permissions other than "Print", this is a finding. The default is for the "Everyone" group to be given Print permission. "All APPLICATION PACKAGES" and "CREATOR OWNER" are not standard user accounts.

Fix: F-82437r1129045_fix

Configure the permissions on shared printers to restrict standard users to only have Print permissions.

b

Windows Server 2025 outdated or unused accounts must be removed or disabled.

Medium - CCI-003627 - V-278003 - SV-278003r1130141_rule

RMF Control

Severity

M

CCI

CCI-003627

Version

WN25-00-000190

Vuln IDs

V-278003

Rule IDs

SV-278003r1130141_rule

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. Satisfies: SRG-OS-000118-GPOS-00060, SRG-OS-000590-GPOS-00110

Checks: C-82533r1130140_chk

Open Windows PowerShell. Domain Controllers: Enter "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. Member servers and standalone or nondomain joined systems: Copy or enter the lines below to the PowerShell window and enter. (Entering twice may be required.) ([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 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 information system security officer (ISSO).

Fix: F-82438r1129048_fix

Regularly review accounts to determine if they are still active. Remove or disable accounts that have not been used in the last 35 days.

b

Windows Server 2025 accounts must require passwords.

IA-2 - Medium - CCI-000764 - V-278004 - SV-278004r1129052_rule

RMF Control

IA-2

Severity

M

CCI

CCI-000764

Version

WN25-00-000200

Vuln IDs

V-278004

Rule IDs

SV-278004r1129052_rule

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-82534r1129050_chk

Review the password required status for enabled user accounts. Open PowerShell. Domain Controllers: Enter "Get-Aduser -Filter * -Properties Passwordnotrequired |FT Name, Passwordnotrequired, Enabled". Exclude disabled accounts (e.g., DefaultAccount, Guest) and Trusted Domain Objects (TDOs). If "Passwordnotrequired" is "True" or blank for any enabled user account, this is a finding. Member servers and standalone or nondomain joined systems: Enter 'Get-CimInstance -Class Win32_Useraccount -Filter "PasswordRequired=False and LocalAccount=True" | FT Name, PasswordRequired, Disabled, LocalAccount'. Exclude disabled accounts (e.g., DefaultAccount, Guest). If any enabled user accounts are returned with a "PasswordRequired" status of "False", this is a finding.

Fix: F-82439r1129051_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 Server 2025 passwords must be configured to expire.

Medium - CCI-004066 - V-278005 - SV-278005r1129055_rule

RMF Control

Severity

M

CCI

Version

WN25-00-000210

Vuln IDs

V-278005

Rule IDs

SV-278005r1129055_rule

Passwords that do not expire or are reused increase the exposure of a password with greater probability of being discovered or cracked.

Checks: C-82535r1129053_chk

Review the password never expires status for enabled user accounts. Open PowerShell. Domain Controllers: Enter "Search-ADAccount -PasswordNeverExpires -UsersOnly | FT Name, PasswordNeverExpires, Enabled". Exclude application accounts, disabled accounts (e.g., DefaultAccount, Guest) and the krbtgt account. If any enabled user accounts are returned with a "PasswordNeverExpires" status of "True", this is a finding. Member servers and standalone or nondomain joined 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., DefaultAccount, Guest). If any enabled user accounts are returned with a "PasswordExpires" status of "False", this is a finding.

Fix: F-82440r1129054_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 or nondomain joined systems. Document any exceptions with the information system security officer (ISSO).

b

Windows Server 2025 system files must be monitored for unauthorized changes.

CM-3 - Medium - CCI-001744 - V-278006 - SV-278006r1129058_rule

RMF Control

CM-3

Severity

M

CCI

CCI-001744

Version

WN25-00-000220

Vuln IDs

V-278006

Rule IDs

SV-278006r1129058_rule

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-82536r1129056_chk

Determine whether the system is monitored for unauthorized changes to system files (e.g., *.exe, *.bat, *.com, *.cmd, and *.dll) against a baseline on a weekly basis. If system files are not monitored for unauthorized changes, this is a finding. A properly configured and approved DOD ESS solution that supports a File Integrity Monitor (FIM) module will meet the requirement for file integrity checking.

Fix: F-82441r1129057_fix

Monitor the system for unauthorized changes to system files (e.g., *.exe, *.bat, *.com, *.cmd, and *.dll) against a baseline on a weekly basis. This can be done with the use of various monitoring tools.

b

Windows Server 2025 nonsystem-created file shares must limit access to groups that require it.

SC-4 - Medium - CCI-001090 - V-278007 - SV-278007r1130143_rule

RMF Control

SC-4

Severity

M

CCI

Version

WN25-00-000230

Vuln IDs

V-278007

Rule IDs

SV-278007r1130143_rule

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 accounts that require it.

Checks: C-82537r1130142_chk

If only system-created shares such as "ADMIN$", "C$", and "IPC$" exist on the system, this is not applicable. (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 nonsystem-created shares. Select "Properties". Select the "Share Permissions" tab. If the file shares have not been configured to restrict permissions to the specific groups or accounts that require access, this is a finding. Select the "Security" tab. If the permissions have not been configured to restrict permissions to the specific groups or accounts that require access, this is a finding.

Fix: F-82442r1129060_fix

If a nonsystem-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 nonsystem-created shares.

b

Windows Server 2025 must have software certificate installation files removed.

CM-6 - Medium - CCI-000366 - V-278008 - SV-278008r1129064_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-00-000240

Vuln IDs

V-278008

Rule IDs

SV-278008r1129064_rule

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-82538r1129062_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 .p12 certificate files or Adobe PreFlight certificate files. Some applications create files with extensions of .p12 that are not certificate installation files. Removal of noncertificate installation files from systems is not required. These must be documented with the information system security officer (ISSO).

Fix: F-82443r1129063_fix

Remove any certificate installation files (*.p12 and *.pfx) found on a system. Note: This does not apply to server-based applications that have a requirement for .p12 certificate files or Adobe PreFlight certificate files.

b

Windows Server 2025 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-278009 - SV-278009r1129067_rule

RMF Control

SC-28

Severity

M

CCI

CCI-001199

Version

WN25-00-000250

Vuln IDs

V-278009

Rule IDs

SV-278009r1129067_rule

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). Satisfies: SRG-OS-000185-GPOS-00079, SRG-OS-000404-GPOS-00183, SRG-OS-000405-GPOS-00184

Checks: C-82539r1129065_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 they do not, this is a finding.

Fix: F-82444r1129066_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.

b

Windows Server 2025 must implement protection methods such as TLS, encrypted VPNs, or IPsec 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-278010 - SV-278010r1129070_rule

RMF Control

SC-8

Severity

M

CCI

CCI-002420

Version

WN25-00-000260

Vuln IDs

V-278010

Rule IDs

SV-278010r1129070_rule

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. Satisfies: SRG-OS-000425-GPOS-00189, SRG-OS-000426-GPOS-00190

Checks: C-82540r1129068_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-82445r1129069_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.

b

Windows Server 2025 must have the roles and features required by the system documented.

CM-7 - Medium - CCI-000381 - V-278011 - SV-278011r1129073_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN25-00-000270

Vuln IDs

V-278011

Rule IDs

SV-278011r1129073_rule

Unnecessary roles and features increase the attack surface of a system. Limiting roles and features of a system to only those necessary reduces this potential. The standard installation option (previously called Server Core) further reduces this when selected at installation.

Checks: C-82541r1129071_chk

Required roles and features will vary based on the function of the individual system. Roles and features specifically required to be disabled per the STIG are identified in separate requirements. If the organization has not documented the roles and features required for the system(s), this is a finding. The PowerShell command "Get-WindowsFeature" will list all roles and features with an "Install State".

Fix: F-82446r1129072_fix

Document the roles and features required for the system to operate. Uninstall any that are not required.

b

Windows Server 2025 must have a host-based firewall installed and enabled.

CM-6 - Medium - CCI-000366 - V-278012 - SV-278012r1129076_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-00-000280

Vuln IDs

V-278012

Rule IDs

SV-278012r1129076_rule

A firewall provides a line of defense against attack, allowing or blocking inbound and outbound connections based on a set of rules. Satisfies: SRG-OS-000480-GPOS-00227, SRG-OS-000480-GPOS-00232

Checks: C-82542r1129074_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-82447r1129075_fix

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

b

Windows Server 2025 must automatically remove or disable temporary user accounts after 72 hours.

AC-2 - Medium - CCI-000016 - V-278013 - SV-278013r1130145_rule

RMF Control

AC-2

Severity

M

CCI

CCI-000016

Version

WN25-00-000300

Vuln IDs

V-278013

Rule IDs

SV-278013r1130145_rule

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-82543r1130144_chk

Review temporary user accounts for expiration dates. Determine if temporary user accounts are used and identify any that exist. If none exist, this is not applicable. Domain Controllers: Open PowerShell. Enter "Search-ADAccount -AccountExpiring | FT Name, AccountExpirationDate". If "AccountExpirationDate" has not been defined within 72 hours for any temporary user account, this is a finding. Member servers and standalone or nondomain joined systems: Open command prompt. Run "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.

Fix: F-82448r1129078_fix

Configure temporary user 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 temporary user account. Delete any temporary user accounts that are no longer necessary.

b

Windows Server 2025 must automatically remove or disable emergency accounts after the crisis is resolved or within 72 hours.

AC-2 - Medium - CCI-001682 - V-278014 - SV-278014r1130147_rule

RMF Control

AC-2

Severity

M

CCI

CCI-001682

Version

WN25-00-000310

Vuln IDs

V-278014

Rule IDs

SV-278014r1130147_rule

Emergency administrator accounts are privileged accounts 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 must 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-82544r1130146_chk

Determine if emergency administrator accounts are used and identify any that exist. If none exist, this is not applicable. 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: Open PowerShell. Enter "Search-ADAccount -AccountExpiring | FT Name, AccountExpirationDate". If "AccountExpirationDate" has been defined and is not within 72 hours for an emergency administrator account, this is a finding. Member servers and standalone or nondomain joined systems: Open command prompt. Run "Net user [username]", where [username] is the name of the emergency account. If "Account expires" has been defined and is not within 72 hours for an emergency administrator account, this is a finding.

Fix: F-82449r1129081_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 temporary user account.

b

Windows Server 2025 must not have the Fax Server role installed.

CM-7 - Medium - CCI-000381 - V-278015 - SV-278015r1129085_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN25-00-000320

Vuln IDs

V-278015

Rule IDs

SV-278015r1129085_rule

Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access to the system.

Checks: C-82545r1129083_chk

Open PowerShell. Enter "Get-WindowsFeature | Where Name -eq Fax". If "Installed State" is "Installed", this is a finding. An Installed State of "Available" or "Removed" is not a finding.

Fix: F-82450r1129084_fix

Uninstall the "Fax Server" role. Start Server Manager. Select the server with the role. Scroll down to "ROLES AND FEATURES" in the right pane. Select "Remove Roles and Features" from the drop-down "TASKS" list. Select the appropriate server on the "Server Selection" page and click "Next". Deselect "Fax Server" on the "Roles" page. Click "Next" and "Remove" as prompted.

b

Windows Server 2025 must not have the Microsoft FTP service installed unless required by the organization.

CM-7 - Medium - CCI-000382 - V-278016 - SV-278016r1130149_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN25-00-000330

Vuln IDs

V-278016

Rule IDs

SV-278016r1130149_rule

Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption.

Checks: C-82546r1130148_chk

If the server has the role of an FTP server, this is not applicable. Open PowerShell. Enter "Get-WindowsFeature | Where Name -eq Web-Ftp-Service". If "Installed State" is "Installed", this is a finding. An Installed State of "Available" or "Removed" is not a finding. If the system has the role of an FTP server, this must be documented with the information system security officer (ISSO).

Fix: F-82451r1129087_fix

Uninstall the "FTP Server" role. Start Server Manager. Select the server with the role. Scroll down to "ROLES AND FEATURES" in the right pane. Select "Remove Roles and Features" from the drop-down "TASKS" list. Select the appropriate server on the "Server Selection" page and click "Next". Deselect "FTP Server" under "Web Server (IIS)" on the "Roles" page. Click "Next" and "Remove" as prompted.

b

Windows Server 2025 must not have Wi-Fi enabled unless required by the organization.

CM-7 - Medium - CCI-000382 - V-278017 - SV-278017r1129091_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN25-00-000332

Vuln IDs

V-278017

Rule IDs

SV-278017r1129091_rule

Unnecessary connections could increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption.

Checks: C-82547r1129089_chk

Open PowerShell or a Command prompt. Type "IP Config /All". If there is a connection named "Wi-Fi" or "Wireless", this is a finding.

Fix: F-82452r1129090_fix

Validate the site documentation to ensure the approval of use for Wi-Fi server connections. If the connection (s) have not been approved, go to "Settings" then "Network and Internet" and remove/disable the Wi-Fi adapter. Any Wi-Fi connections listed or in use must be documented and approved by the information system security officer (ISSO) or authorizing official (AO).

b

Windows Server 2025 must not have Bluetooth enabled unless required by the organization.

CM-7 - Medium - CCI-000382 - V-278018 - SV-278018r1129094_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN25-00-000333

Vuln IDs

V-278018

Rule IDs

SV-278018r1129094_rule

Unnecessary applications and/or services such as Bluetooth could allow an attacker to connect with intentions to take over or disrupt the system.

Checks: C-82548r1129092_chk

In the Windows search bar, type "Services". In the Services "Name" column look for the "Bluetooth Support Service". If this is set to "automatic", this is a finding.

Fix: F-82453r1129093_fix

Validate the site documentation to ensure the approval of use for Wi-Fi server connections. If the connection has not been approved, type "Services" in the Windows search bar. In the Services "Name " column, look for the "Bluetooth Support Service" and set this to "Disabled". Any Bluetooth devices listed or in use must be documented and approved by the information system security officer (ISSO) or authorizing official (AO).

b

Windows Server 2025 must not have the Peer Name Resolution Protocol installed.

CM-7 - Medium - CCI-000381 - V-278019 - SV-278019r1129097_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN25-00-000340

Vuln IDs

V-278019

Rule IDs

SV-278019r1129097_rule

Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access to the system.

Checks: C-82549r1129095_chk

Open PowerShell. Enter "Get-WindowsFeature | Where Name -eq PNRP". If "Installed State" is "Installed", this is a finding. An Installed State of "Available" or "Removed" is not a finding.

Fix: F-82454r1129096_fix

Uninstall the "Peer Name Resolution Protocol" feature. Start Server Manager. Select the server with the feature. Scroll down to "ROLES AND FEATURES" in the right pane. Select "Remove Roles and Features" from the drop-down "TASKS" list. Select the appropriate server on the "Server Selection" page and click "Next". Deselect "Peer Name Resolution Protocol" on the "Features" page. Click "Next" and "Remove" as prompted.

b

Windows Server 2025 must not have Simple TCP/IP Services installed.

CM-7 - Medium - CCI-000381 - V-278020 - SV-278020r1129100_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN25-00-000350

Vuln IDs

V-278020

Rule IDs

SV-278020r1129100_rule

Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access to the system.

Checks: C-82550r1129098_chk

Open PowerShell. Enter "Get-WindowsFeature | Where Name -eq Simple-TCPIP". If "Installed State" is "Installed", this is a finding. An Installed State of "Available" or "Removed" is not a finding.

Fix: F-82455r1129099_fix

Uninstall the "Simple TCP/IP Services" feature. Start Server Manager. Select the server with the feature. Scroll down to "ROLES AND FEATURES" in the right pane. Select "Remove Roles and Features" from the drop-down "TASKS" list. Select the appropriate server on the "Server Selection" page and click "Next". Deselect "Simple TCP/IP Services" on the "Features" page. Click "Next" and "Remove" as prompted.

b

Windows Server 2025 must not have the Telnet Client installed.

CM-7 - Medium - CCI-000382 - V-278021 - SV-278021r1129103_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN25-00-000360

Vuln IDs

V-278021

Rule IDs

SV-278021r1129103_rule

Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access to the system.

Checks: C-82551r1129101_chk

Open PowerShell. Enter "Get-WindowsFeature | Where Name -eq Telnet-Client". If "Installed State" is "Installed", this is a finding. An Installed State of "Available" or "Removed" is not a finding.

Fix: F-82456r1129102_fix

Uninstall the "Telnet Client" feature. Start Server Manager. Select the server with the feature. Scroll down to "ROLES AND FEATURES" in the right pane. Select "Remove Roles and Features" from the drop-down "TASKS" list. Select the appropriate server on the "Server Selection" page and click "Next". Deselect "Telnet Client" on the "Features" page. Click "Next" and "Remove" as prompted.

b

Windows Server 2025 must not have the TFTP Client installed.

CM-7 - Medium - CCI-000381 - V-278022 - SV-278022r1129106_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN25-00-000370

Vuln IDs

V-278022

Rule IDs

SV-278022r1129106_rule

Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access to the system.

Checks: C-82552r1129104_chk

Open PowerShell. Enter "Get-WindowsFeature | Where Name -eq TFTP-Client". If "Installed State" is "Installed", this is a finding. An Installed State of "Available" or "Removed" is not a finding.

Fix: F-82457r1129105_fix

Uninstall the "TFTP Client" feature. Start Server Manager. Select the server with the feature. Scroll down to "ROLES AND FEATURES" in the right pane. Select "Remove Roles and Features" from the drop-down "TASKS" list. Select the appropriate server on the "Server Selection" page and click "Next". Deselect "TFTP Client" on the "Features" page. Click "Next" and "Remove" as prompted.

b

Windows Server 2025 must not have the Server Message Block (SMB) v1 protocol installed.

CM-7 - Medium - CCI-000381 - V-278023 - SV-278023r1130151_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN25-00-000380

Vuln IDs

V-278023

Rule IDs

SV-278023r1130151_rule

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 and is not FIPS-compliant.

Checks: C-82553r1130150_chk

Different methods are available to disable SMBv1 on Windows Server 2025. This is the preferred method, however if WN25-00-000390 and WN25-00-000400 are configured, this is not applicable. Open Windows PowerShell with elevated privileges (run as administrator). Enter "Get-WindowsFeature -Name FS-SMB1". If "Installed State" is "Installed", this is a finding. An Installed State of "Available" or "Removed" is not a finding.

Fix: F-82458r1129108_fix

Uninstall the SMBv1 protocol. Open Windows PowerShell with elevated privileges (run as administrator). Enter "Uninstall-WindowsFeature -Name FS-SMB1 -Restart". (Omit the Restart parameter if an immediate restart of the system cannot be done.) Alternately: Start Server Manager. Select the server with the feature. Scroll down to "ROLES AND FEATURES" in the right pane. Select "Remove Roles and Features" from the drop-down "TASKS" list. Select the appropriate server on the "Server Selection" page and click "Next". Deselect "SMB 1.0/CIFS File Sharing Support" on the "Features" page. Click "Next" and "Remove" as prompted.

b

Windows Server 2025 must have the Server Message Block (SMB) v1 protocol disabled on the SMB server.

CM-7 - Medium - CCI-000381 - V-278024 - SV-278024r1130153_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN25-00-000390

Vuln IDs

V-278024

Rule IDs

SV-278024r1130153_rule

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.

Checks: C-82554r1130152_chk

Different methods are available to disable SMBv1 on Windows Server 2025, if WN25-00-000380 is configured, this is not applicable. 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-82459r1129111_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

Windows Server 2025 must have the Server Message Block (SMB) v1 protocol disabled on the SMB client.

CM-7 - Medium - CCI-000381 - V-278025 - SV-278025r1130155_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN25-00-000400

Vuln IDs

V-278025

Rule IDs

SV-278025r1130155_rule

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.

Checks: C-82555r1130154_chk

Different methods are available to disable SMBv1 on Windows Server 2025, if WN25-00-000380 is configured, this is not applicable. 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)

Fix: F-82460r1129114_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". The system must be restarted for the changes 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

Windows Server 2025 must not have Windows PowerShell 2.0 installed.

CM-7 - Medium - CCI-000381 - V-278026 - SV-278026r1129118_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN25-00-000410

Vuln IDs

V-278026

Rule IDs

SV-278026r1129118_rule

Windows PowerShell 5.x added advanced logging features that can provide additional detail when malware has been run on a system. Disabling the Windows PowerShell 2.0 mitigates against a downgrade attack that evades the Windows PowerShell 5.x script block logging feature.

Checks: C-82556r1129116_chk

Open PowerShell. Enter "Get-WindowsFeature | Where Name -eq PowerShell-v2". If "Installed State" is "Installed", this is a finding. An Installed State of "Available" or "Removed" is not a finding.

Fix: F-82461r1129117_fix

Uninstall the Windows PowerShell 2.0 Engine. Start Server Manager. Select the server with the feature. Scroll down to "ROLES AND FEATURES" in the right pane. Select "Remove Roles and Features" from the drop-down "TASKS" list. Select the appropriate server on the "Server Selection" page and click "Next". Deselect "Windows PowerShell 2.0 Engine" under "Windows PowerShell" on the "Features" page. Click "Next" and "Remove" as prompted.

b

Windows Server 2025 FTP servers must be configured to prevent anonymous logons.

CM-6 - Medium - CCI-000366 - V-278027 - SV-278027r1130157_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-00-000420

Vuln IDs

V-278027

Rule IDs

SV-278027r1130157_rule

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-82557r1130156_chk

If FTP is not installed on the system, this is not applicable. Open Internet Information Services (IIS) Manager. Select the server. Double-click "FTP Authentication". If the "Anonymous Authentication" status is "Enabled", this is a finding.

Fix: F-82462r1129120_fix

Configure the FTP service to prevent anonymous logons. Open IIS Manager. Select the server. Double-click "FTP Authentication". Select "Anonymous Authentication". Select "Disabled" under "Actions".

b

Windows Server 2025 FTP servers must be configured to prevent access to the system drive.

CM-6 - Medium - CCI-000366 - V-278028 - SV-278028r1130159_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-00-000430

Vuln IDs

V-278028

Rule IDs

SV-278028r1130159_rule

The FTP service allows remote users to access shared files and directories that could provide access to system resources and compromise the system, especially if the user can gain access to the root directory of the boot drive.

Checks: C-82558r1130158_chk

If FTP is not installed on the system, this is not applicable. Open "Internet Information Services (IIS) Manager". Select "Sites" under the server name. For any sites with a Binding that lists FTP, right-click the site and select "Explore". If the site is not defined to a specific folder for shared FTP resources, this is a finding. If the site includes any system areas such as root of the drive, Program Files, or Windows directories, this is a finding.

Fix: F-82463r1129123_fix

Configure the FTP sites to allow access only to specific FTP shared resources. Do not allow access to other areas of the system.

a

The Windows Server 2025 time service must synchronize with an appropriate DOD time source.

Low - CCI-004923 - V-278029 - SV-278029r1129127_rule

RMF Control

Severity

L

CCI

CCI-004923

Version

WN25-00-000440

Vuln IDs

V-278029

Rule IDs

SV-278029r1129127_rule

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-82559r1129125_chk

Review the Windows time service configuration. Open an elevated command prompt (run as administrator). Enter "W32tm /query /configuration". Domain-joined systems (excluding the domain controller with the PDC emulator role): If the value for "Type" under "NTP Client" is not "NT5DS", this is a finding. Other systems: If systems are configured with a "Type" of "NTP", including standalone or nondomain joined systems and the domain controller with the PDC Emulator role, and do not have a DOD time server defined for "NTPServer", this is a finding. To determine the domain controller with the PDC Emulator role: Open PowerShell. Enter "Get-ADDomain | FT PDCEmulator".

Fix: F-82464r1129126_fix

Configure the system to synchronize time with an appropriate DOD time source. Domain-joined systems use NT5DS to synchronize time from other systems in the domain by default. 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. Change "Configure Windows NTP Client" to "Enabled" and configure the "NtpServer" field to point to an appropriate DOD time server. The US Naval Observatory operates stratum one-time servers, identified at https://www.usno.navy.mil/USNO/time/ntp/DOD-customers. 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.

b

Windows Server 2025 must have orphaned security identifiers (SIDs) removed from user rights.

CM-6 - Medium - CCI-000366 - V-278030 - SV-278030r1129130_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-00-000450

Vuln IDs

V-278030

Rule IDs

SV-278030r1129130_rule

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.

Checks: C-82560r1129128_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 that begins with "*S-1-".) If any unresolved SIDs exist and are not for currently valid accounts or groups, this is a finding. For server core installations, run the following command: Secedit /export /areas USER_RIGHTS /cfg c:\path\UserRights.txt The results in the file identify user right assignments by SID instead of group name. Review the SIDs to determine which are unidentified. A list of typical SIDs\Groups is below; search Microsoft for articles on well-known SIDs for others. If any unresolved SIDs exist and are not for currently valid accounts or groups, this is a finding. SID - Group S-1-5-11 - Authenticated Users S-1-5-113 - Local account S-1-5-114 - Local account and member of Administrators group S-1-5-19 - Local Service S-1-5-20 - Network Service S-1-5-32-544 - Administrators S-1-5-32-546 - Guests S-1-5-6 - Service S-1-5-9 - Enterprise Domain Controllers S-1-5-domain-512 - Domain Admins S-1-5-root domain-519 - Enterprise Admins S-1-5-80-3139157870-2983391045-3678747466-658725712-1809340420 - NT Service\WdiServiceHost

Fix: F-82465r1129129_fix

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

b

Windows Server 2025 systems must have Unified Extensible Firmware Interface (UEFI) firmware and be configured to run in UEFI mode, not Legacy BIOS.

CM-6 - Medium - CCI-000366 - V-278031 - SV-278031r1129133_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-00-000460

Vuln IDs

V-278031

Rule IDs

SV-278031r1129133_rule

UEFI provides additional security features in comparison to legacy BIOS firmware, including Secure Boot. UEFI is required to support additional security features in Windows, including Virtualization Based Security and Credential Guard. Systems with UEFI that are operating in "Legacy BIOS" mode will not support these security features.

Checks: C-82561r1129131_chk

Devices that have UEFI firmware must run in "UEFI" mode. Verify the system firmware is configured to run in "UEFI" mode, not "Legacy BIOS". Run "System Information". Under "System Summary", if "BIOS Mode" does not display "UEFI", this is a finding.

Fix: F-82466r1129132_fix

Configure UEFI firmware to run in "UEFI" mode, not "Legacy BIOS" mode.

b

Windows Server 2025 must have Secure Boot enabled.

CM-6 - Medium - CCI-000366 - V-278032 - SV-278032r1129136_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-00-000470

Vuln IDs

V-278032

Rule IDs

SV-278032r1129136_rule

Secure Boot is a standard that ensures systems boot only to a trusted operating system. Secure Boot is required to support additional security features in Windows, including Virtualization Based Security and Credential Guard. If Secure Boot is turned off, these security features will not function.

Checks: C-82562r1129134_chk

Devices that have UEFI firmware must have Secure Boot enabled. Run "System Information". Under "System Summary", if "Secure Boot State" does not display "On", this is a finding. On server core installations, run the following PowerShell command: Confirm-SecureBootUEFI If a value of "True" is not returned, this is a finding.

Fix: F-82467r1129135_fix

Enable Secure Boot in the system firmware.

b

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

AC-7 - Medium - CCI-002238 - V-278033 - SV-278033r1129139_rule

RMF Control

AC-7

Severity

M

CCI

CCI-002238

Version

WN25-AC-000010

Vuln IDs

V-278033

Rule IDs

SV-278033r1129139_rule

When enabled, the account lockout feature 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-82563r1129137_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. For server core installations, run the following command: Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt If "LockoutDuration" is less than "15" (excluding "0") in the file, 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-82468r1129138_fix

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

b

Windows Server 2025 must have the number of allowed bad logon attempts configured to three or less.

AC-7 - Medium - CCI-000044 - V-278034 - SV-278034r1129142_rule

RMF Control

AC-7

Severity

M

CCI

CCI-000044

Version

WN25-AC-000020

Vuln IDs

V-278034

Rule IDs

SV-278034r1129142_rule

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 normal user logon.

Checks: C-82564r1129140_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. For server core installations, run the following command: Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt If "LockoutBadCount" equals "0" or is greater than "3" in the file, this is a finding.

Fix: F-82469r1129141_fix

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

b

Windows Server 2025 must have the period of time before the bad logon counter is reset configured to 15 minutes or greater.

AC-7 - Medium - CCI-000044 - V-278035 - SV-278035r1129145_rule

RMF Control

AC-7

Severity

M

CCI

CCI-000044

Version

WN25-AC-000030

Vuln IDs

V-278035

Rule IDs

SV-278035r1129145_rule

When enabled, the account lockout feature 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-82565r1129143_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. For server core installations, run the following command: Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt If "ResetLockoutCount" is less than "15" in the file, this is a finding.

Fix: F-82470r1129144_fix

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

b

Windows Server 2025 password history must be configured to 24 passwords remembered.

Medium - CCI-004061 - V-278036 - SV-278036r1129148_rule

RMF Control

Severity

M

CCI

CCI-004061

Version

WN25-AC-000040

Vuln IDs

V-278036

Rule IDs

SV-278036r1129148_rule

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-82566r1129146_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. For server core installations, run the following command: Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt If "PasswordHistorySize" is less than "24" in the file, this is a finding.

Fix: F-82471r1129147_fix

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

b

Windows Server 2025 maximum password age must be configured to 60 days or less.

Medium - CCI-004066 - V-278037 - SV-278037r1129151_rule

RMF Control

Severity

M

CCI

Version

WN25-AC-000050

Vuln IDs

V-278037

Rule IDs

SV-278037r1129151_rule

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-82567r1129149_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. For server core installations, run the following command: Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt If "MaximumPasswordAge" is greater than "60" or equal to "0" in the file, this is a finding.

Fix: F-82472r1129150_fix

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

b

Windows Server 2025 minimum password age must be configured to at least one day.

Medium - CCI-004066 - V-278038 - SV-278038r1129154_rule

RMF Control

Severity

M

CCI

Version

WN25-AC-000060

Vuln IDs

V-278038

Rule IDs

SV-278038r1129154_rule

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-82568r1129152_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. For server core installations, run the following command: Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt If "MinimumPasswordAge" equals "0" in the file, this is a finding.

Fix: F-82473r1129153_fix

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

b

Windows Server 2025 must have the built-in Windows password complexity policy enabled.

Medium - CCI-004066 - V-278039 - SV-278039r1129157_rule

RMF Control

Severity

M

CCI

Version

WN25-AC-000080

Vuln IDs

V-278039

Rule IDs

SV-278039r1129157_rule

The use of complex passwords increases their strength against attack. The built-in Windows password complexity policy requires passwords to contain at least three of the four types of characters (numbers, uppercase and lowercase letters, and special characters) and prevents the inclusion of user names or parts of user names. Satisfies: SRG-OS-000069-GPOS-00037, SRG-OS-000070-GPOS-00038, SRG-OS-000071-GPOS-00039, SRG-OS-000266-GPOS-00101

Checks: C-82569r1129155_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. For server core installations, run the following command: Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt If "PasswordComplexity" equals "0" in the file, this is a finding. Note: If an external password filter is in use that enforces all four character types and requires this setting to 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-82474r1129156_fix

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

c

Windows Server 2025 reversible password encryption must be disabled.

High - CCI-004062 - V-278040 - SV-278040r1129160_rule

RMF Control

Severity

H

CCI

CCI-004062

Version

WN25-AC-000090

Vuln IDs

V-278040

Rule IDs

SV-278040r1129160_rule

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

Checks: C-82570r1129158_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 passwords using reversible encryption" is not set to "Disabled", this is a finding. For server core installations, run the following command: Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt If "ClearTextPassword" equals "1" in the file, this is a finding.

Fix: F-82475r1129159_fix

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

b

Windows Server 2025 audit records must be backed up to a different system or media than the system being audited.

AU-4 - Medium - CCI-001851 - V-278041 - SV-278041r1129163_rule

RMF Control

AU-4

Severity

M

CCI

CCI-001851

Version

WN25-AU-000010

Vuln IDs

V-278041

Rule IDs

SV-278041r1129163_rule

Protection of log data includes ensuring 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-82571r1129161_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-82476r1129162_fix

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

b

Windows Server 2025 must, at a minimum, off-load audit records of interconnected systems in real time and off-load standalone or nondomain joined systems weekly.

AU-4 - Medium - CCI-001851 - V-278042 - SV-278042r1129166_rule

RMF Control

AU-4

Severity

M

CCI

CCI-001851

Version

WN25-AU-000020

Vuln IDs

V-278042

Rule IDs

SV-278042r1129166_rule

Protection of log data includes ensuring 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-82572r1129164_chk

Verify the audit records, at a minimum, are off-loaded for interconnected systems in real time and off-loaded for standalone or nondomain joined systems weekly. If they are not, this is a finding.

Fix: F-82477r1129165_fix

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

b

Windows Server 2025 permissions for the Application event log must prevent access by nonprivileged accounts.

AU-9 - Medium - CCI-000162 - V-278043 - SV-278043r1129169_rule

RMF Control

AU-9

Severity

M

CCI

Version

WN25-AU-000030

Vuln IDs

V-278043

Rule IDs

SV-278043r1129169_rule

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. Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029

Checks: C-82573r1129167_chk

Navigate to the Application event log file. The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. If the permissions for the "Application.evtx" file are not as restrictive as the default permissions listed below, this is a finding: Eventlog - Full Control SYSTEM - Full Control Administrators - Full Control

Fix: F-82478r1129168_fix

Configure the permissions on the Application event log file (Application.evtx) to prevent access by nonprivileged accounts. 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" folder. If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog".

b

Windows Server 2025 permissions for the Security event log must prevent access by nonprivileged accounts.

AU-9 - Medium - CCI-000162 - V-278044 - SV-278044r1129172_rule

RMF Control

AU-9

Severity

M

CCI

Version

WN25-AU-000040

Vuln IDs

V-278044

Rule IDs

SV-278044r1129172_rule

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. Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029

Checks: C-82574r1129170_chk

Navigate to the Security event log file. The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. If the permissions for the "Security.evtx" file are not as restrictive as the default permissions listed below, this is a finding: Eventlog - Full Control SYSTEM - Full Control Administrators - Full Control

Fix: F-82479r1129171_fix

Configure the permissions on the Security event log file (Security.evtx) to prevent access by nonprivileged accounts. 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" folder. If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog".

b

Windows Server 2025 permissions for the System event log must prevent access by nonprivileged accounts.

AU-9 - Medium - CCI-000162 - V-278045 - SV-278045r1129175_rule

RMF Control

AU-9

Severity

M

CCI

Version

WN25-AU-000050

Vuln IDs

V-278045

Rule IDs

SV-278045r1129175_rule

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. Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029

Checks: C-82575r1129173_chk

Navigate to the System event log file. The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. If the permissions for the "System.evtx" file are not as restrictive as the default permissions listed below, this is a finding: Eventlog - Full Control SYSTEM - Full Control Administrators - Full Control

Fix: F-82480r1129174_fix

Configure the permissions on the System event log file (System.evtx) to prevent access by nonprivileged accounts. 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" folder. If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog".

b

Windows Server 2025 Event Viewer must be protected from unauthorized modification and deletion.

AU-9 - Medium - CCI-001494 - V-278046 - SV-278046r1129178_rule

RMF Control

AU-9

Severity

M

CCI

CCI-001494

Version

WN25-AU-000060

Vuln IDs

V-278046

Rule IDs

SV-278046r1129178_rule

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 to make access decisions regarding the modification or deletion of audit tools. Satisfies: SRG-OS-000257-GPOS-00098, SRG-OS-000258-GPOS-00099

Checks: C-82576r1129176_chk

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

Fix: F-82481r1129177_fix

Configure the permissions on the "Eventvwr.exe" file to prevent modification by any groups or accounts other than TrustedInstaller. The default permissions listed below satisfy this requirement: TrustedInstaller - Full Control Administrators, SYSTEM, Users, ALL APPLICATION PACKAGES, ALL RESTRICTED APPLICATION PACKAGES - Read & Execute The default location is the "%SystemRoot%\System32" folder.

b

Windows Server 2025 must be configured to audit Account Logon - Credential Validation successes.

AU-12 - Medium - CCI-000172 - V-278047 - SV-278047r1129181_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-AU-000070

Vuln IDs

V-278047

Rule IDs

SV-278047r1129181_rule

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-82577r1129179_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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-82482r1129180_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

Windows Server 2025 must be configured to audit Account Logon - Credential Validation failures.

AU-12 - Medium - CCI-000172 - V-278048 - SV-278048r1129184_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-AU-000080

Vuln IDs

V-278048

Rule IDs

SV-278048r1129184_rule

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-82578r1129182_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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-82483r1129183_fix

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

b

Windows Server 2025 must be configured to audit Account Management - Other Account Management Events successes.

AU-12 - Medium - CCI-000172 - V-278049 - SV-278049r1129187_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-AU-000090

Vuln IDs

V-278049

Rule IDs

SV-278049r1129187_rule

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. Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210

Checks: C-82579r1129185_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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-82484r1129186_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

Windows Server 2025 must be configured to audit Account Management - Security Group Management successes.

AC-2 - Medium - CCI-000018 - V-278050 - SV-278050r1129190_rule

RMF Control

AC-2

Severity

M

CCI

Version

WN25-AU-000100

Vuln IDs

V-278050

Rule IDs

SV-278050r1129190_rule

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. Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221

Checks: C-82580r1129188_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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-82485r1129189_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

Windows Server 2025 must be configured to audit Account Management - User Account Management successes.

AC-2 - Medium - CCI-000018 - V-278051 - SV-278051r1129193_rule

RMF Control

AC-2

Severity

M

CCI

Version

WN25-AU-000110

Vuln IDs

V-278051

Rule IDs

SV-278051r1129193_rule

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. Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221

Checks: C-82581r1129191_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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-82486r1129192_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

Windows Server 2025 must be configured to audit Account Management - User Account Management failures.

AC-2 - Medium - CCI-000018 - V-278052 - SV-278052r1129196_rule

RMF Control

AC-2

Severity

M

CCI

Version

WN25-AU-000120

Vuln IDs

V-278052

Rule IDs

SV-278052r1129196_rule

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. Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221

Checks: C-82582r1129194_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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-82487r1129195_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

Windows Server 2025 must be configured to audit Detailed Tracking - Plug and Play Events successes.

AU-12 - Medium - CCI-000172 - V-278053 - SV-278053r1129199_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-AU-000130

Vuln IDs

V-278053

Rule IDs

SV-278053r1129199_rule

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. Plug and Play activity records events related to the successful connection of external devices.

Checks: C-82583r1129197_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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 >> Plug and Play Events - Success

Fix: F-82488r1129198_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Detailed Tracking >> Audit PNP Activity with "Success" selected.

b

Windows Server 2025 must be configured to audit Detailed Tracking - Process Creation successes.

AU-12 - Medium - CCI-000172 - V-278054 - SV-278054r1129202_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-AU-000140

Vuln IDs

V-278054

Rule IDs

SV-278054r1129202_rule

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. Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215

Checks: C-82584r1129200_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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-82489r1129201_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 2025 must be configured to audit Logon/Logoff - Account Lockout successes.

AU-12 - Medium - CCI-000172 - V-278055 - SV-278055r1129205_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-AU-000150

Vuln IDs

V-278055

Rule IDs

SV-278055r1129205_rule

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. Satisfies: SRG-OS-000240-GPOS-00090, SRG-OS-000470-GPOS-00214

Checks: C-82585r1129203_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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 >> Account Lockout - Success

Fix: F-82490r1129204_fix

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

b

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

AU-12 - Medium - CCI-000172 - V-278056 - SV-278056r1129208_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-AU-000160

Vuln IDs

V-278056

Rule IDs

SV-278056r1129208_rule

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. Satisfies: SRG-OS-000240-GPOS-00090, SRG-OS-000470-GPOS-00214

Checks: C-82586r1129206_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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 >> Account Lockout - Failure

Fix: F-82491r1129207_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

Windows Server 2025 must be configured to audit Logon/Logoff - Group Membership successes.

AU-12 - Medium - CCI-000172 - V-278057 - SV-278057r1129211_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-AU-000170

Vuln IDs

V-278057

Rule IDs

SV-278057r1129211_rule

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 Group Membership records information related to the group membership of a user's logon token.

Checks: C-82587r1129209_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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 >> Group Membership - Success

Fix: F-82492r1129210_fix

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

b

Windows Server 2025 must be configured to audit logoff successes.

AU-12 - Medium - CCI-000172 - V-278058 - SV-278058r1129214_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-AU-000180

Vuln IDs

V-278058

Rule IDs

SV-278058r1129214_rule

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-82588r1129212_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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-82493r1129213_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

Windows Server 2025 must be configured to audit logon successes.

AC-17 - Medium - CCI-000067 - V-278059 - SV-278059r1129217_rule

RMF Control

AC-17

Severity

M

CCI

CCI-000067

Version

WN25-AU-000190

Vuln IDs

V-278059

Rule IDs

SV-278059r1129217_rule

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. Satisfies: SRG-OS-000032-GPOS-00013, SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220

Checks: C-82589r1129215_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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-82494r1129216_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

Windows Server 2025 must be configured to audit logon failures.

AC-17 - Medium - CCI-000067 - V-278060 - SV-278060r1129220_rule

RMF Control

AC-17

Severity

M

CCI

CCI-000067

Version

WN25-AU-000200

Vuln IDs

V-278060

Rule IDs

SV-278060r1129220_rule

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. Satisfies: SRG-OS-000032-GPOS-00013, SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220

Checks: C-82590r1129218_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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-82495r1129219_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

Windows Server 2025 must be configured to audit Logon/Logoff - Special Logon successes.

AU-12 - Medium - CCI-000172 - V-278061 - SV-278061r1129223_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-AU-000210

Vuln IDs

V-278061

Rule IDs

SV-278061r1129223_rule

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 that have administrative privileges and can be used to elevate processes. Satisfies: SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220

Checks: C-82591r1129221_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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-82496r1129222_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

Windows Server 2025 must be configured to audit Object Access - Other Object Access Events successes.

AU-12 - Medium - CCI-000172 - V-278062 - SV-278062r1129226_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-AU-000220

Vuln IDs

V-278062

Rule IDs

SV-278062r1129226_rule

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. Auditing for other object access records events related to the management of task scheduler jobs and COM+ objects.

Checks: C-82592r1129224_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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 >> Other Object Access Events - Success

Fix: F-82497r1129225_fix

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

b

Windows Server 2025 must be configured to audit Object Access - Other Object Access Events failures.

AU-12 - Medium - CCI-000172 - V-278063 - SV-278063r1129229_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-AU-000230

Vuln IDs

V-278063

Rule IDs

SV-278063r1129229_rule

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. Auditing for other object access records events related to the management of task scheduler jobs and COM+ objects.

Checks: C-82593r1129227_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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 >> Other Object Access Events - Failure

Fix: F-82498r1129228_fix

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

b

Windows Server 2025 must be configured to audit Object Access - Removable Storage successes.

AU-12 - Medium - CCI-000172 - V-278064 - SV-278064r1129232_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-AU-000240

Vuln IDs

V-278064

Rule IDs

SV-278064r1129232_rule

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-82594r1129230_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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-82499r1129231_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

Windows Server 2025 must be configured to audit Object Access - Removable Storage failures.

AU-12 - Medium - CCI-000172 - V-278065 - SV-278065r1129235_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-AU-000250

Vuln IDs

V-278065

Rule IDs

SV-278065r1129235_rule

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-82595r1129233_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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-82500r1129234_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

Windows Server 2025 must be configured to audit Policy Change - Audit Policy Change successes.

AU-12 - Medium - CCI-000172 - V-278066 - SV-278066r1129238_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-AU-000260

Vuln IDs

V-278066

Rule IDs

SV-278066r1129238_rule

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. Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212

Checks: C-82596r1129236_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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 Audit Policy Change - Success

Fix: F-82501r1129237_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

Windows Server 2025 must be configured to audit Policy Change - Audit Policy Change failures.

AU-12 - Medium - CCI-000172 - V-278067 - SV-278067r1129241_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-AU-000270

Vuln IDs

V-278067

Rule IDs

SV-278067r1129241_rule

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. Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212

Checks: C-82597r1129239_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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 Audit Policy Change - Failure

Fix: F-82502r1129240_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

Windows Server 2025 must be configured to audit Policy Change - Authentication Policy Change successes.

AU-12 - Medium - CCI-000172 - V-278068 - SV-278068r1129244_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-AU-000280

Vuln IDs

V-278068

Rule IDs

SV-278068r1129244_rule

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. Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210

Checks: C-82598r1129242_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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-82503r1129243_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

Windows Server 2025 must be configured to audit Policy Change - Authorization Policy Change successes.

AU-12 - Medium - CCI-000172 - V-278069 - SV-278069r1129247_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-AU-000281

Vuln IDs

V-278069

Rule IDs

SV-278069r1129247_rule

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". Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210

Checks: C-82599r1129245_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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-82504r1129246_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

Windows Server 2025 must be configured to audit Privilege Use - Sensitive Privilege Use successes.

AU-12 - Medium - CCI-000172 - V-278070 - SV-278070r1129250_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-AU-000300

Vuln IDs

V-278070

Rule IDs

SV-278070r1129250_rule

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". Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210, SRG-OS-000755-GPOS-00220

Checks: C-82600r1129248_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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-82505r1129249_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

Windows Server 2025 must be configured to audit Privilege Use - Sensitive Privilege Use failures.

AU-12 - Medium - CCI-000172 - V-278071 - SV-278071r1129253_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-AU-000310

Vuln IDs

V-278071

Rule IDs

SV-278071r1129253_rule

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". Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210, SRG-OS-000755-GPOS-00220

Checks: C-82601r1129251_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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-82506r1129252_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

Windows Server 2025 must be configured to audit System - IPsec Driver successes.

AU-12 - Medium - CCI-000172 - V-278072 - SV-278072r1129256_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-AU-000320

Vuln IDs

V-278072

Rule IDs

SV-278072r1129256_rule

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. Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212

Checks: C-82602r1129254_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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-82507r1129255_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

Windows Server 2025 must be configured to audit System - IPsec Driver failures.

AU-12 - Medium - CCI-000172 - V-278073 - SV-278073r1129259_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-AU-000330

Vuln IDs

V-278073

Rule IDs

SV-278073r1129259_rule

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. Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212

Checks: C-82603r1129257_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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-82508r1129258_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 2025 must be configured to audit System - Other System Events successes.

AU-12 - Medium - CCI-000172 - V-278074 - SV-278074r1129262_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-AU-000340

Vuln IDs

V-278074

Rule IDs

SV-278074r1129262_rule

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-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212

Checks: C-82604r1129260_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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 >> Other System Events - Success

Fix: F-82509r1129261_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 2025 must be configured to audit System - Other System Events failures.

AU-12 - Medium - CCI-000172 - V-278075 - SV-278075r1129265_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-AU-000350

Vuln IDs

V-278075

Rule IDs

SV-278075r1129265_rule

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-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212

Checks: C-82605r1129263_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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 >> Other System Events - Failure

Fix: F-82510r1129264_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

Windows Server 2025 must be configured to audit System - Security State Change successes.

AU-12 - Medium - CCI-000172 - V-278076 - SV-278076r1129268_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-AU-000360

Vuln IDs

V-278076

Rule IDs

SV-278076r1129268_rule

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. Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212

Checks: C-82606r1129266_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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-82511r1129267_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

Windows Server 2025 must be configured to audit System - Security System Extension successes.

AU-12 - Medium - CCI-000172 - V-278077 - SV-278077r1129271_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-AU-000370

Vuln IDs

V-278077

Rule IDs

SV-278077r1129271_rule

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. Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212

Checks: C-82607r1129269_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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-82512r1129270_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

Windows Server 2025 must be configured to audit System - System Integrity successes.

AU-12 - Medium - CCI-000172 - V-278078 - SV-278078r1129274_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-AU-000380

Vuln IDs

V-278078

Rule IDs

SV-278078r1129274_rule

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. Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222

Checks: C-82608r1129272_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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-82513r1129273_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

Windows Server 2025 must be configured to audit System - System Integrity failures.

AU-12 - Medium - CCI-000172 - V-278079 - SV-278079r1129277_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-AU-000390

Vuln IDs

V-278079

Rule IDs

SV-278079r1129277_rule

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. Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222

Checks: C-82609r1129275_chk

Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or 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-82514r1129276_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

Windows Server 2025 must prevent the display of slide shows on the lock screen.

CM-7 - Medium - CCI-000381 - V-278080 - SV-278080r1129280_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN25-CC-000010

Vuln IDs

V-278080

Rule IDs

SV-278080r1129280_rule

Slide shows 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-82610r1129278_chk

Verify the registry value below: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Personalization\ Value Name: NoLockScreenSlideshow Value Type: REG_DWORD Value: 0x00000001 (1) If the registry value does not exist or is not configured as specified, this is a finding.

Fix: F-82515r1129279_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> Control Panel >> Personalization >> Prevent enabling lock screen slide show to "Enabled".

b

Windows Server 2025 must have WDigest Authentication disabled.

CM-7 - Medium - CCI-000381 - V-278081 - SV-278081r1129283_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN25-CC-000020

Vuln IDs

V-278081

Rule IDs

SV-278081r1129283_rule

When the WDigest Authentication protocol is enabled, plain-text passwords are stored in the Local Security Authority Subsystem Service (LSASS), exposing them to theft. WDigest is disabled by default in Windows Server 2025. This setting ensures this is enforced.

Checks: C-82611r1129281_chk

Verify the registry value below: Registry HiveHKEY_LOCAL_MACHINE Registry Path\SYSTEM\CurrentControlSet\Control\SecurityProviders\Wdigest\ Value NameUseLogonCredential TypeREG_DWORD Value0x00000000 (0) If the registry value does not exist or is not configured as specified, this is a finding.

Fix: F-82516r1129282_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide. Set "WDigest Authentication (disabling may require KB2871997)" to "Disabled". 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.

a

Windows Server 2025 Internet Protocol version 6 (IPv6) source routing must be configured to the highest protection level to prevent IP source routing.

CM-6 - Low - CCI-000366 - V-278082 - SV-278082r1129286_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN25-CC-000030

Vuln IDs

V-278082

Rule IDs

SV-278082r1129286_rule

Configuring the system to disable IPv6 source routing protects against spoofing.

Checks: C-82612r1129284_chk

Verify the registry value below: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\ Value Name: DisableIPSourceRouting Type: REG_DWORD Value: 0x00000002 (2) If the registry value does not exist or is not configured as specified, this is a finding.

Fix: F-82517r1129285_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> MSS: (DisableIPSourceRouting IPv6) IP source routing protection level (protects against packet spoofing) to "Enabled" with "Highest protection, source routing is completely disabled" selected. This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.adml" must be copied to the \Windows\PolicyDefinitions and \Windows\PolicyDefinitions\en-US directories respectively.

a

Windows Server 2025 source routing must be configured to the highest protection level to prevent Internet Protocol (IP) source routing.

CM-6 - Low - CCI-000366 - V-278083 - SV-278083r1129289_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN25-CC-000040

Vuln IDs

V-278083

Rule IDs

SV-278083r1129289_rule

Configuring the system to disable IP source routing protects against spoofing.

Checks: C-82613r1129287_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ Value Name: DisableIPSourceRouting Value Type: REG_DWORD Value: 0x00000002 (2)

Fix: F-82518r1129288_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> MSS: (DisableIPSourceRouting) IP source routing protection level (protects against packet spoofing) to "Enabled" with "Highest protection, source routing is completely disabled" selected. This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.adml" must be copied to the \Windows\PolicyDefinitions and \Windows\PolicyDefinitions\en-US directories respectively.

a

Windows Server 2025 must be configured to prevent Internet Control Message Protocol (ICMP) redirects from overriding Open Shortest Path First (OSPF)-generated routes.

CM-6 - Low - CCI-000366 - V-278084 - SV-278084r1129292_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN25-CC-000050

Vuln IDs

V-278084

Rule IDs

SV-278084r1129292_rule

Allowing ICMP redirect of routes can lead to traffic not being routed properly. When disabled, this forces ICMP to be routed via the shortest path first.

Checks: C-82614r1129290_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ Value Name: EnableICMPRedirect Value Type: REG_DWORD Value: 0x00000000 (0)

Fix: F-82519r1129291_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> MSS: (EnableICMPRedirect) Allow ICMP redirects to override OSPF generated routes to "Disabled". This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.adml" must be copied to the \Windows\PolicyDefinitions and \Windows\PolicyDefinitions\en-US directories respectively.

a

Windows Server 2025 must be configured to ignore NetBIOS name release requests except from WINS servers.

SC-5 - Low - CCI-002385 - V-278085 - SV-278085r1129295_rule

RMF Control

SC-5

Severity

L

CCI

CCI-002385

Version

WN25-CC-000060

Vuln IDs

V-278085

Rule IDs

SV-278085r1129295_rule

Configuring the system to ignore name release requests, except from WINS servers, prevents a denial-of-service (DoS) attack. The DoS consists of sending a NetBIOS name release request to the server for each entry in the server's cache, causing a response delay in the normal operation of the server's WINS resolution capability.

Checks: C-82615r1129293_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry HiveHKEY_LOCAL_MACHINE Registry Path\SYSTEM\CurrentControlSet\Services\Netbt\Parameters\ Value NameNoNameReleaseOnDemand Value TypeREG_DWORD Value0x00000001 (1)

Fix: F-82520r1129294_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> MSS: (NoNameReleaseOnDemand) Allow the computer to ignore NetBIOS name release requests except from WINS servers to "Enabled". This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.adml" must be copied to the \Windows\PolicyDefinitions and \Windows\PolicyDefinitions\en-US directories respectively.

b

Windows Server 2025 insecure logons to an SMB server must be disabled.

CM-6 - Medium - CCI-000366 - V-278086 - SV-278086r1129298_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-CC-000070

Vuln IDs

V-278086

Rule IDs

SV-278086r1129298_rule

Insecure guest logons allow unauthenticated access to shared folders. Shared resources on a system must require authentication to establish proper access.

Checks: C-82616r1129296_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\LanmanWorkstation\ Value Name: AllowInsecureGuestAuth Type: REG_DWORD Value: 0x00000000 (0)

Fix: F-82521r1129297_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> Network >> Lanman Workstation >> Enable insecure guest logons to "Disabled".

b

Windows Server 2025 hardened Universal Naming Convention (UNC) paths must be defined to require mutual authentication and integrity for at least the \\*\SYSVOL and \\*\NETLOGON shares.

CM-6 - Medium - CCI-000366 - V-278087 - SV-278087r1130302_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-CC-000080

Vuln IDs

V-278087

Rule IDs

SV-278087r1130302_rule

Additional security requirements are applied to UNC paths specified in hardened UNC paths before allowing access to them. This aids in preventing tampering with or spoofing of connections to these paths.

Checks: C-82617r1130160_chk

This requirement is applicable to domain-joined systems. For standalone or nondomain joined systems, this is not applicable. 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\NetworkProvider\HardenedPaths\ Value Name: \\*\NETLOGON Value Type: REG_SZ Value: RequireMutualAuthentication=1, RequireIntegrity=1 Value Name: \\*\SYSVOL Value Type: REG_SZ Value: RequireMutualAuthentication=1, RequireIntegrity=1 Additional entries would not be a finding.

Fix: F-82522r1130301_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> Network >> Network Provider >> Hardened UNC Paths" to "Enabled" with at least the following configured in "Hardened UNC Paths" (click "Show" to display): Value Name: \\*\SYSVOL Value: RequireMutualAuthentication=1, RequireIntegrity=1 Value Name: \\*\NETLOGON Value: RequireMutualAuthentication=1, RequireIntegrity=1

b

Windows Server 2025 command line data must be included in process creation events.

AU-3 - Medium - CCI-000135 - V-278088 - SV-278088r1129304_rule

RMF Control

AU-3

Severity

M

CCI

CCI-000135

Version

WN25-CC-000090

Vuln IDs

V-278088

Rule IDs

SV-278088r1129304_rule

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.

Checks: C-82618r1129302_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Audit\ Value Name: ProcessCreationIncludeCmdLine_Enabled Value Type: REG_DWORD Value: 0x00000001 (1)

Fix: F-82523r1129303_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Audit Process Creation >> Include command line in process creation events to "Enabled".

b

Windows Server 2025 must be configured to enable Remote host allows delegation of nonexportable credentials.

CM-6 - Medium - CCI-000366 - V-278089 - SV-278089r1129307_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-CC-000100

Vuln IDs

V-278089

Rule IDs

SV-278089r1129307_rule

An exportable version of credentials is provided to remote hosts when using credential delegation, which exposes them to theft on the remote host. Restricted Admin mode or Remote Credential Guard allow delegation of nonexportable credentials providing additional protection of the credentials. Enabling this configures the host to support Restricted Admin mode or Remote Credential Guard.

Checks: C-82619r1129305_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\CredentialsDelegation\ Value Name: AllowProtectedCreds Type: REG_DWORD Value: 0x00000001 (1)

Fix: F-82524r1129306_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Credentials Delegation >> Remote host allows delegation of nonexportable credentials to "Enabled".

b

Windows Server 2025 virtualization-based security must be enabled with the platform security level configured to Secure Boot or Secure Boot with DMA Protection.

CM-6 - Medium - CCI-000366 - V-278090 - SV-278090r1130164_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-CC-000110

Vuln IDs

V-278090

Rule IDs

SV-278090r1130164_rule

Virtualization Based Security (VBS) provides the platform for the additional security features Credential Guard and virtualization-based protection of code integrity. Secure Boot is the minimum security level, with DMA protection providing additional memory protection. DMA Protection requires a CPU that supports input/output memory management unit (IOMMU).

Checks: C-82620r1130162_chk

For standalone or nondomain joined systems, this is not applicable. Open PowerShell with elevated privileges (run as administrator). Enter the following: "Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard" If "RequiredSecurityProperties" does not include a value of "2" indicating "Secure Boot" (e.g., "{1, 2}"), this is a finding. If "Secure Boot and DMA Protection" is configured, "3" will also be displayed in the results (e.g., "{1, 2, 3}"). If "VirtualizationBasedSecurityStatus" is not a value of "2" indicating "Running", this is a finding. Alternately: Run "System Information". Under "System Summary", verify the following: If "Device Guard Virtualization based security" does not display "Running", this is a finding. If "Device Guard Required Security Properties" does not display "Base Virtualization Support, Secure Boot", this is a finding. If "Secure Boot and DMA Protection" is configured, "DMA Protection" will also be displayed (e.g., "Base Virtualization Support, Secure Boot, DMA Protection"). The policy settings referenced in the Fix section will configure the following registry values; however, due to hardware requirements, the registry values alone do not ensure proper function. Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeviceGuard\ Value Name: EnableVirtualizationBasedSecurity Value Type: REG_DWORD Value: 0x00000001 (1) Value Name: RequirePlatformSecurityFeatures Value Type: REG_DWORD Value: 0x00000001 (1) (Secure Boot only) or 0x00000003 (3) (Secure Boot and DMA Protection) A Microsoft TechNet article on Credential Guard, including system requirement details, can be found at the following link: https://technet.microsoft.com/itpro/windows/keep-secure/credential-guard

Fix: F-82525r1130163_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Device Guard >> Turn On Virtualization Based Security to "Enabled" with "Secure Boot" or "Secure Boot and DMA Protection" selected. A Microsoft TechNet article on Credential Guard, including system requirement details, can be found at the following link: https://technet.microsoft.com/itpro/windows/keep-secure/credential-guard

b

Windows Server 2025 Early Launch Antimalware, Boot-Start Driver Initialization Policy must prevent boot drivers identified as bad.

CM-6 - Medium - CCI-000366 - V-278091 - SV-278091r1129313_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-CC-000130

Vuln IDs

V-278091

Rule IDs

SV-278091r1129313_rule

Compromised boot drivers can introduce malware prior to 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-82621r1129311_chk

The default behavior is for Early Launch Antimalware - Boot-Start Driver Initialization policy to enforce "Good, unknown and bad but critical" (preventing "bad"). If the registry value name below does not exist, this is not a finding. If it exists and is configured with a value of "0x00000007 (7)", this is a finding. Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Policies\EarlyLaunch\ Value Name: DriverLoadPolicy Value Type: REG_DWORD Value: 0x00000001 (1), 0x00000003 (3), or 0x00000008 (8) (or if the Value Name does not exist) Possible values for this setting are: 8 - Good only 1 - Good and unknown 3 - Good, unknown and bad but critical 7 - All (which includes "bad" and would be a finding)

Fix: F-82526r1129312_fix

The default behavior is for Early Launch Antimalware - Boot-Start Driver Initialization policy to enforce "Good, unknown and bad but critical" (preventing "bad"). If this needs to be corrected or a more secure setting is desired, configure the policy value for Computer Configuration >> Administrative Templates >> System >> Early Launch Antimalware >> Boot-Start Driver Initialization Policy to "Not Configured" or "Enabled" with any option other than "All" selected.

b

Windows Server 2025 group policy objects must be reprocessed even if they have not changed.

CM-6 - Medium - CCI-000366 - V-278092 - SV-278092r1129316_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-CC-000140

Vuln IDs

V-278092

Rule IDs

SV-278092r1129316_rule

Registry entries for group policy settings can potentially be changed from the required configuration. This could occur as part of troubleshooting or by a malicious process on a compromised system. Enabling this setting and then selecting the "Process even if the Group Policy objects have not changed" option ensures 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-82622r1129314_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: 0x00000000 (0)

Fix: F-82527r1129315_fix

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

b

Windows Server 2025 downloading print driver packages over HTTP must be turned off.

CM-7 - Medium - CCI-000381 - V-278093 - SV-278093r1129319_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN25-CC-000150

Vuln IDs

V-278093

Rule IDs

SV-278093r1129319_rule

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 will prevent uncontrolled updates to the system. This setting prevents the computer from downloading print driver packages over HTTP.

Checks: C-82623r1129317_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: 0x00000001 (1)

Fix: F-82528r1129318_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".

b

Windows Server 2025 printing over HTTP must be turned off.

CM-7 - Medium - CCI-000381 - V-278094 - SV-278094r1129322_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN25-CC-000160

Vuln IDs

V-278094

Rule IDs

SV-278094r1129322_rule

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 will prevent 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-82624r1129320_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: 0x00000001 (1)

Fix: F-82529r1129321_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

Windows Server 2025 network selection user interface (UI) must not be displayed on the logon screen.

CM-7 - Medium - CCI-000381 - V-278095 - SV-278095r1129325_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN25-CC-000170

Vuln IDs

V-278095

Rule IDs

SV-278095r1129325_rule

Enabling interaction with the network selection UI allows users to change connections to available networks without signing in to Windows.

Checks: C-82625r1129323_chk

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: 0x00000001 (1)

Fix: F-82530r1129324_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Logon >> Do not display network selection UI to "Enabled".

b

Windows Server 2025 users must be prompted to authenticate when the system wakes from sleep (on battery).

CM-6 - Medium - CCI-000366 - V-278096 - SV-278096r1129328_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-CC-000180

Vuln IDs

V-278096

Rule IDs

SV-278096r1129328_rule

A system that does not require authentication when resuming from sleep may provide access to unauthorized users. Authentication must always be required when accessing a system. This setting ensures users are prompted for a password when the system wakes from sleep (on battery).

Checks: C-82626r1129326_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: 0x00000001 (1)

Fix: F-82531r1129327_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

Windows Server 2025 users must be prompted to authenticate when the system wakes from sleep (plugged in).

CM-6 - Medium - CCI-000366 - V-278097 - SV-278097r1129331_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-CC-000190

Vuln IDs

V-278097

Rule IDs

SV-278097r1129331_rule

A system that does not require authentication when resuming from sleep may provide access to unauthorized users. Authentication must always be required when accessing a system. This setting ensures users are prompted for a password when the system wakes from sleep (plugged in).

Checks: C-82627r1129329_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: 0x00000001 (1)

Fix: F-82532r1129330_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".

a

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

CM-7 - Low - CCI-000381 - V-278098 - SV-278098r1129334_rule

RMF Control

CM-7

Severity

L

CCI

Version

WN25-CC-000200

Vuln IDs

V-278098

Rule IDs

SV-278098r1129334_rule

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 will prevent 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-82628r1129332_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: 0x00000001 (1)

Fix: F-82533r1129333_fix

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

c

Windows Server 2025 AutoPlay must be turned off for nonvolume devices.

CM-7 - High - CCI-001764 - V-278099 - SV-278099r1129337_rule

RMF Control

CM-7

Severity

H

CCI

CCI-001764

Version

WN25-CC-000210

Vuln IDs

V-278099

Rule IDs

SV-278099r1129337_rule

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 nonvolume devices, such as Media Transfer Protocol (MTP) devices.

Checks: C-82629r1129335_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: 0x00000001 (1)

Fix: F-82534r1129336_fix

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

c

Windows Server 2025 default AutoRun behavior must be configured to prevent AutoRun commands.

CM-7 - High - CCI-001764 - V-278100 - SV-278100r1129340_rule

RMF Control

CM-7

Severity

H

CCI

CCI-001764

Version

WN25-CC-000220

Vuln IDs

V-278100

Rule IDs

SV-278100r1129340_rule

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

Checks: C-82630r1129338_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: 0x00000001 (1)

Fix: F-82535r1129339_fix

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

c

Windows Server 2025 AutoPlay must be disabled for all drives.

CM-7 - High - CCI-001764 - V-278101 - SV-278101r1129343_rule

RMF Control

CM-7

Severity

H

CCI

CCI-001764

Version

WN25-CC-000230

Vuln IDs

V-278101

Rule IDs

SV-278101r1129343_rule

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-82631r1129341_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-82536r1129342_fix

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

b

Windows Server 2025 administrator accounts must not be enumerated during elevation.

SC-3 - Medium - CCI-001084 - V-278102 - SV-278102r1129346_rule

RMF Control

SC-3

Severity

M

CCI

Version

WN25-CC-000240

Vuln IDs

V-278102

Rule IDs

SV-278102r1129346_rule

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 type in a username and password to elevate a running application.

Checks: C-82632r1129344_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-82537r1129345_fix

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

b

Windows Server 2025 Telemetry must be configured to send "required diagnostic data" or "optional diagnostic data".

CM-6 - Medium - CCI-000366 - V-278103 - SV-278103r1129349_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-CC-000250

Vuln IDs

V-278103

Rule IDs

SV-278103r1129349_rule

Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Limiting this capability will prevent potentially sensitive information from being sent outside the enterprise. The "send required diagnostic data" option for Allow Diagnostic Data configures the lowest amount of data, effectively none outside of the Malicious Software Removal Tool (MSRT), Defender, and Diagnostic Data client settings. "Optional Diagnostic Data" sends basic diagnostic and usage data and may be required to support some Microsoft services.

Checks: C-82633r1129347_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\DataCollection\ Value Name: AllowTelemetry Type: REG_DWORD Value0x00000001 (1), 0x00000003 (3)

Fix: F-82538r1129348_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Data Collection and Preview Build >> Allow Diagnostic Data to "Enabled" with "Send required diagnostic data" selected or "Send optional diagnostic data".

a

Windows Server 2025 Windows Update must not obtain updates from other PCs on the internet.

CM-6 - Low - CCI-000366 - V-278104 - SV-278104r1129352_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN25-CC-000260

Vuln IDs

V-278104

Rule IDs

SV-278104r1129352_rule

Windows Update can obtain updates from additional sources instead of Microsoft. In addition to Microsoft, updates can be obtained from and sent to PCs on the local network as well as on the internet. This is part of the Windows Update trusted process; however, to minimize outside exposure, obtaining updates from or sending to systems on the internet must be prevented.

Checks: C-82634r1129350_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\DeliveryOptimization\ Value Name: DODownloadMode Value Type: REG_DWORD Value: 0x00000000 (0) - No peering (HTTP Only) 0x00000001 (1) - Peers on same NAT only (LAN) 0x00000002 (2) - Local Network / Private group peering (Group) 0x00000063 (99) - Simple download mode, no peering (Simple) 0x00000064 (100) - Bypass mode, Delivery Optimization not used (Bypass) A value of 0x00000003 (3), internet, is a finding.

Fix: F-82539r1129351_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Delivery Optimization >> Download Mode to "Enabled" with any option except "Internet" selected. Acceptable selections include: Bypass (100) Group (2) HTTP only (0) LAN (1) Simple (99)

b

Windows Server 2025 Application event log size must be configured to 32768 KB or greater.

AU-4 - Medium - CCI-001849 - V-278105 - SV-278105r1130166_rule

RMF Control

AU-4

Severity

M

CCI

CCI-001849

Version

WN25-CC-000270

Vuln IDs

V-278105

Rule IDs

SV-278105r1130166_rule

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-82635r1130165_chk

If the system is configured to write events directly to an audit server, this is not applicable. 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-82540r1129354_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

Windows Server 2025 Security event log size must be configured to 196608 KB or greater.

AU-4 - Medium - CCI-001849 - V-278106 - SV-278106r1130168_rule

RMF Control

AU-4

Severity

M

CCI

CCI-001849

Version

WN25-CC-000280

Vuln IDs

V-278106

Rule IDs

SV-278106r1130168_rule

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-82636r1130167_chk

If the system is configured to write events directly to an audit server, this is not applicable. 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-82541r1129357_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

Windows Server 2025 System event log size must be configured to 32768 KB or greater.

AU-4 - Medium - CCI-001849 - V-278107 - SV-278107r1130170_rule

RMF Control

AU-4

Severity

M

CCI

CCI-001849

Version

WN25-CC-000290

Vuln IDs

V-278107

Rule IDs

SV-278107r1130170_rule

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-82637r1130169_chk

If the system is configured to write events directly to an audit server, this is not applicable. 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-82542r1129360_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 Server 2025 Microsoft Defender antivirus SmartScreen must be enabled.

CM-7 - Medium - CCI-000381 - V-278108 - SV-278108r1130172_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN25-CC-000300

Vuln IDs

V-278108

Rule IDs

SV-278108r1130172_rule

Microsoft Defender antivirus SmartScreen helps protect systems from programs downloaded from the internet that may be malicious. Enabling SmartScreen can block potentially malicious programs or warn users.

Checks: C-82638r1130171_chk

This is applicable to unclassified systems; for other systems, this is not applicable. 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 Value Type: REG_DWORD Value: 0x00000001 (1)

Fix: F-82543r1129363_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> Configure Windows Defender SmartScreen to "Enabled" with either option "Warn" or "Warn and prevent bypass" selected. Windows Server 2025 includes duplicate policies for this setting. It can also be configured under Computer Configuration >> Administrative Templates >> Windows Components >> Windows Defender SmartScreen >> Explorer.

b

Windows Server 2025 Explorer Data Execution Prevention must be enabled.

SI-16 - Medium - CCI-002824 - V-278109 - SV-278109r1129367_rule

RMF Control

SI-16

Severity

M

CCI

CCI-002824

Version

WN25-CC-000310

Vuln IDs

V-278109

Rule IDs

SV-278109r1129367_rule

Data Execution Prevention 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-82639r1129365_chk

The default behavior is for Data Execution Prevention to be turned on for File Explorer. If the registry value name below does not exist, this is not a finding. If it exists and is configured with a value of "0", this is not a finding. If it exists and is configured with a value of "1", this is a finding. Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Explorer\ Value Name: NoDataExecutionPrevention Value Type: REG_DWORD Value: 0x00000000 (0) (or if the Value Name does not exist)

Fix: F-82544r1129366_fix

The default behavior is for data execution prevention to be turned on for File Explorer. If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> Turn off Data Execution Prevention for Explorer to "Not Configured" or "Disabled".

a

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

CM-6 - Low - CCI-000366 - V-278110 - SV-278110r1129370_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN25-CC-000320

Vuln IDs

V-278110

Rule IDs

SV-278110r1129370_rule

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

Checks: C-82640r1129368_chk

The default behavior is for File Explorer heap termination on corruption to be enabled. If the registry Value Name below does not exist, this is not a finding. If it exists and is configured with a value of "0", this is not a finding. If it exists and is configured with a value of "1", this is a finding. Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Explorer\ Value Name: NoHeapTerminationOnCorruption Value Type: REG_DWORD Value: 0x00000000 (0) (or if the Value Name does not exist)

Fix: F-82545r1129369_fix

The default behavior is for File Explorer heap termination on corruption to be disabled. If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> Turn off heap termination on corruption to "Not Configured" or "Disabled".

b

Windows Server 2025 File Explorer shell protocol must run in protected mode.

CM-6 - Medium - CCI-000366 - V-278111 - SV-278111r1129373_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-CC-000330

Vuln IDs

V-278111

Rule IDs

SV-278111r1129373_rule

The shell protocol will limit the set of folders that 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-82641r1129371_chk

The default behavior is for shell protected mode to be turned on for File Explorer. If the registry value name below does not exist, this is not a finding. If it exists and is configured with a value of "0", this is not a finding. If it exists and is configured with a value of "1", this is a finding. Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer\ Value Name: PreXPSP2ShellProtocolBehavior Value Type: REG_DWORD Value: 0x00000000 (0) (or if the Value Name does not exist)

Fix: F-82546r1129372_fix

The default behavior is for shell protected mode to be turned on for File Explorer. If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> Turn off shell protocol protected mode to "Not Configured" or "Disabled".

b

Windows Server 2025 must not save passwords in the Remote Desktop Client.

Medium - CCI-004895 - V-278112 - SV-278112r1129376_rule

RMF Control

Severity

M

CCI

Version

WN25-CC-000340

Vuln IDs

V-278112

Rule IDs

SV-278112r1129376_rule

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. Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157

Checks: C-82642r1129374_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: 0x00000001 (1)

Fix: F-82547r1129375_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

Windows Server 2025 Remote Desktop Services must prevent drive redirection.

SC-4 - Medium - CCI-001090 - V-278113 - SV-278113r1129379_rule

RMF Control

SC-4

Severity

M

CCI

Version

WN25-CC-000350

Vuln IDs

V-278113

Rule IDs

SV-278113r1129379_rule

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

Checks: C-82643r1129377_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: 0x00000001 (1)

Fix: F-82548r1129378_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

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

Medium - CCI-004895 - V-278114 - SV-278114r1129382_rule

RMF Control

Severity

M

CCI

Version

WN25-CC-000360

Vuln IDs

V-278114

Rule IDs

SV-278114r1129382_rule

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. Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157

Checks: C-82644r1129380_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: 0x00000001 (1)

Fix: F-82549r1129381_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

Windows Server 2025 Remote Desktop Services must require secure Remote Procedure Call (RPC) communications.

AC-17 - Medium - CCI-000068 - V-278115 - SV-278115r1129385_rule

RMF Control

AC-17

Severity

M

CCI

CCI-000068

Version

WN25-CC-000370

Vuln IDs

V-278115

Rule IDs

SV-278115r1129385_rule

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. Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000250-GPOS-00093

Checks: C-82645r1129383_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: 0x00000001 (1)

Fix: F-82550r1129384_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

Windows Server 2025 Remote Desktop Services must be configured with the client connection encryption set to High Level.

AC-17 - Medium - CCI-000068 - V-278116 - SV-278116r1129388_rule

RMF Control

AC-17

Severity

M

CCI

CCI-000068

Version

WN25-CC-000380

Vuln IDs

V-278116

Rule IDs

SV-278116r1129388_rule

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. Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000250-GPOS-00093

Checks: C-82646r1129386_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: 0x00000003 (3)

Fix: F-82551r1129387_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" with "High Level" selected.

b

Windows Server 2025 must prevent attachments from being downloaded from RSS feeds.

CM-6 - Medium - CCI-000366 - V-278117 - SV-278117r1129391_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-CC-000390

Vuln IDs

V-278117

Rule IDs

SV-278117r1129391_rule

Attachments from RSS feeds may not be secure. This setting will prevent attachments from being downloaded from RSS feeds.

Checks: C-82647r1129389_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: 0x00000001 (1)

Fix: F-82552r1129390_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> RSS Feeds >> Prevent downloading of enclosures to "Enabled".

b

Windows Server 2025 must disable Basic authentication for RSS feeds over HTTP.

CM-7 - Medium - CCI-000381 - V-278118 - SV-278118r1129394_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN25-CC-000400

Vuln IDs

V-278118

Rule IDs

SV-278118r1129394_rule

Basic authentication uses plain-text passwords that could be used to compromise a system. Disabling Basic authentication will reduce this potential.

Checks: C-82648r1129392_chk

The default behavior is for the Windows RSS platform to not use Basic authentication over HTTP connections. If the registry value name below does not exist, this is not a finding. If it exists and is configured with a value of "0", this is not a finding. If it exists and is configured with a value of "1", this is a finding. Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Policies\Microsoft\Internet Explorer\Feeds\ Value Name: AllowBasicAuthInClear Value Type: REG_DWORD Value: 0x00000000 (0) (or if the Value Name does not exist)

Fix: F-82553r1129393_fix

The default behavior is for the Windows RSS platform to not use Basic authentication over HTTP connections. If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> RSS Feeds >> Turn on Basic feed authentication over HTTP to "Not Configured" or "Disabled".

b

Windows Server 2025 must prevent Indexing of encrypted files.

CM-7 - Medium - CCI-000381 - V-278119 - SV-278119r1129397_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN25-CC-000410

Vuln IDs

V-278119

Rule IDs

SV-278119r1129397_rule

Indexing of encrypted files may expose sensitive data. This setting prevents encrypted files from being indexed.

Checks: C-82649r1129395_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\Windows Search\ Value Name: AllowIndexingEncryptedStoresOrItems Value Type: REG_DWORD Value: 0x00000000 (0)

Fix: F-82554r1129396_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Search >> Allow indexing of encrypted files to "Disabled".

b

Windows Server 2025 must prevent users from changing installation options.

Medium - CCI-003980 - V-278120 - SV-278120r1129400_rule

RMF Control

Severity

M

CCI

CCI-003980

Version

WN25-CC-000420

Vuln IDs

V-278120

Rule IDs

SV-278120r1129400_rule

Installation options for applications are typically controlled by administrators. This setting prevents users from changing installation options that may bypass security features.

Checks: C-82650r1129398_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: 0x00000000 (0)

Fix: F-82555r1129399_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Installer >> Allow user control over installs to "Disabled".

c

Windows Server 2025 must disable the Windows Installer Always install with elevated privileges option.

High - CCI-003980 - V-278121 - SV-278121r1129403_rule

RMF Control

Severity

H

CCI

CCI-003980

Version

WN25-CC-000430

Vuln IDs

V-278121

Rule IDs

SV-278121r1129403_rule

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-82651r1129401_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: 0x00000000 (0)

Fix: F-82556r1129402_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Installer >> Always install with elevated privileges to "Disabled".

b

Windows Server 2025 users must be notified if a web-based program attempts to install software.

CM-6 - Medium - CCI-000366 - V-278122 - SV-278122r1129406_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-CC-000440

Vuln IDs

V-278122

Rule IDs

SV-278122r1129406_rule

Web-based programs may attempt to install malicious software on a system. Ensuring users are notified if a web-based program attempts to install software allows them to refuse the installation.

Checks: C-82652r1129404_chk

The default behavior is for Internet Explorer to warn users and select whether to allow or refuse installation when a web-based program attempts to install software on the system. If the registry value name below does not exist, this is not a finding. If it exists and is configured with a value of "0", this is not a finding. If it exists and is configured with a value of "1", this is a finding. Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Installer\ Value Name: SafeForScripting Value Type: REG_DWORD Value: 0x00000000 (0) (or if the Value Name does not exist)

Fix: F-82557r1129405_fix

The default behavior is for Internet Explorer to warn users and select whether to allow or refuse installation when a web-based program attempts to install software on the system. If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Installer >> Prevent Internet Explorer security prompt for Windows Installer scripts to "Not Configured" or "Disabled".

b

Windows Server 2025 must disable automatically signing in the last interactive user after a system-initiated restart.

CM-6 - Medium - CCI-000366 - V-278123 - SV-278123r1129409_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-CC-000450

Vuln IDs

V-278123

Rule IDs

SV-278123r1129409_rule

Windows 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-82653r1129407_chk

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: 0x00000001 (1)

Fix: F-82558r1129408_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Logon Options >> Sign-in and lock last interactive user automatically after a restart to "Disabled".

b

Windows Server 2025 PowerShell script block logging must be enabled.

AU-3 - Medium - CCI-000135 - V-278124 - SV-278124r1129412_rule

RMF Control

AU-3

Severity

M

CCI

CCI-000135

Version

WN25-CC-000460

Vuln IDs

V-278124

Rule IDs

SV-278124r1129412_rule

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.

Checks: C-82654r1129410_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)

Fix: F-82559r1129411_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows PowerShell >> Turn on PowerShell Script Block Logging to "Enabled".

c

Windows Server 2025 Windows Remote Management (WinRM) client must not use Basic authentication.

MA-4 - High - CCI-000877 - V-278125 - SV-278125r1129415_rule

RMF Control

MA-4

Severity

H

CCI

CCI-000877

Version

WN25-CC-000470

Vuln IDs

V-278125

Rule IDs

SV-278125r1129415_rule

Basic authentication uses plain-text passwords that could be used to compromise a system. Disabling Basic authentication will reduce this potential.

Checks: C-82655r1129413_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: 0x00000000 (0)

Fix: F-82560r1129414_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Remote Management (WinRM) >> WinRM Client >> Allow Basic authentication to "Disabled".

b

Windows Server 2025 Windows Remote Management (WinRM) client must not allow unencrypted traffic.

MA-4 - Medium - CCI-002890 - V-278126 - SV-278126r1129418_rule

RMF Control

MA-4

Severity

M

CCI

CCI-002890

Version

WN25-CC-000480

Vuln IDs

V-278126

Rule IDs

SV-278126r1129418_rule

Unencrypted remote access to a system can allow sensitive information to be compromised. Windows remote management connections must be encrypted to prevent this. Satisfies: SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174

Checks: C-82656r1129416_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: 0x00000000 (0)

Fix: F-82561r1129417_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Remote Management (WinRM) >> WinRM Client >> Allow unencrypted traffic to "Disabled".

b

Windows Server 2025 Windows Remote Management (WinRM) client must not use Digest authentication.

MA-4 - Medium - CCI-000877 - V-278127 - SV-278127r1129421_rule

RMF Control

MA-4

Severity

M

CCI

CCI-000877

Version

WN25-CC-000490

Vuln IDs

V-278127

Rule IDs

SV-278127r1129421_rule

Digest authentication is not as strong as other options and may be subject to man-in-the-middle attacks. Disallowing Digest authentication will reduce this potential.

Checks: C-82657r1129419_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: 0x00000000 (0)

Fix: F-82562r1129420_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Remote Management (WinRM) >> WinRM Client >> Disallow Digest authentication to "Enabled".

c

Windows Server 2025 Windows Remote Management (WinRM) service must not use Basic authentication.

MA-4 - High - CCI-000877 - V-278128 - SV-278128r1129424_rule

RMF Control

MA-4

Severity

H

CCI

CCI-000877

Version

WN25-CC-000500

Vuln IDs

V-278128

Rule IDs

SV-278128r1129424_rule

Basic authentication uses plain-text passwords that could be used to compromise a system. Disabling Basic authentication will reduce this potential.

Checks: C-82658r1129422_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: 0x00000000 (0)

Fix: F-82563r1129423_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Remote Management (WinRM) >> WinRM Service >> Allow Basic authentication to "Disabled".

b

Windows Server 2025 Windows Remote Management (WinRM) service must not allow unencrypted traffic.

MA-4 - Medium - CCI-002890 - V-278129 - SV-278129r1129427_rule

RMF Control

MA-4

Severity

M

CCI

CCI-002890

Version

WN25-CC-000510

Vuln IDs

V-278129

Rule IDs

SV-278129r1129427_rule

Unencrypted remote access to a system can allow sensitive information to be compromised. Windows remote management connections must be encrypted to prevent this. Satisfies: SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174

Checks: C-82659r1129425_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: 0x00000000 (0)

Fix: F-82564r1129426_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Remote Management (WinRM) >> WinRM Service >> Allow unencrypted traffic to "Disabled".

b

Windows Server 2025 Windows Remote Management (WinRM) service must not store RunAs credentials.

Medium - CCI-004895 - V-278130 - SV-278130r1130299_rule

RMF Control

Severity

M

CCI

Version

WN25-CC-000520

Vuln IDs

V-278130

Rule IDs

SV-278130r1130299_rule

Storage of administrative credentials could allow unauthorized access. Disallowing the storage of RunAs credentials for WinRM will prevent them from being used with plug-ins. Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157

Checks: C-82660r1129428_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: 0x00000001 (1)

Fix: F-82565r1129429_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

Windows Server 2025 must have PowerShell Transcription enabled.

AC-3 - Medium - CCI-000213 - V-278131 - SV-278131r1129433_rule

RMF Control

AC-3

Severity

M

CCI

Version

WN25-CC-000530

Vuln IDs

V-278131

Rule IDs

SV-278131r1129433_rule

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 Transcription will record detailed information from the processing of PowerShell commands and scripts. This can provide additional detail when malware has run on a system.

Checks: C-82661r1129431_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\Transcription\ Value Name: EnableTranscripting Value Type: REG_DWORD Value: 1

Fix: F-82566r1129432_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows PowerShell >> "Turn on PowerShell Transcription" to "Enabled". Specify the Transcript output directory to point to a Central Log Server or another secure location to prevent user access.

c

Windows Server 2025 must only allow administrators responsible for the domain controller to have Administrator rights on the system.

AC-6 - High - CCI-002235 - V-278132 - SV-278132r1129436_rule

RMF Control

AC-6

Severity

H

CCI

Version

WN25-DC-000010

Vuln IDs

V-278132

Rule IDs

SV-278132r1129436_rule

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 using only accounts with the minimum level of authority necessary. Standard user accounts must not be members of the built-in Administrators group.

Checks: C-82662r1129434_chk

This applies to domain controllers. A separate version applies to other systems. Review the Administrators group. Only the appropriate administrator groups or accounts responsible for administration of the system may be members of the group. Standard user accounts must not be members of the local administrator group. If prohibited accounts are members of the local administrators group, this is a finding. If the built-in Administrator account or other required administrative accounts are found on the system, this is not a finding.

Fix: F-82567r1129435_fix

Configure the Administrators group to include only administrator groups or accounts that are responsible for the system. Remove any standard user accounts.

b

Windows Server 2025 Kerberos user logon restrictions must be enforced.

IA-2 - Medium - CCI-001941 - V-278133 - SV-278133r1129439_rule

RMF Control

IA-2

Severity

M

CCI

Version

WN25-DC-000020

Vuln IDs

V-278133

Rule IDs

SV-278133r1129439_rule

This policy setting determines whether the Kerberos Key Distribution Center (KDC) validates every request for a session ticket against the user rights policy of the target computer. The policy is enabled by default, which is the most secure setting for validating that access to target resources is not circumvented. Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058

Checks: C-82663r1129437_chk

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

Fix: F-82568r1129438_fix

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

b

Windows Server 2025 Kerberos service ticket maximum lifetime must be limited to 600 minutes or less.

IA-2 - Medium - CCI-001941 - V-278134 - SV-278134r1129442_rule

RMF Control

IA-2

Severity

M

CCI

Version

WN25-DC-000030

Vuln IDs

V-278134

Rule IDs

SV-278134r1129442_rule

This setting determines the maximum amount of time (in minutes) that a granted session ticket can be used to access a particular service. Session tickets are used only to authenticate new connections with servers. Ongoing operations are not interrupted if the session ticket used to authenticate the connection expires during the connection. Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058

Checks: C-82664r1129440_chk

This applies to domain controllers. It is NA for other systems. Verify the following is configured in the Default Domain Policy: Open "Group Policy Management". Navigate to "Group Policy Objects" in the Domain being reviewed (Forest >> Domains >> Domain). Right-click the "Default Domain Policy". Select "Edit". Navigate to Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy. If the value for "Maximum lifetime for service ticket" is "0" or greater than "600" minutes, this is a finding.

Fix: F-82569r1129441_fix

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

b

Windows Server 2025 Kerberos user ticket lifetime must be limited to 10 hours or less.

IA-2 - Medium - CCI-001941 - V-278135 - SV-278135r1129445_rule

RMF Control

IA-2

Severity

M

CCI

Version

WN25-DC-000040

Vuln IDs

V-278135

Rule IDs

SV-278135r1129445_rule

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

Checks: C-82665r1129443_chk

This applies to domain controllers. It is NA for other systems. Verify the following is configured in the Default Domain Policy: Open "Group Policy Management". Navigate to "Group Policy Objects" in the Domain being reviewed (Forest >> Domains >> Domain). Right-click the "Default Domain Policy". Select "Edit". Navigate to Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy. If the value for "Maximum lifetime for user ticket" is "0" or greater than "10" hours, this is a finding.

Fix: F-82570r1129444_fix

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

b

Windows Server 2025 Kerberos policy user ticket renewal maximum lifetime must be limited to seven days or less.

IA-2 - Medium - CCI-001941 - V-278136 - SV-278136r1129448_rule

RMF Control

IA-2

Severity

M

CCI

Version

WN25-DC-000050

Vuln IDs

V-278136

Rule IDs

SV-278136r1129448_rule

This setting determines the period of time (in days) during which a user's Ticket Granting Ticket (TGT) may be renewed. This security configuration limits the amount of time an attacker has to crack the TGT and gain access. Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058

Checks: C-82666r1129446_chk

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

Fix: F-82571r1129447_fix

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

b

Windows Server 2025 computer clock synchronization tolerance must be limited to five minutes or less.

IA-2 - Medium - CCI-001941 - V-278137 - SV-278137r1129451_rule

RMF Control

IA-2

Severity

M

CCI

Version

WN25-DC-000060

Vuln IDs

V-278137

Rule IDs

SV-278137r1129451_rule

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

Checks: C-82667r1129449_chk

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

Fix: F-82572r1129450_fix

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

c

Windows Server 2025 permissions on the Active Directory data files must only allow system administrators (SAs) access.

AC-6 - High - CCI-002235 - V-278138 - SV-278138r1130298_rule

RMF Control

AC-6

Severity

H

CCI

Version

WN25-DC-000070

Vuln IDs

V-278138

Rule IDs

SV-278138r1130298_rule

Improper access permissions for directory data-related files could allow unauthorized users to read, modify, or delete directory data or audit trails. Satisfies: SRG-OS-000324-GPOS-00125, SRG-OS-000206-GPOS-00084

Checks: C-82668r1129452_chk

This applies to domain controllers. It is NA for other systems. Run "Regedit". Navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters". Note the directory locations in the values for: Database log files path DSA Database file By default, they will be \Windows\NTDS. If the locations are different, the following will need to be run for each: Open "command prompt (Admin)". Navigate to the NTDS directory (\Windows\NTDS by default). Run "icacls *.*". If the permissions on each file are not as restrictive as the following, this is a finding: NT AUTHORITY\SYSTEM:(I)(F) BUILTIN\Administrators:(I)(F) (I) - permission inherited from parent container (F) - full access

Fix: F-82573r1129453_fix

Maintain the permissions on NTDS database and log files as follows: NT AUTHORITY\SYSTEM:(I)(F) BUILTIN\Administrators:(I)(F) (I) - permission inherited from parent container (F) - full access

c

Windows Server 2025 Active Directory SYSVOL directory must have the proper access control permissions.

AC-6 - High - CCI-002235 - V-278139 - SV-278139r1129457_rule

RMF Control

AC-6

Severity

H

CCI

Version

WN25-DC-000080

Vuln IDs

V-278139

Rule IDs

SV-278139r1129457_rule

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

Checks: C-82669r1129455_chk

This applies to domain controllers. It is NA for other systems. Open a command prompt. Run "net share". Make note of the directory location of the SYSVOL share. By default, this will be \Windows\SYSVOL\sysvol. For this requirement, permissions will be verified at the first SYSVOL directory level. If any standard user accounts or groups have greater than "Read & execute" permissions, this is a finding. The default permissions noted below meet this requirement: Open command prompt. Run "icacls c:\Windows\SYSVOL". The following results must be displayed: NT AUTHORITY\Authenticated Users:(RX) NT AUTHORITY\Authenticated Users:(OI)(CI)(IO)(GR,GE) BUILTIN\Server Operators:(RX) BUILTIN\Server Operators:(OI)(CI)(IO)(GR,GE) BUILTIN\Administrators:(M,WDAC,WO) BUILTIN\Administrators:(OI)(CI)(IO)(F) NT AUTHORITY\SYSTEM:(F) NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(F) CREATOR OWNER:(OI)(CI)(IO)(F) (RX) - Read & execute Run "icacls /help" to view definitions of other permission codes.

Fix: F-82574r1129456_fix

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

c

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

AC-6 - High - CCI-002235 - V-278140 - SV-278140r1129460_rule

RMF Control

AC-6

Severity

H

CCI

Version

WN25-DC-000090

Vuln IDs

V-278140

Rule IDs

SV-278140r1129460_rule

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

Checks: C-82670r1129458_chk

This applies to domain controllers. It is NA for other systems. Review the permissions on Group Policy objects. Open "Group Policy Management" (available from various menus or run "gpmc.msc"). Navigate to "Group Policy Objects" in the domain being reviewed (Forest >> Domains >> Domain). For each Group Policy object: Select the Group Policy object item in the left pane. Select the "Delegation" tab in the right pane. Select "Advanced". Select each Group or user name. View the permissions. If any standard user accounts or groups have "Allow" permissions greater than "Read" and "Apply group policy", this is a finding. Other access permissions that allow the objects to be updated are considered findings unless specifically documented by the information system security officer (ISSO). The default permissions noted below satisfy this requirement. The permissions shown are at the summary level. More detailed permissions can be viewed by selecting the next "Advanced" button, the desired Permission entry, and the "Edit" button. Authenticated Users - Read, Apply group policy, Special permissions The special permissions for Authenticated Users are for Read-type Properties. If detailed permissions include any Create, Delete, Modify, or Write Permissions, or Properties, this is a finding. The special permissions for the following default groups are not the focus of this requirement and may include a wide range of permissions and properties: CREATOR OWNER - Special permissions SYSTEM - Read, Write, Create all child objects, Delete all child objects, Special permissions Domain Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions Enterprise Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions The Domain Admins and Enterprise Admins will not have the "Delete all child objects" permission on the two default Group Policy objects: Default Domain Policy and Default Domain Controllers Policy. They will have this permission on organization created Group Policy objects.

Fix: F-82575r1129459_fix

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

c

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

AC-6 - High - CCI-002235 - V-278141 - SV-278141r1129463_rule

RMF Control

AC-6

Severity

H

CCI

Version

WN25-DC-000100

Vuln IDs

V-278141

Rule IDs

SV-278141r1129463_rule

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

Checks: C-82671r1129461_chk

This applies to domain controllers. It is NA for other systems. Review the permissions on the Domain Controllers OU. Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). Select "Advanced Features" in the "View" menu if not previously selected. Select the "Domain Controllers" OU (folder in folder icon). Right-click and select "Properties". Select the "Security" tab. If the permissions on the Domain Controllers OU do not restrict changes to System, Domain Admins, Enterprise Admins and Administrators, this is a finding. The default permissions listed below satisfy this requirement. Domains supporting Microsoft Exchange will have additional Exchange related permissions on the Domain Controllers OU. These may include some change-related permissions and is not a finding. The permissions shown are at the summary level. To view more detailed permissions, select "Advanced", then select the desired Permission entry, then click "View" or "Edit". Except where noted otherwise, the special permissions may include a wide range of permissions and properties and are acceptable for this requirement. CREATOR OWNER - Special permissions SELF - Special permissions Authenticated Users - Read, Special permissions The special permissions for Authenticated Users are Read types. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. SYSTEM - Full Control Domain Admins - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions Enterprise Admins - Full Control Key Admins - Special permissions Enterprise Key Admins - Special permissions Administrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions Pre-Windows 2000 Compatible Access - Special permissions The Special permissions for Pre-Windows 2000 Compatible Access are Read types. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions

Fix: F-82576r1129462_fix

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

c

Windows Server 2025 organization created Active Directory Organizational Unit (OU) objects must have proper access control permissions.

AC-6 - High - CCI-002235 - V-278142 - SV-278142r1129466_rule

RMF Control

AC-6

Severity

H

CCI

Version

WN25-DC-000110

Vuln IDs

V-278142

Rule IDs

SV-278142r1129466_rule

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

Checks: C-82672r1129464_chk

This applies to domain controllers. It is NA for other systems. Review the permissions on domain-defined OUs. Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). Ensure "Advanced Features" is selected in the "View" menu. For each OU that is defined (folder in folder icon) excluding the Domain Controllers OU: Right-click the OU and select "Properties". Select the "Security" tab. If the Allow type permissions on the OU are not at least as restrictive as those below, this is a finding. The permissions shown are at the summary level. To view more detailed permissions, select "Advanced", then select the desired Permission entry, then click "View" or "Edit". Except where noted otherwise, the special permissions may include a wide range of permissions and properties and are acceptable for this requirement. CREATOR OWNER - Special permissions Self - Special permissions Authenticated Users - Read, Special permissions The Special permissions for Authenticated Users are Read type. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. SYSTEM - Full Control Domain Admins - Full Control Enterprise Admins - Full Control Key Admins - Special permissions Enterprise Key Admins - Special permissions Administrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions Pre-Windows 2000 Compatible Access - Special permissions The Special permissions for Pre-Windows 2000 Compatible Access are for Read types. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions If an information system security officer (ISSO)-approved distributed administration model (help desk or other user support staff) is implemented, permissions above Read may be allowed for groups documented by the ISSO. If any OU with improper permissions includes identification or authentication data (e.g., accounts, passwords, or password hash data) used by systems to determine access control, the severity is CAT I (e.g., OUs that include user accounts, including service/application accounts). If an OU with improper permissions does not include identification and authentication data used by systems to determine access control, the severity is CAT II (e.g., Workstation, Printer OUs).

Fix: F-82577r1129465_fix

Maintain the Allow type permissions on domain-defined OUs to be at least as restrictive as the defaults below. Document any additional permissions above Read with the ISSO if an approved distributed administration model (help desk or other user support staff) is implemented. CREATOR OWNER - Special permissions Self - Special permissions Authenticated Users - Read, Special permissions The special permissions for Authenticated Users are Read type. SYSTEM - Full Control Domain Admins - Full Control Enterprise Admins - Full Control Key Admins - Special permissions Enterprise Key Admins - Special permissions Administrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions Pre-Windows 2000 Compatible Access - Special permissions The special permissions for Pre-Windows 2000 Compatible Access are for Read types. ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions

b

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

SC-4 - Medium - CCI-001090 - V-278143 - SV-278143r1129469_rule

RMF Control

SC-4

Severity

M

CCI

Version

WN25-DC-000120

Vuln IDs

V-278143

Rule IDs

SV-278143r1129469_rule

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

Checks: C-82673r1129467_chk

This applies to domain controllers. It is NA for other systems. Run "Regedit". Navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters". Note the directory locations in the values for "DSA Database file". Open a command prompt. Enter "net share". Note the logical drive(s) or file system partition for any organization-created data shares. Ignore system shares (e.g., NETLOGON, SYSVOL, and administrative shares ending in $). User shares that are hidden (ending with $) must not be ignored. If user shares are located on the same logical partition as the directory server data files, this is a finding.

Fix: F-82578r1129468_fix

Move shares used to store files owned by users to a different logical partition than the directory server data files.

b

Windows Server 2025 domain controllers must run on a machine dedicated to that function.

CM-7 - Medium - CCI-000381 - V-278144 - SV-278144r1130174_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN25-DC-000130

Vuln IDs

V-278144

Rule IDs

SV-278144r1130174_rule

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

Checks: C-82674r1130173_chk

This applies to domain controllers, it is NA for other systems. Review the installed roles the domain controller is supporting. Start Server Manager. Select "AD DS" in the left pane then select the server name under "Servers" to the right. Select "Add (or Remove) Roles and Features" from "Tasks" in the "Roles and Features" section. (Cancel before any changes are made.) Determine if any additional server roles are installed. A basic domain controller setup will include the following: - Active Directory Domain Services. - DNS Server. - File and Storage Services. If any roles not requiring installation on a domain controller are installed, this is a finding. A Domain Name System (DNS) server integrated with the directory server (e.g., AD-integrated DNS) is an acceptable application. However, the DNS server must comply with the DNS STIG security requirements. Run "Programs and Features". Review installed applications. If any applications are installed that are not required for the domain controller, this is a finding.

Fix: F-82579r1129471_fix

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

b

Windows Server 2025 must use separate, NSA-approved (Type 1) cryptography to protect the directory data in transit for directory service implementations at a classified confidentiality level when replication data traverses a network cleared to a lower level than the data.

SC-13 - Medium - CCI-002450 - V-278145 - SV-278145r1129475_rule

RMF Control

SC-13

Severity

M

CCI

CCI-002450

Version

WN25-DC-000140

Vuln IDs

V-278145

Rule IDs

SV-278145r1129475_rule

Directory data that is not appropriately encrypted is subject to compromise. Commercial-grade encryption does not provide adequate protection when the classification level of directory data in transit is higher than the level of the network.

Checks: C-82675r1129473_chk

This applies to domain controllers. It is NA for other systems. Review the organization network diagram(s) or documentation to determine the level of classification for the network(s) over which replication data is transmitted. Determine the classification level of the Windows domain controller. If the classification level of the Windows domain controller is higher than the level of the networks, review the organization network diagram(s) and directory implementation documentation to determine if NSA-approved encryption is used to protect the replication network traffic. If the classification level of the Windows domain controller is higher than the level of the network traversed and NSA-approved encryption is not used, this is a finding.

Fix: F-82580r1129474_fix

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

c

Windows Server 2025 directory data (outside the root DSE) of a nonpublic directory must be configured to prevent anonymous access.

CM-6 - High - CCI-000366 - V-278146 - SV-278146r1129478_rule

RMF Control

CM-6

Severity

H

CCI

Version

WN25-DC-000150

Vuln IDs

V-278146

Rule IDs

SV-278146r1129478_rule

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

Checks: C-82676r1129476_chk

This applies to domain controllers. It is NA for other systems. Open command prompt (not elevated). Run "ldp.exe". From the "Connection menu", select "Bind". Clear the User, Password, and Domain fields. Select "Simple bind" for the Bind type, and then click "OK". Confirmation of anonymous access will be displayed at the end: res = ldap_simple_bind_s Authenticated as: 'NT AUTHORITY\ANONYMOUS LOGON' From the "Browse" menu, select "Search". In the Search dialog, enter the DN of the domain naming context (e.g., "dc=disaost,dc=mil") in the Base DN field. Clear the Attributes field and select "Run". Error messages must display related to Bind and user not authenticated. If attribute data is displayed, anonymous access is enabled to the domain naming context and this is a finding. The following network controls allow the finding severity to be downgraded to a CAT II since these measures lower the risk associated with anonymous access. Network hardware ports at the site are subject to 802.1x authentication or MAC address restrictions. Premise firewall or host restrictions prevent access to ports 389, 636, 3268, and 3269 from client hosts not explicitly identified by domain (.mil) or IP address.

Fix: F-82581r1129477_fix

Configure directory data (outside the root DSE) of a nonpublic directory to prevent anonymous access. For AD, there are multiple configuration items that could enable anonymous access. Changing the access permissions on the domain naming context object (from the secure defaults) could enable anonymous access. If the check procedures indicate this is the cause, the process that was used to change the permissions must be reversed. This could have been through the Windows Support Tools ADSI Edit console (adsiedit.msc). The dsHeuristics option is used. This is addressed in the check for AD.0230 in the AD Forest STIG.

a

Windows Server 2025 directory service must be configured to terminate LDAP-based network connections to the directory server after five minutes of inactivity.

SC-10 - Low - CCI-001133 - V-278147 - SV-278147r1129481_rule

RMF Control

SC-10

Severity

L

CCI

CCI-001133

Version

WN25-DC-000160

Vuln IDs

V-278147

Rule IDs

SV-278147r1129481_rule

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

Checks: C-82677r1129479_chk

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

Fix: F-82582r1129480_fix

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

b

Windows Server 2025 Active Directory Group Policy Objects (GPOs) must be configured with proper audit settings.

AU-12 - Medium - CCI-000172 - V-278148 - SV-278148r1130304_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-DC-000170

Vuln IDs

V-278148

Rule IDs

SV-278148r1130304_rule

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

Checks: C-82678r1129482_chk

This applies to domain controllers. It is NA for other systems. Review the auditing configuration for all GPOs. Open "Group Policy Management" (available from various menus or run "gpmc.msc"). Navigate to "Group Policy Objects" in the domain being reviewed (Forest >> Domains >> Domain). For each GPO: Select the GPO item in the left pane. Select the "Delegation" tab in the right pane. Select "Advanced". Select "Advanced", and then select the "Auditing" tab. If the audit settings for any GPO are not at least as inclusive as those below, this is a finding: Type - Fail Principal - Everyone Access - Full Control Applies to - This object and all descendant objects or Descendant groupPolicyContainer objects The three Success types listed below are defaults inherited from the Parent Object. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Type - Success Principal - Everyone Access - Special (Permissions: Write all properties, Modify permissions; Properties: all "Write" type selected) Inherited from - Parent Object Applies to - Descendant groupPolicyContainer objects Two instances with the following summary information will be listed: Type - Success Principal - Everyone Access - blank (Permissions: none selected; Properties: one instance - Write gPLink, one instance - Write gPOptions) Inherited from - Parent Object Applies to - Descendant Organization Unit Objects

Fix: F-82583r1130303_fix

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

b

Windows Server 2025 Active Directory (AD) Domain object must be configured with proper audit settings.

AU-12 - Medium - CCI-000172 - V-278149 - SV-278149r1129487_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-DC-000180

Vuln IDs

V-278149

Rule IDs

SV-278149r1129487_rule

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

Checks: C-82679r1129485_chk

This applies to domain controllers. It is NA for other systems. Review the auditing configuration for the Domain object. Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). Verify "Advanced Features" is selected in the "View" menu. Select the domain being reviewed in the left pane. Right-click the domain name, and then select "Properties". Select the "Security" tab. Select "Advanced", and then select the "Auditing" tab. If the audit settings on the Domain object are not at least as inclusive as those below, this is a finding: Type - Fail Principal - Everyone Access - Full Control Inherited from - None Applies to - This object only The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. Two instances with the following summary information will be listed: Type - Success Principal - Everyone Access - (blank) Inherited from - None Applies to - Special Type - Success Principal - Domain Users Access - All extended rights Inherited from - None Applies to - This object only Type - Success Principal - Administrators Access - All extended rights Inherited from - None Applies to - This object only Type - Success Principal - Everyone Access - Special Inherited from - None Applies to - This object only (Access - Special = Permissions: Write all properties, Modify permissions, Modify owner)

Fix: F-82584r1129486_fix

Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). Select "Advanced Features" in the "View" menu. Select the domain being reviewed in the left pane. Right-click the domain name and select "Properties". Select the "Security" tab. Select "Advanced", and then select the "Auditing" tab. Configure the audit settings for Domain object to include the following: Type - Fail Principal - Everyone Access - Full Control Inherited from - None Applies to - This object only The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. Two instances with the following summary information will be listed: Type - Success Principal - Everyone Access - (blank) Inherited from - None Applies to - Special Type - Success Principal - Domain Users Access - All extended rights Inherited from - None Applies to - This object only Type - Success Principal - Administrators Access - All extended rights Inherited from - None Applies to - This object only Type - Success Principal - Everyone Access - Special Inherited from - None Applies to - This object only (Access - Special = Permissions: Write all properties, Modify permissions, Modify owner.)

b

Windows Server 2025 Active Directory (AD) Infrastructure object must be configured with proper audit settings.

AU-12 - Medium - CCI-000172 - V-278150 - SV-278150r1129490_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-DC-000190

Vuln IDs

V-278150

Rule IDs

SV-278150r1129490_rule

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

Checks: C-82680r1129488_chk

This applies to domain controllers. It is NA for other systems. Review the auditing configuration for the Infrastructure object. Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). Verify "Advanced Features" is selected in the "View" menu. Select the domain being reviewed in the left pane. Right-click the "Infrastructure" object in the right pane and select "Properties". Select the "Security" tab. Select "Advanced", and then select the "Auditing" tab. If the audit settings on the Infrastructure object are not at least as inclusive as those below, this is a finding: Type - Fail Principal - Everyone Access - Full Control Inherited from - None The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. Type - Success Principal - Everyone Access - Special Inherited from - None (Access - Special = Permissions: Write all properties, All extended rights, Change infrastructure master) Two instances with the following summary information will be listed: Type - Success Principal - Everyone Access - (blank) Inherited from - (CN of domain)

Fix: F-82585r1129489_fix

Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). Select "Advanced Features" in the "View" menu. Select the domain being reviewed in the left pane. Right-click the "Infrastructure" object in the right pane and select "Properties". Select the "Security" tab. Select "Advanced", and then select the "Auditing" tab. Configure the audit settings for the Infrastructure object to include the following: Type - Fail Principal - Everyone Access - Full Control Inherited from - None The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. Type - Success Principal - Everyone Access - Special Inherited from - None (Access - Special = Permissions: Write all properties, All extended rights, Change infrastructure master) Two instances with the following summary information will be listed: Type - Success Principal - Everyone Access - (blank) Inherited from - (CN of domain)

b

Windows Server 2025 Active Directory (AD) Domain Controllers Organizational Unit (OU) object must be configured with proper audit settings.

AU-12 - Medium - CCI-000172 - V-278151 - SV-278151r1129493_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-DC-000200

Vuln IDs

V-278151

Rule IDs

SV-278151r1129493_rule

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

Checks: C-82681r1129491_chk

This applies to domain controllers. It is NA for other systems. Review the auditing configuration for the Domain Controller OU object. Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). Verify "Advanced Features" is selected in the "View" menu. Select the "Domain Controllers OU" under the domain being reviewed in the left pane. Right-click the "Domain Controllers OU" object and select "Properties". Select the "Security" tab. Select "Advanced", and then select the "Auditing" tab. If the audit settings on the Domain Controllers OU object are not at least as inclusive as those below, this is a finding: Type - Fail Principal - Everyone Access - Full Control Inherited from - None Applies to - This object and all descendant objects The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. Type - Success Principal - Everyone Access - Special Inherited from - None Applies to - This object only (Access - Special = Permissions: all create, delete and modify permissions) Type - Success Principal - Everyone Access - Write all properties Inherited from - None Applies to - This object and all descendant objects Two instances with the following summary information will be listed: Type - Success Principal - Everyone Access - (blank) Inherited from - (CN of domain) Applies to - Descendant Organizational Unit objects

Fix: F-82586r1129492_fix

Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). Select "Advanced Features" in the "View" menu. Select the "Domain Controllers OU" under the domain being reviewed in the left pane. Right-click the "Domain Controllers OU" object and select "Properties". Select the "Security" tab. Select "Advanced", and then select the "Auditing" tab. Configure the audit settings for Domain Controllers OU object to include the following: Type - Fail Principal - Everyone Access - Full Control Inherited from - None The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. Type - Success Principal - Everyone Access - Special Inherited from - None Applies to - This object only (Access - Special = Permissions: all create, delete and modify permissions) Type - Success Principal - Everyone Access - Write all properties Inherited from - None Applies to - This object and all descendant objects Two instances with the following summary information will be listed: Type - Success Principal - Everyone Access - (blank) Inherited from - (CN of domain) Applies to - Descendant Organizational Unit objects

b

Windows Server 2025 Active Directory (AD) AdminSDHolder object must be configured with proper audit settings.

AU-12 - Medium - CCI-000172 - V-278152 - SV-278152r1129496_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-DC-000210

Vuln IDs

V-278152

Rule IDs

SV-278152r1129496_rule

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

Checks: C-82682r1129494_chk

This applies to domain controllers. It is NA for other systems. Review the auditing configuration for the "AdminSDHolder" object. Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). Verify "Advanced Features" is selected in the "View" menu. Select "System" under the domain being reviewed in the left pane. Right-click the "AdminSDHolder" object in the right pane and select "Properties". Select the "Security" tab. Select "Advanced", and then select the "Auditing" tab. If the audit settings on the "AdminSDHolder" object are not at least as inclusive as those below, this is a finding: Type - Fail Principal - Everyone Access - Full Control Inherited from - None Applies to - This object only The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. Type - Success Principal - Everyone Access - Special Inherited from - None Applies to - This object only (Access - Special = Write all properties, Modify permissions, Modify owner) Two instances with the following summary information will be listed: Type - Success Principal - Everyone Access - (blank) Inherited from - (CN of domain) Applies to - Descendant Organizational Unit objects

Fix: F-82587r1129495_fix

Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). Select "Advanced Features" in the "View" menu. Select "System" under the domain being reviewed in the left pane. Right-click the "AdminSDHolder" object in the right pane and select "Properties". Select the "Security" tab. Select "Advanced", and then select the "Auditing" tab. Configure the audit settings for AdminSDHolder object to include the following: Type - Fail Principal - Everyone Access - Full Control Inherited from - None Applies to - This object only The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. Type - Success Principal - Everyone Access - Special Inherited from - None Applies to - This object only (Access - Special = Write all properties, Modify permissions, Modify owner) Two instances with the following summary information will be listed: Type - Success Principal - Everyone Access - (blank) Inherited from - (CN of domain) Applies to - Descendant Organizational Unit objects

b

Windows Server 2025 Active Directory (AD) RID Manager$ object must be configured with proper audit settings.

AU-12 - Medium - CCI-000172 - V-278153 - SV-278153r1129499_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-DC-000220

Vuln IDs

V-278153

Rule IDs

SV-278153r1129499_rule

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

Checks: C-82683r1129497_chk

This applies to domain controllers. It is NA for other systems. Review the auditing configuration for the "RID Manager$" object. Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). Verify "Advanced Features" is selected in the "View" menu. Select "System" under the domain being reviewed in the left pane. Right-click the "RID Manager$" object in the right pane and select "Properties". Select the "Security" tab. Select "Advanced", and then select the "Auditing" tab. If the audit settings on the "RID Manager$" object are not at least as inclusive as those below, this is a finding: Type - Fail Principal - Everyone Access - Full Control Inherited from - None The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. Type - Success Principal - Everyone Access - Special Inherited from - None (Access - Special = Write all properties, All extended rights, Change RID master) Two instances with the following summary information will be listed: Type - Success Principal - Everyone Access - (blank) Inherited from - (CN of domain)

Fix: F-82588r1129498_fix

Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). Select "Advanced Features" in the "View" menu. Select "System" under the domain being reviewed in the left pane. Right-click the "RID Manager$" object in the right pane and select "Properties". Select the "Security" tab. Select "Advanced", and then select the "Auditing" tab. Configure the audit settings for RID Manager$ object to include the following: Type - Fail Principal - Everyone Access - Full Control Inherited from - None The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. Type - Success Principal - Everyone Access - Special Inherited from - None (Access - Special = Write all properties, All extended rights, Change RID master) Two instances with the following summary information will be listed: Type - Success Principal - Everyone Access - (blank) Inherited from - (CN of domain)

b

Windows Server 2025 must be configured to audit Account Management - Computer Account Management successes.

AC-2 - Medium - CCI-000018 - V-278154 - SV-278154r1129502_rule

RMF Control

AC-2

Severity

M

CCI

Version

WN25-DC-000230

Vuln IDs

V-278154

Rule IDs

SV-278154r1129502_rule

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Computer Account Management records events such as creating, changing, deleting, renaming, disabling, or enabling computer accounts. Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221

Checks: C-82684r1129500_chk

This applies to domain controllers. It is NA for other systems. Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or a command prompt with elevated privileges ("Run as administrator"). Enter "AuditPol /get /category:*" Compare the "AuditPol" settings with the following. If the system does not audit the following, this is a finding: Account Management >> Computer Account Management - Success

Fix: F-82589r1129501_fix

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

b

Windows Server 2025 must be configured to audit DS Access - Directory Service Access successes.

AU-12 - Medium - CCI-000172 - V-278155 - SV-278155r1129505_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-DC-000240

Vuln IDs

V-278155

Rule IDs

SV-278155r1129505_rule

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 Directory Service Access records events related to users accessing an Active Directory object. Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212

Checks: C-82685r1129503_chk

This applies to domain controllers. It is NA for other systems. Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or a command prompt with elevated privileges ("Run as administrator"). Enter "AuditPol /get /category:*". Compare the "AuditPol" settings with the following. If the system does not audit the following, this is a finding: DS Access >> Directory Service Access - Success

Fix: F-82590r1129504_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> DS Access >> Directory Service Access with Success selected.

b

Windows Server 2025 must be configured to audit DS Access - Directory Service Access failures.

AU-12 - Medium - CCI-000172 - V-278156 - SV-278156r1129508_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-DC-000250

Vuln IDs

V-278156

Rule IDs

SV-278156r1129508_rule

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 Directory Service Access records events related to users accessing an Active Directory object. Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212

Checks: C-82686r1129506_chk

This applies to domain controllers. It is NA for other systems. Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or a command prompt with elevated privileges ("Run as administrator"). Enter "AuditPol /get /category:*". Compare the "AuditPol" settings with the following. If the system does not audit the following, this is a finding: DS Access >> Directory Service Access - Failure

Fix: F-82591r1129507_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> DS Access >> Directory Service Access with "Failure" selected.

b

Windows Server 2025 must be configured to audit DS Access - Directory Service Changes successes.

AU-12 - Medium - CCI-000172 - V-278157 - SV-278157r1129511_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-DC-000260

Vuln IDs

V-278157

Rule IDs

SV-278157r1129511_rule

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 Directory Service Changes records events related to changes made to objects in Active Directory Domain Services. Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212

Checks: C-82687r1129509_chk

This applies to domain controllers. It is NA for other systems. Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or a command prompt with elevated privileges ("Run as administrator"). Enter "AuditPol /get /category:*". Compare the "AuditPol" settings with the following. If the system does not audit the following, this is a finding: DS Access >> Directory Service Changes - Success

Fix: F-82592r1129510_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> DS Access >> Directory Service Changes with "Success" selected.

b

Windows Server 2025 must be configured to audit DS Access - Directory Service Changes failures.

AU-12 - Medium - CCI-000172 - V-278158 - SV-278158r1129514_rule

RMF Control

AU-12

Severity

M

CCI

Version

WN25-DC-000270

Vuln IDs

V-278158

Rule IDs

SV-278158r1129514_rule

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 Directory Service Changes records events related to changes made to objects in Active Directory Domain Services. Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212

Checks: C-82688r1129512_chk

This applies to domain controllers. It is NA for other systems. Security Option "Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings" must be set to "Enabled" (WN25-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration. Open PowerShell or a command prompt with elevated privileges ("Run as administrator"). Enter "AuditPol /get /category:*". Compare the "AuditPol" settings with the following. If the system does not audit the following, this is a finding: DS Access >> Directory Service Changes - Failure

Fix: F-82593r1129513_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> DS Access >> Directory Service Changes with "Failure" selected.

b

Windows Server 2025 domain controllers must have a PKI server certificate.

IA-5 - Medium - CCI-000185 - V-278159 - SV-278159r1129517_rule

RMF Control

IA-5

Severity

M

CCI

Version

WN25-DC-000280

Vuln IDs

V-278159

Rule IDs

SV-278159r1129517_rule

Domain controllers are part of the chain of trust for PKI authentications. Without the appropriate certificate, the authenticity of the domain controller cannot be verified. Domain controllers must have a server certificate to establish authenticity as part of PKI authentications in the domain.

Checks: C-82689r1129515_chk

This applies to domain controllers. It is NA for other systems. Run "MMC". Select "Add/Remove Snap-in" from the "File" menu. Select "Certificates" in the left pane, and then click "Add >". Select "Computer Account", and then click "Next". Select the appropriate option for "Select the computer you want this snap-in to manage", and then click "Finish". Click "OK". Select and expand the "Certificates (Local Computer)" entry in the left pane. Select and expand the "Personal" entry in the left pane. Select the "Certificates" entry in the left pane. If no certificate for the domain controller exists in the right pane, this is a finding.

Fix: F-82594r1129516_fix

Obtain a server certificate for the domain controller.

c

Windows Server 2025 domain Controller PKI certificates must be issued by the DOD PKI or an approved External Certificate Authority (ECA).

IA-5 - High - CCI-000185 - V-278160 - SV-278160r1130176_rule

RMF Control

IA-5

Severity

H

CCI

Version

WN25-DC-000290

Vuln IDs

V-278160

Rule IDs

SV-278160r1130176_rule

A PKI implementation depends on the practices established by the Certificate Authority (CA) to ensure the implementation is secure. Without proper practices, the certificates issued by a CA have limited value in authentication functions. The use of multiple CAs from separate PKI implementations results in interoperability issues. If servers and clients do not have a common set of root CA certificates, they are not able to authenticate each other.

Checks: C-82690r1130175_chk

This applies to domain controllers. It is NA for other systems. Run "MMC". Select "Add/Remove Snap-in" from the "File" menu. Select "Certificates" in the left pane, and then click "Add >". Select "Computer Account", and then click "Next". Select the appropriate option for "Select the computer you want this snap-in to manage", and then click "Finish". Click "OK". Select and expand the "Certificates (Local Computer)" entry in the left pane. Select and expand the "Personal" entry in the left pane. Select the "Certificates" entry in the left pane. In the right pane, examine the "Issued By" field for the certificate to determine the issuing CA. If the "Issued By" field of the PKI certificate being used by the domain controller does not indicate the issuing CA is part of the DOD PKI or an approved ECA, this is a finding. If the certificates in use are issued by a CA authorized by the Component's CIO, this is a CAT II finding. There are multiple sources from which lists of valid DOD CAs and approved ECAs can be obtained: The Global Directory Service (GDS) website provides an online source. The address for this site is https://crl.gds.disa.mil. DOD Public Key Enablement (PKE) Engineering Support maintains the InstallRoot utility to manage DOD supported root certificates on Windows computers, which includes a list of authorized CAs. The utility package can be downloaded from the PKI and PKE Tools page on Cyber Exchange: https://https://cyber.mil/pki-pke/

Fix: F-82595r1129519_fix

Obtain a server certificate for the domain controller issued by the DOD PKI or an approved ECA.

c

Windows Server 2025 PKI certificates associated with user accounts must be issued by a DOD PKI or an approved External Certificate Authority (ECA).

IA-5 - High - CCI-000185 - V-278161 - SV-278161r1129523_rule

RMF Control

IA-5

Severity

H

CCI

Version

WN25-DC-000300

Vuln IDs

V-278161

Rule IDs

SV-278161r1129523_rule

A PKI implementation depends on the practices established by the Certificate Authority (CA) to ensure the implementation is secure. Without proper practices, the certificates issued by a CA have limited value in authentication functions. Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182

Checks: C-82691r1129521_chk

This applies to domain controllers. It is NA for other systems. Review user account mappings to PKI certificates. Open PowerShell. Enter "Get-ADUser -Filter * | FT Name, UserPrincipalName, Enabled". Exclude disabled accounts (e.g., DefaultAccount, Guest) and the krbtgt account. If the User Principal Name (UPN) is not in the format of an individual's identifier for the certificate type and for the appropriate domain suffix, this is a finding. For standard NIPRNet certificates, the individual's identifier is in the format of an Electronic Data Interchange - Personnel Identifier (EDI-PI). Alt Tokens and other certificates may use a different UPN format than the EDI-PI, which vary by organization. Verified these with the organization. NIPRNet example: Name - User Principal Name User1 - 1234567890@mil Refer to the PKE documentation for other network domain suffixes. If the mappings are to certificates issued by a CA authorized by the Component's CIO, this is a CAT II finding.

Fix: F-82596r1129522_fix

Map user accounts to PKI certificates using the appropriate UPN for the network. Refer to the PKE documentation for details.

b

Windows Server 2025 Active Directory (AD) user accounts, including administrators, must be configured to require the use of a Common Access Card (CAC), Personal Identity Verification (PIV)-compliant hardware token, or Alternate Logon Token (ALT) for user authentication.

IA-2 - Medium - CCI-000765 - V-278162 - SV-278162r1129526_rule

RMF Control

IA-2

Severity

M

CCI

CCI-000765

Version

WN25-DC-000310

Vuln IDs

V-278162

Rule IDs

SV-278162r1129526_rule

Smart cards such as the CAC support a two-factor authentication technique. This provides a higher level of trust in the asserted identity than use of the username and password for authentication. Satisfies: SRG-OS-000105-GPOS-00052, SRG-OS-000106-GPOS-00053, SRG-OS-000107-GPOS-00054, SRG-OS-000108-GPOS-00055, SRG-OS-000375-GPOS-00160, SRG-OS-000705-GPOS-00150

Checks: C-82692r1129524_chk

This applies to domain controllers. It is NA for other systems. Open PowerShell. Enter the following: "Get-ADUser -Filter {(Enabled -eq $True) -and (SmartcardLogonRequired -eq $False)} | FT Name" ("DistinguishedName" may be substituted for "Name" for more detailed output.) If any user accounts, including administrators, are listed, this is a finding. Alternately: To view sample accounts in "Active Directory Users and Computers" (available from various menus or run "dsa.msc"): Select the Organizational Unit (OU) where the user accounts are located. (By default, this is the Users node; however, accounts may be under other organization-defined OUs.) Right-click the sample user account and select "Properties". Select the "Account" tab. If any user accounts, including administrators, do not have "Smart card is required for interactive logon" checked in the "Account Options" area, this is a finding.

Fix: F-82597r1129525_fix

Configure all user accounts, including administrator accounts, in AD to enable the option "Smart card is required for interactive logon". Run "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). Select the OU where the user accounts are located. (By default, this is the Users node; however, accounts may be under other organization-defined OUs.) Right-click the user account and select "Properties". Select the "Account" tab. Check "Smart card is required for interactive logon" in the "Account Options" area.

b

Windows Server 2025 domain controllers must require LDAP access signing.

SC-8 - Medium - CCI-002418 - V-278163 - SV-278163r1129529_rule

RMF Control

SC-8

Severity

M

CCI

Version

WN25-DC-000320

Vuln IDs

V-278163

Rule IDs

SV-278163r1129529_rule

Unsigned network traffic is susceptible to man-in-the-middle attacks, where an intruder captures packets between the server and the client and modifies them before forwarding them to the client. In the case of an LDAP server, this means that an attacker could cause a client to make decisions based on false records from the LDAP directory. The risk of an attacker pulling this off can be decreased by implementing strong physical security measures to protect the network infrastructure. Furthermore, implementing Internet Protocol security (IPsec) authentication header (AH) mode, which performs mutual authentication and packet integrity for IP traffic, can make all types of man-in-the-middle attacks extremely difficult. Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188

Checks: C-82693r1129527_chk

This applies to domain controllers. It is NA for other systems. If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Services\NTDS\Parameters\ Value Name: LDAPServerIntegrity Value Type: REG_DWORD Value: 0x00000002 (2)

Fix: F-82598r1129528_fix

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

b

Windows Server 2025 domain controllers must be configured to allow reset of machine account passwords.

CM-6 - Medium - CCI-000366 - V-278164 - SV-278164r1129532_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-DC-000330

Vuln IDs

V-278164

Rule IDs

SV-278164r1129532_rule

Enabling this setting on all domain controllers in a domain prevents domain members from changing their computer account passwords. If these passwords are weak or compromised, the inability to change them may leave these computers vulnerable.

Checks: C-82694r1129530_chk

This applies to domain controllers. It is NA for other systems. If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ Value Name: RefusePasswordChange Value Type: REG_DWORD Value: 0x00000000 (0)

Fix: F-82599r1129531_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Domain controller: Refuse machine account password changes to "Disabled".

b

The Windows Server 2025 "Access this computer from the network" user right must only be assigned to the Administrators, Authenticated Users, and Enterprise Domain Controllers groups on domain controllers.

AC-3 - Medium - CCI-000213 - V-278165 - SV-278165r1130179_rule

RMF Control

AC-3

Severity

M

CCI

Version

WN25-DC-000340

Vuln IDs

V-278165

Rule IDs

SV-278165r1130179_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Access this computer from the network" right may access resources on the system, and this right must be limited to those requiring it.

Checks: C-82695r1130177_chk

This applies to domain controllers. It is NA for other systems. Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Access this computer from the network" right, this is a finding: - Administrators. - Authenticated Users. - Enterprise Domain Controllers. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If any SIDs other than the following are granted the "SeNetworkLogonRight" user right, this is a finding. S-1-5-32-544 (Administrators) S-1-5-11 (Authenticated Users) S-1-5-9 (Enterprise Domain Controllers) If an application requires this user right, this is not a finding. Vendor documentation must support the requirement for having the user right. The requirement must be documented with the information system security officer (ISSO). The application account must meet requirements for application account passwords, such as length (WN25-00-000050) and required frequency of changes (WN25-00-000060).

Fix: F-82600r1130178_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Access this computer from the network to include only the following accounts or groups: - Administrators. - Authenticated Users. - Enterprise Domain Controllers.

b

The Windows Server 2025 "Add workstations to domain" user right must only be assigned to the Administrators group on domain controllers.

AC-6 - Medium - CCI-002235 - V-278166 - SV-278166r1130182_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN25-DC-000350

Vuln IDs

V-278166

Rule IDs

SV-278166r1130182_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Add workstations to domain" right may add computers to a domain. This could result in unapproved or incorrectly configured systems being added to a domain.

Checks: C-82696r1130180_chk

This applies to domain controllers. It is NA for other systems. Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Add workstations to domain" right, this is a finding: - Administrators. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If any SIDs other than the following are granted the "SeMachineAccountPrivilege" user right, this is a finding. S-1-5-32-544 (Administrators)

Fix: F-82601r1130181_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Add workstations to domain to include only the following accounts or groups: - Administrators.

b

The Windows Server 2025 "Allow log on through Remote Desktop Services" user right must only be assigned to the Administrators group on domain controllers.

AC-3 - Medium - CCI-000213 - V-278167 - SV-278167r1130185_rule

RMF Control

AC-3

Severity

M

CCI

Version

WN25-DC-000360

Vuln IDs

V-278167

Rule IDs

SV-278167r1130185_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Allow log on through Remote Desktop Services" user right can access a system through Remote Desktop.

Checks: C-82697r1130183_chk

This applies to domain controllers, it is NA for other systems. Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Allow log on through Remote Desktop Services" user right, this is a finding: - Administrators. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If any SIDs other than the following are granted the "SeRemoteInteractiveLogonRight" user right, this is a finding. S-1-5-32-544 (Administrators)

Fix: F-82602r1130184_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Allow log on through Remote Desktop Services to include only the following accounts or groups: - Administrators.

b

The Windows Server 2025 "Deny access to this computer from the network" user right on domain controllers must be configured to prevent unauthenticated access.

AC-3 - Medium - CCI-000213 - V-278168 - SV-278168r1130188_rule

RMF Control

AC-3

Severity

M

CCI

Version

WN25-DC-000370

Vuln IDs

V-278168

Rule IDs

SV-278168r1130188_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. The "Deny access to this computer from the network" user right defines the accounts that are prevented from logging on from the network. The Guests group must be assigned this right to prevent unauthenticated access.

Checks: C-82698r1130186_chk

This applies to domain controllers. A separate version applies to other systems. Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If the following accounts or groups are not defined for the "Deny access to this computer from the network" user right, this is a finding: - Guests Group. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If the following SIDs are not defined for the "SeDenyNetworkLogonRight" user right, this is a finding. S-1-5-32-546 (Guests)

Fix: F-82603r1130187_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Deny access to this computer from the network to include the following: - Guests Group.

b

The Windows Server 2025 "Deny log on as a batch job" user right on domain controllers must be configured to prevent unauthenticated access.

AC-3 - Medium - CCI-000213 - V-278169 - SV-278169r1130191_rule

RMF Control

AC-3

Severity

M

CCI

Version

WN25-DC-000380

Vuln IDs

V-278169

Rule IDs

SV-278169r1130191_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. The "Deny log on as a batch job" user right defines accounts that are prevented from logging on to the system as a batch job, such as Task Scheduler. The Guests group must be assigned to prevent unauthenticated access.

Checks: C-82699r1130189_chk

This applies to domain controllers. A separate version applies to other systems. Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If the following accounts or groups are not defined for the "Deny log on as a batch job" user right, this is a finding: - Guests Group. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If the following SID(s) are not defined for the "SeDenyBatchLogonRight" user right, this is a finding: S-1-5-32-546 (Guests)

Fix: F-82604r1130190_fix

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

b

The Windows Server 2025 "Deny log on as a service" user right must be configured to include no accounts or groups (blank) on domain controllers.

AC-3 - Medium - CCI-000213 - V-278170 - SV-278170r1130192_rule

RMF Control

AC-3

Severity

M

CCI

Version

WN25-DC-000390

Vuln IDs

V-278170

Rule IDs

SV-278170r1130192_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. The "Deny log on as a service" user right defines accounts that are denied logon as a service. Incorrect configurations could prevent services from starting and result in a denial of service.

Checks: C-82700r1129548_chk

This applies to domain controllers. A separate version applies to other systems. Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups are defined for the "Deny log on as a service" user right, this is a finding. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If any SIDs are granted the "SeDenyServiceLogonRight" user right, this is a finding.

Fix: F-82605r1129549_fix

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

b

The Windows Server 2025 "Deny log on locally" user right on domain controllers must be configured to prevent unauthenticated access.

AC-3 - Medium - CCI-000213 - V-278171 - SV-278171r1130195_rule

RMF Control

AC-3

Severity

M

CCI

Version

WN25-DC-000400

Vuln IDs

V-278171

Rule IDs

SV-278171r1130195_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. The "Deny log on locally" user right defines accounts that are prevented from logging on interactively. The Guests group must be assigned this right to prevent unauthenticated access.

Checks: C-82701r1130193_chk

This applies to domain controllers. A separate version applies to other systems. Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If the following accounts or groups are not defined for the "Deny log on locally" user right, this is a finding: - Guests Group. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If the following SID(s) are not defined for the "SeDenyInteractiveLogonRight" user right, this is a finding: S-1-5-32-546 (Guests)

Fix: F-82606r1130194_fix

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

b

Windows Server 2025 must be configured for certificate-based authentication for domain controllers.

AC-3 - Medium - CCI-000213 - V-278172 - SV-278172r1129556_rule

RMF Control

AC-3

Severity

M

CCI

Version

WN25-DC-000405

Vuln IDs

V-278172

Rule IDs

SV-278172r1129556_rule

Active Directory domain services elevation of privilege vulnerability could allow a user rights to the system, such as administrative and other high-level capabilities.

Checks: C-82702r1129554_chk

This applies to domain controllers. This is not applicable for member servers. 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\Kdc Value Name: StrongCertificateBindingEnforcement Value Type: REG_DWORD Value: 0x00000001 (1) or 0x00000002 (2)

Fix: F-82607r1129555_fix

Configure the registry value. Registry Hive: HKEY_LOCAL_MACHINE Registry Path: SYSTEM\CurrentControlSet\Services\Kdc Value Name: StrongCertificateBindingEnforcement Value Type: REG_DWORD Value: 0x00000001 (1) or 0x00000002 (2)

b

Windows Server 2025 must be configured for name-based strong mappings for certificates.

AC-3 - Medium - CCI-000213 - V-278173 - SV-278173r1130306_rule

RMF Control

AC-3

Severity

M

CCI

Version

WN25-DC-000406

Vuln IDs

V-278173

Rule IDs

SV-278173r1130306_rule

Weak mappings give rise to security vulnerabilities and demand hardening measures. Certificate names must be correctly mapped to the intended user account in Active Directory. A lack of strong name-based mappings allows certain weak certificate mappings, such as Issuer/Subject AltSecID and User Principal Names (UPN) mappings, to be treated as strong mappings.

Checks: C-82703r1129557_chk

This applies to domain controllers. This is not applicable for member servers. Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Administrative Template >> System >> KDC >> Allow name-based strong mappings for certificates. If "Allow name-based strong mappings for certificates" is not "Enabled", this is a finding.

Fix: F-82608r1130305_fix

Configure the policy value for Computer Configuration >> Administrative Template >> System >> KDC >> Allow name-based strong mappings for certificates to "Enabled". The policy must contain exactly one certificate thumbprint per rule, with each rule represented as a tuple. Thumbprints must be unique and cannot be repeated in multiple rules. The sections of each tuple that are separated by semi-colons must be in the stated order, while the fields separated by commas can be in any order. The rules themselves are separated by new lines.

b

The Windows Server 2025 "Deny log on through Remote Desktop Services" user right on domain controllers must be configured to prevent unauthenticated access.

AC-17 - Medium - CCI-002314 - V-278174 - SV-278174r1130200_rule

RMF Control

AC-17

Severity

M

CCI

CCI-002314

Version

WN25-DC-000410

Vuln IDs

V-278174

Rule IDs

SV-278174r1130200_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. The "Deny log on through Remote Desktop Services" user right defines the accounts that are prevented from logging on using Remote Desktop Services. The Guests group must be assigned this right to prevent unauthenticated access.

Checks: C-82704r1130198_chk

This applies to domain controllers. A separate version applies to other systems. Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If the following accounts or groups are not defined for the "Deny log on through Remote Desktop Services" user right, this is a finding: - Guests Group. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If the following SID(s) are not defined for the "SeDenyRemoteInteractiveLogonRight" user right, this is a finding: S-1-5-32-546 (Guests)

Fix: F-82609r1130199_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Deny log on through Remote Desktop Services to include the following: - Guests Group.

b

The Windows Server 2025 "Enable computer and user accounts to be trusted for delegation" user right must only be assigned to the Administrators group on domain controllers.

AC-6 - Medium - CCI-002235 - V-278175 - SV-278175r1130203_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN25-DC-000420

Vuln IDs

V-278175

Rule IDs

SV-278175r1130203_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. The "Enable computer and user accounts to be trusted for delegation" user right allows the "Trusted for Delegation" setting to be changed. This could allow unauthorized users to impersonate other users.

Checks: C-82705r1130201_chk

This applies to domain controllers. A separate version applies to other systems. Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Enable computer and user accounts to be trusted for delegation" user right, this is a finding: - Administrators. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If any SIDs other than the following are granted the "SeEnableDelegationPrivilege" user right, this is a finding: S-1-5-32-544 (Administrators)

Fix: F-82610r1130202_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Enable computer and user accounts to be trusted for delegation to include only the following accounts or groups: - Administrators.

b

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

CM-6 - Medium - CCI-000366 - V-278176 - SV-278176r1130205_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-DC-000430

Vuln IDs

V-278176

Rule IDs

SV-278176r1130205_rule

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

Checks: C-82706r1129566_chk

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

Fix: F-82611r1130204_fix

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

c

Windows Server 2025 must only allow administrators responsible for the member server or standalone or nondomain joined system to have Administrator rights on the system.

AC-6 - High - CCI-002235 - V-278177 - SV-278177r1129571_rule

RMF Control

AC-6

Severity

H

CCI

Version

WN25-MS-000010

Vuln IDs

V-278177

Rule IDs

SV-278177r1129571_rule

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 using only 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 (Refer to AD.0003 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-82707r1129569_chk

This applies to member servers and standalone or nondomain joined systems. A separate version applies to domain controllers. Open "Computer Management". Navigate to "Groups" under "Local Users and Groups". Review the local "Administrators" group. Only 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 accounts that do not have responsibility for administration of the system are members of the local Administrators group, this is a finding. If the built-in Administrator account or other required administrative accounts are found on the system, this is not a finding.

Fix: F-82612r1129570_fix

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

b

Windows Server 2025 local administrator accounts must have their privileged token filtered to prevent elevated privileges from being used over the network on domain-joined member servers.

SC-3 - Medium - CCI-001084 - V-278178 - SV-278178r1130207_rule

RMF Control

SC-3

Severity

M

CCI

Version

WN25-MS-000020

Vuln IDs

V-278178

Rule IDs

SV-278178r1130207_rule

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-82708r1130206_chk

This applies to member servers. For domain controllers and standalone or nondomain joined systems, this is not applicable. If the following registry value does not exist or is not configured as specified, this is a finding: Registry HiveHKEY_LOCAL_MACHINE Registry Path\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System Value NameLocalAccountTokenFilterPolicy TypeREG_DWORD Value: 0x00000000 (0) This setting may cause issues with some network scanning tools if local administrative accounts are used remotely. Scans must 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-82613r1129573_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.

b

Windows Server 2025 local users on domain-joined member servers must not be enumerated.

CM-7 - Medium - CCI-000381 - V-278179 - SV-278179r1130209_rule

RMF Control

CM-7

Severity

M

CCI

Version

WN25-MS-000030

Vuln IDs

V-278179

Rule IDs

SV-278179r1130209_rule

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-82709r1130208_chk

This applies to member servers. For domain controllers and standalone or nondomain joined systems, this is not applicable. 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: 0x00000000 (0)

Fix: F-82614r1129576_fix

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

b

Windows Server 2025 must restrict unauthenticated Remote Procedure Call (RPC) clients from connecting to the RPC server on domain-joined member servers and standalone or nondomain joined systems.

IA-3 - Medium - CCI-001967 - V-278180 - SV-278180r1129580_rule

RMF Control

IA-3

Severity

M

CCI

CCI-001967

Version

WN25-MS-000040

Vuln IDs

V-278180

Rule IDs

SV-278180r1129580_rule

Unauthenticated RPC clients may allow anonymous access to sensitive information. Configuring RPC to restrict unauthenticated RPC clients from connecting to the RPC server will prevent anonymous connections.

Checks: C-82710r1129578_chk

This applies to member servers and standalone or nondomain joined systems, it is NA for domain controllers. If the following registry value does not exist or is not configured as specified, this is a finding: Registry HiveHKEY_LOCAL_MACHINE Registry Path\SOFTWARE\Policies\Microsoft\Windows NT\Rpc\ Value NameRestrictRemoteClients TypeREG_DWORD Value0x00000001 (1)

Fix: F-82615r1129579_fix

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

b

Windows Server 2025 must limit the caching of logon credentials to four or less on domain-joined member servers.

CM-6 - Medium - CCI-000366 - V-278181 - SV-278181r1130211_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-MS-000050

Vuln IDs

V-278181

Rule IDs

SV-278181r1130211_rule

The default Windows configuration caches the last logon credentials for users who log on interactively to a system. This feature is provided for system availability reasons, such as the user's machine being disconnected from the network or domain controllers being unavailable. Even though the credential cache is well protected, if a system is attacked, an unauthorized individual may isolate the password to a domain user account using a password-cracking program and gain access to the domain.

Checks: C-82711r1130210_chk

This applies to member servers. For domain controllers and standalone or nondomain joined systems, this is not applicable. If the following registry value does not exist or is not configured as specified, this is a finding: Registry HiveHKEY_LOCAL_MACHINE Registry Path\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\ Value NameCachedLogonsCount Value TypeREG_SZ Value4 (or less)

Fix: F-82616r1129582_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Interactive Logon: Number of previous logons to cache (in case Domain Controller is not available) to "4" logons or less.

b

Windows Server 2025 must restrict remote calls to the Security Account Manager (SAM) to Administrators on domain-joined member servers and standalone or nondomain joined systems.

AC-6 - Medium - CCI-002235 - V-278182 - SV-278182r1129586_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN25-MS-000060

Vuln IDs

V-278182

Rule IDs

SV-278182r1129586_rule

The Windows SAM stores users' passwords. Restricting Remote Procedure Call (RPC) connections to the SAM to Administrators helps protect those credentials.

Checks: C-82712r1129584_chk

This applies to member servers and standalone or nondomain joined systems; it is NA for domain controllers. 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: RestrictRemoteSAM Value Type: REG_SZ Value: O:BAG:BAD:(A;;RC;;;BA)

Fix: F-82617r1129585_fix

Navigate to the policy Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Network access: Restrict clients allowed to make remote calls to SAM. Select "Edit Security" to configure the "Security descriptor:". Add "Administrators" in "Group or user names:" if it is not already listed (this is the default). Select "Administrators" in "Group or user names:". Select "Allow" for "Remote Access" in "Permissions for "Administrators". Click "OK". The "Security descriptor:" must be populated with "O:BAG:BAD:(A;;RC;;;BA) for the policy to be enforced.

b

Windows Server 2025 Access this computer from the network user right must only be assigned to the Administrators and Authenticated Users groups on domain-joined member servers and standalone or nondomain joined systems.

AC-3 - Medium - CCI-000213 - V-278183 - SV-278183r1130214_rule

RMF Control

AC-3

Severity

M

CCI

Version

WN25-MS-000070

Vuln IDs

V-278183

Rule IDs

SV-278183r1130214_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Access this computer from the network" user right may access resources on the system, and this right must be limited to those requiring it.

Checks: C-82713r1130212_chk

This applies to member servers and standalone or nondomain joined systems. A separate version applies to domain controllers. Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Access this computer from the network" user right, this is a finding: - Administrators. - Authenticated Users. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If any SIDs other than the following are granted the "SeNetworkLogonRight" user right, this is a finding: S-1-5-32-544 (Administrators) S-1-5-11 (Authenticated Users) If an application requires this user right, this is not a finding. Vendor documentation must support the requirement for having the user right. The requirement must be documented with the information system security officer (ISSO). The application account must meet requirements for application account passwords, such as length (WN25-00-000050) and required frequency of changes (WN25-00-000060).

Fix: F-82618r1130213_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Access this computer from the network to include only the following accounts or groups: - Administrators. - Authenticated Users.

b

The Windows Server 2025 "Deny access to this computer from the network" user right on domain-joined member servers must be configured to prevent access from highly privileged domain accounts and local accounts and from unauthenticated access on all systems.

AC-3 - Medium - CCI-000213 - V-278184 - SV-278184r1129592_rule

RMF Control

AC-3

Severity

M

CCI

Version

WN25-MS-000080

Vuln IDs

V-278184

Rule IDs

SV-278184r1129592_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. The "Deny access to this computer from the network" user right defines the accounts that are prevented from logging on from the network. In an Active Directory Domain, denying logons to the Enterprise Admins and Domain Admins groups on lower-trust systems helps mitigate the risk of privilege escalation from credential theft attacks, which could lead to the compromise of an entire domain. Local accounts on domain-joined systems must also be assigned this right to decrease the risk of lateral movement resulting from credential theft attacks. The Guests group must be assigned this right to prevent unauthenticated access.

Checks: C-82714r1129590_chk

This applies to member servers and standalone or nondomain joined systems. A separate version applies to domain controllers. Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If the following accounts or groups are not defined for the "Deny access to this computer from the network" user right, this is a finding: Domain Systems Only: - Enterprise Admins group. - Domain Admins group. - "Local account and member of Administrators group" or "Local account" (see Note below). All Systems: - Guests group. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If the following SIDs are not defined for the "SeDenyNetworkLogonRight" user right, this is a finding. Domain Systems Only: S-1-5-root domain-519 (Enterprise Admins) S-1-5-domain-512 (Domain Admins) S-1-5-114 ("Local account and member of Administrators group") or S-1-5-113 ("Local account") All Systems: S-1-5-32-546 (Guests) Note: These are built-in security groups. "Local account" is more restrictive but may cause issues on servers such as systems that provide failover clustering.

Fix: F-82619r1129591_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Deny access to this computer from the network to include the following: Domain Systems Only: - Enterprise Admins group. - Domain Admins group. - "Local account and member of Administrators group" or "Local account" (see Note below). All Systems: - Guests group. Note: These are built-in security groups. "Local account" is more restrictive but may cause issues on servers such as systems that provide failover clustering.

b

Windows Server 2025 Deny log on as a batch job user right on domain-joined member servers must be configured to prevent access from highly privileged domain accounts and from unauthenticated access on all systems.

AC-3 - Medium - CCI-000213 - V-278185 - SV-278185r1129595_rule

RMF Control

AC-3

Severity

M

CCI

Version

WN25-MS-000090

Vuln IDs

V-278185

Rule IDs

SV-278185r1129595_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. The "Deny log on as a batch job" user right defines accounts that are prevented from logging on to the system as a batch job, such as Task Scheduler. In an Active Directory Domain, denying logons to the Enterprise Admins and Domain Admins groups on lower-trust systems helps mitigate the risk of privilege escalation from credential theft attacks, which could lead to the compromise of an entire domain. The Guests group must be assigned to prevent unauthenticated access.

Checks: C-82715r1129593_chk

This applies to member servers and standalone or nondomain joined systems. A separate version applies to domain controllers. Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If the following accounts or groups are not defined for the "Deny log on as a batch job" user right, this is a finding: Domain Systems Only: - Enterprise Admins Group. - Domain Admins Group. All Systems: - Guests Group. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If the following SIDs are not defined for the "SeDenyBatchLogonRight" user right, this is a finding. Domain Systems Only: S-1-5-root domain-519 (Enterprise Admins) S-1-5-domain-512 (Domain Admins) All Systems: S-1-5-32-546 (Guests)

Fix: F-82620r1129594_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Deny log on as a batch job to include the following: Domain Systems Only: - Enterprise Admins Group. - Domain Admins Group. All Systems: - Guests Group.

b

The Windows Server 2025 "Deny log on as a service" user right on domain-joined member servers must be configured to prevent access from highly privileged domain accounts. No other groups or accounts must be assigned this right.

AC-3 - Medium - CCI-000213 - V-278186 - SV-278186r1130216_rule

RMF Control

AC-3

Severity

M

CCI

Version

WN25-MS-000100

Vuln IDs

V-278186

Rule IDs

SV-278186r1130216_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. The "Deny log on as a service" user right defines accounts that are denied logon as a service. In an Active Directory Domain, denying logons to the Enterprise Admins and Domain Admins groups on lower-trust systems helps mitigate the risk of privilege escalation from credential theft attacks, which could lead to the compromise of an entire domain. Incorrect configurations could prevent services from starting and result in a denial of service.

Checks: C-82716r1130215_chk

This applies to member servers and standalone or nondomain joined systems. A separate version applies to domain controllers. Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If the following accounts or groups are not defined for the "Deny log on as a service" user right on domain-joined systems, this is a finding: - Enterprise Admins Group. - Domain Admins Group. If any accounts or groups are defined for the "Deny log on as a service" user right on nondomain-joined systems, this is a finding. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If the following SIDs are not defined for the "SeDenyServiceLogonRight" user right on domain-joined systems, this is a finding: S-1-5-root domain-519 (Enterprise Admins) S-1-5-domain-512 (Domain Admins) If any SIDs are defined for the user right on nondomain-joined systems, this is a finding.

Fix: F-82621r1129597_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Deny log on as a service to include the following: Domain systems: - Enterprise Admins Group. - Domain Admins Group.

b

The Windows Server 2025 "Deny log on locally" user right on domain-joined member servers must be configured to prevent access from highly privileged domain accounts and from unauthenticated access on all systems.

AC-3 - Medium - CCI-000213 - V-278187 - SV-278187r1129601_rule

RMF Control

AC-3

Severity

M

CCI

Version

WN25-MS-000110

Vuln IDs

V-278187

Rule IDs

SV-278187r1129601_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. The "Deny log on locally" user right defines accounts that are prevented from logging on interactively. In an Active Directory Domain, denying logons to the Enterprise Admins and Domain Admins groups on lower-trust systems helps mitigate the risk of privilege escalation from credential theft attacks, which could lead to the compromise of an entire domain. The Guests group must be assigned this right to prevent unauthenticated access.

Checks: C-82717r1129599_chk

This applies to member servers and standalone or nondomain joined systems. A separate version applies to domain controllers. Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If the following accounts or groups are not defined for the "Deny log on locally" user right, this is a finding: Domain Systems Only: - Enterprise Admins Group. - Domain Admins Group. All Systems: - Guests Group. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If the following SIDs are not defined for the "SeDenyInteractiveLogonRight" user right, this is a finding: Domain Systems Only: S-1-5-root domain-519 (Enterprise Admins) S-1-5-domain-512 (Domain Admins) All Systems: S-1-5-32-546 (Guests)

Fix: F-82622r1129600_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Deny log on locally to include the following: Domain Systems Only: - Enterprise Admins Group. - Domain Admins Group. All Systems: - Guests Group.

b

The Windows Server 2025 "Deny log on through Remote Desktop Services" user right on domain-joined member servers must be configured to prevent access from highly privileged domain accounts and all local accounts and from unauthenticated access on all systems.

AC-17 - Medium - CCI-002314 - V-278188 - SV-278188r1129604_rule

RMF Control

AC-17

Severity

M

CCI

CCI-002314

Version

WN25-MS-000120

Vuln IDs

V-278188

Rule IDs

SV-278188r1129604_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. The "Deny log on through Remote Desktop Services" user right defines the accounts that are prevented from logging on using Remote Desktop Services. In an Active Directory Domain, denying logons to the Enterprise Admins and Domain Admins groups on lower-trust systems helps mitigate the risk of privilege escalation from credential theft attacks, which could lead to the compromise of an entire domain. Local accounts on domain-joined systems must also be assigned this right to decrease the risk of lateral movement resulting from credential theft attacks. The Guests group must be assigned this right to prevent unauthenticated access.

Checks: C-82718r1129602_chk

This applies to member servers and standalone or nondomain joined systems. A separate version applies to domain controllers. Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If the following accounts or groups are not defined for the "Deny log on through Remote Desktop Services" user right, this is a finding: Domain Systems Only: - Enterprise Admins group. - Domain Admins group. - Local account (see Note below). All Systems: - Guests group. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If the following SIDs are not defined for the "SeDenyRemoteInteractiveLogonRight" user right, this is a finding. Domain Systems Only: S-1-5-root domain-519 (Enterprise Admins) S-1-5-domain-512 (Domain Admins) S-1-5-113 ("Local account") All Systems: S-1-5-32-546 (Guests) Note: "Local account" refers to the Windows built-in security group.

Fix: F-82623r1129603_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Deny log on through Remote Desktop Services to include the following: Domain Systems Only: - Enterprise Admins group. - Domain Admins group. - Local account (see Note below). All Systems: - Guests group. Note: "Local account" refers to the Windows built-in security group.

b

The Windows Server 2025 "Enable computer and user accounts to be trusted for delegation" user right must not be assigned to any groups or accounts on domain-joined member servers and standalone or nondomain joined systems.

AC-6 - Medium - CCI-002235 - V-278189 - SV-278189r1129607_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN25-MS-000130

Vuln IDs

V-278189

Rule IDs

SV-278189r1129607_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. The "Enable computer and user accounts to be trusted for delegation" user right allows the "Trusted for Delegation" setting to be changed. This could allow unauthorized users to impersonate other users.

Checks: C-82719r1129605_chk

This applies to member servers and standalone or nondomain joined systems. A separate version applies to domain controllers. Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups are granted the "Enable computer and user accounts to be trusted for delegation" user right, this is a finding. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If any SIDs are granted the "SeEnableDelegationPrivilege" user right, this is a finding.

Fix: F-82624r1129606_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Enable computer and user accounts to be trusted for delegation to be defined but containing no entries (blank).

c

Windows Server 2025 must be running Credential Guard on domain-joined member servers.

CM-6 - High - CCI-000366 - V-278190 - SV-278190r1130308_rule

RMF Control

CM-6

Severity

H

CCI

Version

WN25-MS-000140

Vuln IDs

V-278190

Rule IDs

SV-278190r1130308_rule

Credential Guard uses virtualization-based security to protect data that could be used in credential theft attacks if compromised. This authentication information, which was stored in the Local Security Authority (LSA) in previous versions of Windows, is isolated from the rest of operating system and can only be accessed by privileged system software.

Checks: C-82720r1130217_chk

For domain controllers and standalone or nondomain joined systems, this is not applicable. Open PowerShell with elevated privileges (run as administrator). Enter the following: "Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard" If "SecurityServicesRunning" does not include a value of "1" (e.g., "{1, 2}"), this is a finding. Alternately: Run "System Information". Under "System Summary", verify the following: If "Device Guard Security Services Running" does not list "Credential Guard", this is a finding. The policy settings referenced in the Fix section will configure the following registry value. However, due to hardware requirements, the registry value alone does not ensure proper function. Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeviceGuard\ Value Name: LsaCfgFlags Value Type: REG_DWORD Value: 0x00000001 (1) (Enabled with UEFI lock) A Microsoft article on Credential Guard system requirements can be found at the following link: https://docs.microsoft.com/en-us/windows/security/identity-protection/credential-guard/credential-guard-requirements

Fix: F-82625r1130307_fix

Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Device Guard >> Turn On Virtualization Based Security to "Enabled" with "Enabled with UEFI lock" selected for "Credential Guard Configuration". A Microsoft article on Credential Guard system requirements can be found at the following link: https://docs.microsoft.com/en-us/windows/security/identity-protection/credential-guard/credential-guard-requirements Severity Override Guidance: The AO can allow the severity override if they have reviewed the overall protection provided to the affected servers that are not capable of complying with the Credential Guard requirement. Items that must be reviewed/considered for compliance or mitigation for non-Credential Guard compliance are: - The use of Microsoft Local Administrator Password Solution (LAPS) or similar products to control different local administrative passwords for all affected servers. This is to include a strict password change requirement (60 days or less). - Strict separation of roles and duties. Server administrator credentials cannot be used on Windows desktop to administer it. Documentation of all exceptions must be supplied. - Use of a Privileged Access Workstation (PAW) and adherence to the Clean Source principle for administering affected servers. - Boundary Protection that is currently in place to protect from vulnerabilities in the network/servers. - Windows Defender rule block credential stealing from LSASS.exe is applied. This rule can only be applied if Windows Defender is in use. - The overall number of vulnerabilities that are unmitigated on the network/servers.

b

The operating system must prohibit the use of cached authenticators after one day.

IA-5 - Medium - CCI-002007 - V-278191 - SV-278191r1130219_rule

RMF Control

IA-5

Severity

M

CCI

CCI-002007

Version

WN25-NS-000420

Vuln IDs

V-278191

Rule IDs

SV-278191r1130219_rule

If cached authentication information is out-of-date, the validity of the authentication information may be questionable.

Checks: C-82721r1129611_chk

Using Registry Editor, browse to HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft\Windows NT\CurrentVersion\Winlogon. If CachedLogonCount is set to anything but "0" (zero), this is a finding.

Fix: F-82626r1129612_fix

Using Registry Editor browse to HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft\Windows NT\CurrentVersion\Winlogon. Set CachedLogonCount is set to 0 (zero).

b

Windows Server 2025 must have the DOD Root Certificate Authority (CA) certificates installed in the Trusted Root Store.

IA-5 - Medium - CCI-000185 - V-278192 - SV-278192r1129616_rule

RMF Control

IA-5

Severity

M

CCI

Version

WN25-PK-000010

Vuln IDs

V-278192

Rule IDs

SV-278192r1129616_rule

To ensure secure DOD websites and DOD-signed code are properly validated, the system must trust the DOD Root CAs. The DOD root certificates will ensure that the trust chain is established for server certificates issued from the DOD CAs. Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182, SRG-OS-000775-GPOS-00230

Checks: C-82722r1129614_chk

The certificates and thumbprints referenced below apply to unclassified systems. Refer to the PKE documentation for other networks. Open 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 2, OU=PKI, OU=DOD, O=U.S. Government, C=US Thumbprint: 8C941B34EA1EA6ED9AE2BC54CF687252B4C9B561 NotAfter: 12/5/2029 Subject: CN=DOD Root CA 3, OU=PKI, OU=DOD, O=U.S. Government, C=US Thumbprint: D73CA91102A2204A36459ED32213B467D7CE97FB NotAfter: 12/30/2029 Subject: CN=DOD Root CA 4, OU=PKI, OU=DOD, O=U.S. Government, C=US Thumbprint: B8269F25DBD937ECAFD4C35A9838571723F2D026 NotAfter: 7/25/2032 Subject: CN=DOD Root CA 5, OU=PKI, OU=DOD, O=U.S. Government, C=US Thumbprint: 4ECB5CC3095670454DA1CBD410FC921F46B8564B NotAfter: 6/14/2041 Alternately, use the Certificates MMC snap-in: Run "MMC". Select "File", "Add/Remove Snap-in". Select "Certificates" and click "Add". Select "Computer account" and click "Next". Select "Local computer: (the computer this console is running on)" and 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 the certificate and select "Open". Select the "Details" Tab. Scroll to the bottom and select "Thumbprint". If the DOD Root CA certificates below are not listed or the value for the "Thumbprint" field is not as noted, this is a finding: DOD Root CA 3 Thumbprint: D73CA91102A2204A36459ED32213B467D7CE97FB Valid to: Sunday, December 30, 2029 DOD Root CA 4 Thumbprint: B8269F25DBD937ECAFD4C35A9838571723F2D026 Valid to: Sunday, July 25, 2032 DOD Root CA 5 Thumbprint: 4ECB5CC3095670454DA1CBD410FC921F46B8564B Valid to: Friday, June 14, 2041

Fix: F-82627r1129615_fix

Install the DOD Root CA certificates: DOD Root CA 3 DOD Root CA 4 DOD Root CA 5 The InstallRoot tool is available on Cyber Exchange at https://cyber.mil/pki-pke/tools-configuration-files.

b

Windows Server 2025 must have the DOD Interoperability Root Certificate Authority (CA) cross-certificates installed in the Untrusted Certificates Store on unclassified systems.

IA-5 - Medium - CCI-000185 - V-278193 - SV-278193r1129619_rule

RMF Control

IA-5

Severity

M

CCI

Version

WN25-PK-000020

Vuln IDs

V-278193

Rule IDs

SV-278193r1129619_rule

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. Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182

Checks: C-82723r1129617_chk

This is applicable to unclassified systems. It is NA for others. Open PowerShell as an administrator. Execute the following command: Get-ChildItem -Path Cert:Localmachine\disallowed | Where {$_.Issuer -Like "*DOD Interoperability*" -and $_.Subject -Like "*DOD*"} | FL Subject, Issuer, Thumbprint, NotAfter If the following certificate "Subject", "Issuer", and "Thumbprint" information is not displayed, this is a finding: Subject: CN=DOD Root CA 3, OU=PKI, OU=DOD, O=U.S. Government, C=US Issuer: CN=DOD Interoperability Root CA 2, OU=PKI, OU=DOD, O=U.S. Government, C=US Thumbprint: AC06108CA348CC03B53795C64BF84403C1DBD341 NotAfter: 1/22/2025 10:22:56 AM Subject: CN=DOD Root CA 2, OU=PKI, OU=DOD, O=U.S. Government, C=US Issuer: CN=DOD Interoperability Root CA 1, OU=PKI, OU=DOD, O=U.S. Government, C=US Thumbprint: A8C27332CCB4CA49554CE55D34062A7DD2850C02 NotAfter: 8/26/2025 9:25:51 AM Alternately, use the Certificates MMC snap-in: Run "MMC". Select "File", "Add/Remove Snap-in". Select "Certificates" and click "Add". Select "Computer account" and click "Next". Select "Local computer: (the computer this console is running on)" and 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 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 Issued To: DOD Root CA 3 Issued By: DOD Interoperability Root CA 2 Thumbprint: AC06108CA348CC03B53795C64BF84403C1DBD341 Valid to: Saturday, January 22, 2025

Fix: F-82628r1129618_fix

Install the DOD Interoperability Root CA cross-certificates on unclassified systems. Issued To - Issued By - Thumbprint DOD Root CA 3- DOD Interoperability Root CA 2 - 49CBE933151872E17C8EAE7F0ABA97FB610F6477 DOD Root CA 3 - DOD Interoperability Root CA 2 - AC06108CA348CC03B53795C64BF84403C1DBD341 Administrators must run the Federal Bridge Certification Authority (FBCA) Cross-Certificate Removal Tool once as an administrator and once as the current user. The FBCA Cross-Certificate Remover Tool and User Guide are available on Cyber Exchange at https://cyber.mil/pki-pke/tools-configuration-files.

b

Windows Server 2025 must have the US DOD CCEB Interoperability Root CA cross-certificates in the Untrusted Certificates Store on unclassified systems.

IA-5 - Medium - CCI-000185 - V-278194 - SV-278194r1129622_rule

RMF Control

IA-5

Severity

M

CCI

Version

WN25-PK-000030

Vuln IDs

V-278194

Rule IDs

SV-278194r1129622_rule

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. Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182

Checks: C-82724r1129620_chk

This is applicable to unclassified systems. It is NA for others. Open PowerShell as an administrator. Execute the following command: Get-ChildItem -Path Cert:Localmachine\disallowed | Where Issuer -Like "*CCEB Interoperability*" | FL Subject, Issuer, Thumbprint, NotAfter If the following certificate "Subject", "Issuer", and "Thumbprint" information is not displayed, this is a finding. Subject: CN=DOD Root CA 3, OU=PKI, OU=DOD, O=U.S. Government, C=US Issuer: CN=US DOD CCEB Interoperability Root CA 2, OU=PKI, OU=DOD, O=U.S. Government, C=US Thumbprint: AF132AC65DE86FC4FB3FE51FD637EBA0FF0B12A9 NotAfter: 8/26/2025 9:07:50 AM 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: 929BF3196896994C0A201DF4A5B71F603FEFBF2E NotAfter: 9/27/2025 Alternately, use the Certificates MMC snap-in: Run "MMC". Select "File", "Add/Remove Snap-in". Select "Certificates" and click "Add". Select "Computer account" and click "Next". Select "Local computer: (the computer this console is running on)" and 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 the certificate and select "Open". Select the "Details" Tab. Scroll to the bottom and select "Thumbprint". If the certificate below is not listed or the value for the "Thumbprint" field is not as noted, this is a finding: Issued To: DOD Root CA 3 Issued By: US DOD CCEB Interoperability Root CA 2 Thumbprint: AF132AC65DE86FC4FB3FE51FD637EBA0FF0B12A9 Valid to: Friday, August 26, 2025 Issued To: DOD Root CA 3 Issued By: US DOD CCEB Interoperability Root CA 2 Thumbprint: 929BF3196896994C0A201DF4A5B71F603FEFBF2E Valid: Friday, September 27, 2025

Fix: F-82629r1129621_fix

Install the US DOD CCEB Interoperability Root CA cross-certificate on unclassified systems. Issued To - Issued By - Thumbprint DOD Root CA 3 - US DOD CCEB Interoperability Root CA 2 - AF132AC65DE86FC4FB3FE51FD637EBA0FF0B12A9 DOD Root CA 3 - US DOD CCEB Interoperability Root CA 2 - 929BF3196896994C0A201DF4A5B71F603FEFBF2E Administrators must run the Federal Bridge Certification Authority (FBCA) Cross-Certificate Removal Tool once as an administrator and once as the current user. The FBCA Cross-Certificate Remover Tool and User Guide are available on Cyber Exchange at https://cyber.mil/pki-pke/tools-configuration-files.

b

Windows Server 2025 must have the built-in guest account disabled.

IA-8 - Medium - CCI-000804 - V-278195 - SV-278195r1129625_rule

RMF Control

IA-8

Severity

M

CCI

CCI-000804

Version

WN25-SO-000010

Vuln IDs

V-278195

Rule IDs

SV-278195r1129625_rule

A system faces an increased vulnerability threat if the built-in guest account is not disabled. This 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-82725r1129623_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. For server core installations, run the following command: Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt If "EnableGuestAccount" equals "1" in the file, this is a finding.

Fix: F-82630r1129624_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Accounts: Guest account status to "Disabled".

c

Windows Server 2025 must prevent local accounts with blank passwords from being used from the network.

CM-6 - High - CCI-000366 - V-278196 - SV-278196r1129628_rule

RMF Control

CM-6

Severity

H

CCI

Version

WN25-SO-000020

Vuln IDs

V-278196

Rule IDs

SV-278196r1129628_rule

An account without a password can allow unauthorized access to a system as only the username would be required. Password policies must prevent accounts with blank passwords from existing on a system. However, if a local account with a blank password does exist, enabling this setting will prevent network access, limiting the account to local console logon only.

Checks: C-82726r1129626_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: 0x00000001 (1)

Fix: F-82631r1129627_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 Windows Server 2025 built-in administrator account must be renamed.

CM-6 - Medium - CCI-000366 - V-278197 - SV-278197r1129631_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-SO-000030

Vuln IDs

V-278197

Rule IDs

SV-278197r1129631_rule

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-82727r1129629_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. For server core installations, run the following command: Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt If "NewAdministratorName" is not something other than "Administrator" in the file, this is a finding.

Fix: F-82632r1129630_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 Windows Server 2025 built-in guest account must be renamed.

CM-6 - Medium - CCI-000366 - V-278198 - SV-278198r1129634_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-SO-000040

Vuln IDs

V-278198

Rule IDs

SV-278198r1129634_rule

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-82728r1129632_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. For server core installations, run the following command: Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt If "NewGuestName" is not something other than "Guest" in the file, this is a finding.

Fix: F-82633r1129633_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

Windows Server 2025 must force audit policy subcategory settings to override audit policy category settings.

AU-12 - Medium - CCI-000169 - V-278199 - SV-278199r1129637_rule

RMF Control

AU-12

Severity

M

CCI

CCI-000169

Version

WN25-SO-000050

Vuln IDs

V-278199

Rule IDs

SV-278199r1129637_rule

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. This setting allows administrators to enable more precise auditing capabilities.

Checks: C-82729r1129635_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ Value Name: SCENoApplyLegacyAuditPolicy Value Type: REG_DWORD Value: 0x00000001 (1)

Fix: F-82634r1129636_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Audit: Force audit policy subcategory settings (Windows 7 or later) to override audit policy category settings to "Enabled".

b

The Windows Server 2025 setting Domain member: Digitally encrypt or sign secure channel data (always) must be configured to Enabled.

SC-8 - Medium - CCI-002418 - V-278200 - SV-278200r1129640_rule

RMF Control

SC-8

Severity

M

CCI

Version

WN25-SO-000060

Vuln IDs

V-278200

Rule IDs

SV-278200r1129640_rule

Requests sent on the secure channel are authenticated, and sensitive information (such as passwords) is encrypted, but not all information is encrypted. If this policy is enabled, outgoing secure channel traffic will be encrypted and signed. Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188

Checks: C-82730r1129638_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ Value Name: RequireSignOrSeal Value Type: REG_DWORD Value: 0x00000001 (1)

Fix: F-82635r1129639_fix

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

b

Windows Server 2025 setting Domain member: Digitally encrypt secure channel data (when possible) must be configured to Enabled.

SC-8 - Medium - CCI-002418 - V-278201 - SV-278201r1129643_rule

RMF Control

SC-8

Severity

M

CCI

Version

WN25-SO-000070

Vuln IDs

V-278201

Rule IDs

SV-278201r1129643_rule

Requests sent on the secure channel are authenticated, and sensitive information (such as passwords) is encrypted, but not all information is encrypted. If this policy is enabled, outgoing secure channel traffic will be encrypted. Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188

Checks: C-82731r1129641_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ Value Name: SealSecureChannel Value Type: REG_DWORD Value: 0x00000001 (1)

Fix: F-82636r1129642_fix

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

b

The Windows Server 2025 setting Domain member: Digitally sign secure channel data (when possible) must be configured to Enabled.

SC-8 - Medium - CCI-002418 - V-278202 - SV-278202r1129646_rule

RMF Control

SC-8

Severity

M

CCI

Version

WN25-SO-000080

Vuln IDs

V-278202

Rule IDs

SV-278202r1129646_rule

Requests sent on the secure channel are authenticated, and sensitive information (such as passwords) is encrypted, but the channel is not integrity checked. If this policy is enabled, outgoing secure channel traffic will be signed. Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188

Checks: C-82732r1129644_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ Value Name: SignSecureChannel Value Type: REG_DWORD Value: 0x00000001 (1)

Fix: F-82637r1129645_fix

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

b

Windows Server 2025 computer account password must not be prevented from being reset.

IA-3 - Medium - CCI-001967 - V-278203 - SV-278203r1129649_rule

RMF Control

IA-3

Severity

M

CCI

CCI-001967

Version

WN25-SO-000090

Vuln IDs

V-278203

Rule IDs

SV-278203r1129649_rule

Computer account passwords are changed automatically on a regular basis. Disabling automatic password changes can make the system more vulnerable to malicious access. Frequent password changes can be a significant safeguard for the system. A new password for the computer account will be generated every 30 days.

Checks: C-82733r1129647_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ Value Name: DisablePasswordChange Value Type: REG_DWORD Value: 0x00000000 (0)

Fix: F-82638r1129648_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Domain member: Disable machine account password changes to "Disabled".

b

Windows Server 2025 maximum age for machine account passwords must be configured to 30 days or less.

CM-6 - Medium - CCI-000366 - V-278204 - SV-278204r1129652_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-SO-000100

Vuln IDs

V-278204

Rule IDs

SV-278204r1129652_rule

Computer account passwords are changed automatically on a regular basis. This setting controls the maximum password age that a machine account may have. This must be set to no more than 30 days, ensuring the machine changes its password monthly.

Checks: C-82734r1129650_chk

This is the default configuration for this setting (30 days). If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ Value Name: MaximumPasswordAge Value Type: REG_DWORD Value: 0x0000001e (30) (or less, but not 0)

Fix: F-82639r1129651_fix

This is the default configuration for this setting (30 days). Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Domain member: Maximum machine account password age to "30" or less (excluding "0", which is unacceptable).

b

Windows Server 2025 must be configured to require a strong session key.

SC-8 - Medium - CCI-002418 - V-278205 - SV-278205r1129655_rule

RMF Control

SC-8

Severity

M

CCI

Version

WN25-SO-000110

Vuln IDs

V-278205

Rule IDs

SV-278205r1129655_rule

A computer connecting to a domain controller will establish a secure channel. The secure channel connection may be subject to compromise, such as hijacking or eavesdropping, if strong session keys are not used to establish the connection. Requiring strong session keys enforces 128-bit encryption between systems. Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188

Checks: C-82735r1129653_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ Value Name: RequireStrongKey Value Type: REG_DWORD Value: 0x00000001 (1) This setting may prevent a system from being joined to a domain if not configured consistently between systems.

Fix: F-82640r1129654_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Domain member: Require strong (Windows 2000 or Later) session key to "Enabled".

b

Windows Server 2025 machine inactivity limit must be set to 15 minutes or less, locking the system with the screen saver.

AC-11 - Medium - CCI-000056 - V-278206 - SV-278206r1129658_rule

RMF Control

AC-11

Severity

M

CCI

CCI-000056

Version

WN25-SO-000120

Vuln IDs

V-278206

Rule IDs

SV-278206r1129658_rule

Unattended systems are susceptible to unauthorized use and must be locked when unattended. The screen saver must be set at a maximum of 15 minutes and be password protected. This protects critical and sensitive data from exposure to unauthorized personnel with physical access to the computer. Satisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000029-GPOS-00010, SRG-OS-000031-GPOS-00012

Checks: C-82736r1129656_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ Value Name: InactivityTimeoutSecs Value Type: REG_DWORD Value: 0x00000384 (900) (or less, excluding "0" which is effectively disabled)

Fix: F-82641r1129657_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Interactive logon: Machine inactivity limit to "900" seconds or less, excluding "0", which is effectively disabled.

b

The Windows Server 2025 required legal notice must be configured to display before console logon.

AC-8 - Medium - CCI-000048 - V-278207 - SV-278207r1129661_rule

RMF Control

AC-8

Severity

M

CCI

CCI-000048

Version

WN25-SO-000130

Vuln IDs

V-278207

Rule IDs

SV-278207r1129661_rule

Failure to display the logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources. Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007, SRG-OS-000228-GPOS-00088

Checks: C-82737r1129659_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ Value Name: LegalNoticeText Value Type: REG_SZ Value: See message text below You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.

Fix: F-82642r1129660_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Interactive Logon: Message text for users attempting to log on to the following: You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.

a

Windows Server 2025 title for legal banner dialog box must be configured with the appropriate text.

AC-8 - Low - CCI-000048 - V-278208 - SV-278208r1129664_rule

RMF Control

AC-8

Severity

L

CCI

CCI-000048

Version

WN25-SO-000140

Vuln IDs

V-278208

Rule IDs

SV-278208r1129664_rule

Failure to display the logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources. Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000228-GPOS-00088

Checks: C-82738r1129662_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ Value Name: LegalNoticeCaption Value Type: REG_SZ Value: See message title options below "DOD Notice and Consent Banner", "US Department of Defense Warning Statement", or an organization-defined equivalent. If an organization-defined title is used, it can in no case contravene or modify the language of the banner text required in WN25-SO-000150. Automated tools may only search for the titles defined above. If an organization-defined title is used, a manual review will be required.

Fix: F-82643r1129663_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Interactive Logon: Message title for users attempting to log on to "DOD Notice and Consent Banner", "US Department of Defense Warning Statement", or an organization-defined equivalent. If an organization-defined title is used, it can in no case contravene or modify the language of the message text required in WN25-SO-000150.

b

The Windows Server 2025 Smart Card removal option must be configured to Force Logoff or Lock Workstation.

CM-6 - Medium - CCI-000366 - V-278209 - SV-278209r1129667_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-SO-000150

Vuln IDs

V-278209

Rule IDs

SV-278209r1129667_rule

Unattended systems are susceptible to unauthorized use and must be locked. Configuring a system to lock when a smart card is removed will ensure the system is inaccessible when unattended.

Checks: C-82739r1129665_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\ Value Name: scremoveoption Value Type: REG_SZ Value: 1 (Lock Workstation) or 2 (Force Logoff) If configuring this on servers causes issues, such as terminating users' remote sessions, and the organization has a policy in place that any other sessions on the servers, such as administrative console logons, are manually locked or logged off when unattended or not in use, this would be acceptable. This must be documented with the information system security officer (ISSO).

Fix: F-82644r1129666_fix

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

b

The Windows Server 2025 setting Microsoft network client: Digitally sign communications (always) must be configured to Enabled.

SC-8 - Medium - CCI-002418 - V-278210 - SV-278210r1129670_rule

RMF Control

SC-8

Severity

M

CCI

Version

WN25-SO-000160

Vuln IDs

V-278210

Rule IDs

SV-278210r1129670_rule

The server message block (SMB) protocol provides the basis for many network operations. Digitally signed SMB packets aid in preventing man-in-the-middle attacks. If this policy is enabled, the SMB client will only communicate with an SMB server that performs SMB packet signing. Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188

Checks: C-82740r1129668_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ Value Name: RequireSecuritySignature Value Type: REG_DWORD Value: 0x00000001 (1)

Fix: F-82645r1129669_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Microsoft network client: Digitally sign communications (always) to "Enabled".

b

The Windows Server 2025 setting Microsoft network client: Digitally sign communications (if server agrees) must be configured to Enabled.

SC-8 - Medium - CCI-002418 - V-278211 - SV-278211r1129673_rule

RMF Control

SC-8

Severity

M

CCI

Version

WN25-SO-000170

Vuln IDs

V-278211

Rule IDs

SV-278211r1129673_rule

The server message block (SMB) protocol provides the basis for many network operations. If this policy is enabled, the SMB client will request packet signing when communicating with an SMB server that is enabled or required to perform SMB packet signing. Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188

Checks: C-82741r1129671_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ Value Name: EnableSecuritySignature Value Type: REG_DWORD Value: 0x00000001 (1)

Fix: F-82646r1129672_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Microsoft network client: Digitally sign communications (if server agrees) to "Enabled".

b

Windows Server 2025 unencrypted passwords must not be sent to third-party Server Message Block (SMB) servers.

IA-5 - Medium - CCI-000197 - V-278212 - SV-278212r1129676_rule

RMF Control

IA-5

Severity

M

CCI

CCI-000197

Version

WN25-SO-000180

Vuln IDs

V-278212

Rule IDs

SV-278212r1129676_rule

Some non-Microsoft SMB servers only support unencrypted (plain-text) password authentication. Sending plain-text passwords across the network when authenticating to an SMB server reduces the overall security of the environment. Check with the vendor of the SMB server to determine if there is a way to support encrypted password authentication.

Checks: C-82742r1129674_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry HiveHKEY_LOCAL_MACHINE Registry Path\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ Value NameEnablePlainTextPassword Value TypeREG_DWORD Value0x00000000 (0)

Fix: F-82647r1129675_fix

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

b

The Windows Server 2025 setting Microsoft network server: Digitally sign communications (always) must be configured to Enabled.

SC-8 - Medium - CCI-002418 - V-278213 - SV-278213r1129679_rule

RMF Control

SC-8

Severity

M

CCI

Version

WN25-SO-000190

Vuln IDs

V-278213

Rule IDs

SV-278213r1129679_rule

The server message block (SMB) protocol provides the basis for many network operations. Digitally signed SMB packets aid in preventing man-in-the-middle attacks. If this policy is enabled, the SMB server will only communicate with an SMB client that performs SMB packet signing. Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188

Checks: C-82743r1129677_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\ Value Name: RequireSecuritySignature Value Type: REG_DWORD Value: 0x00000001 (1)

Fix: F-82648r1129678_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Microsoft network server: Digitally sign communications (always) to "Enabled".

b

The Windows Server 2025 setting Microsoft network server: Digitally sign communications (if client agrees) must be configured to Enabled.

SC-8 - Medium - CCI-002418 - V-278214 - SV-278214r1129682_rule

RMF Control

SC-8

Severity

M

CCI

Version

WN25-SO-000200

Vuln IDs

V-278214

Rule IDs

SV-278214r1129682_rule

The server message block (SMB) protocol provides the basis for many network operations. Digitally signed SMB packets aid in preventing man-in-the-middle attacks. If this policy is enabled, the SMB server will negotiate SMB packet signing as requested by the client. Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188

Checks: C-82744r1129680_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\ Value Name: EnableSecuritySignature Value Type: REG_DWORD Value: 0x00000001 (1)

Fix: F-82649r1129681_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Microsoft network server: Digitally sign communications (if client agrees) to "Enabled".

c

Windows Server 2025 must not allow anonymous SID/Name translation.

CM-6 - High - CCI-000366 - V-278215 - SV-278215r1129685_rule

RMF Control

CM-6

Severity

H

CCI

Version

WN25-SO-000210

Vuln IDs

V-278215

Rule IDs

SV-278215r1129685_rule

Allowing anonymous SID/Name translation can provide sensitive information for accessing a system. Only authorized users must be able to perform such translations.

Checks: C-82745r1129683_chk

Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options. If the value for "Network access: Allow anonymous SID/Name translation" is not set to "Disabled", this is a finding.

Fix: F-82650r1129684_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Network access: Allow anonymous SID/Name translation to "Disabled".

c

Windows Server 2025 must not allow anonymous enumeration of Security Account Manager (SAM) accounts.

CM-6 - High - CCI-000366 - V-278216 - SV-278216r1129688_rule

RMF Control

CM-6

Severity

H

CCI

Version

WN25-SO-000220

Vuln IDs

V-278216

Rule IDs

SV-278216r1129688_rule

Anonymous enumeration of SAM accounts allows anonymous logon users (null session connections) to list all accounts names, thus providing a list of potential points to attack the system.

Checks: C-82746r1129686_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ Value Name: RestrictAnonymousSAM Value Type: REG_DWORD Value: 0x00000001 (1)

Fix: F-82651r1129687_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Network access: Do not allow anonymous enumeration of SAM accounts to "Enabled".

c

Windows Server 2025 must not allow anonymous enumeration of shares.

SC-4 - High - CCI-001090 - V-278217 - SV-278217r1129691_rule

RMF Control

SC-4

Severity

H

CCI

Version

WN25-SO-000230

Vuln IDs

V-278217

Rule IDs

SV-278217r1129691_rule

Allowing anonymous logon users (null session connections) to list all account names and enumerate all shared resources can provide a map of potential points to attack the system.

Checks: C-82747r1129689_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ Value Name: RestrictAnonymous Value Type: REG_DWORD Value: 0x00000001 (1)

Fix: F-82652r1129690_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Network access: Do not allow anonymous enumeration of SAM accounts and shares to "Enabled".

b

Windows Server 2025 must be configured to prevent anonymous users from having the same permissions as the Everyone group.

CM-6 - Medium - CCI-000366 - V-278218 - SV-278218r1129694_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-SO-000240

Vuln IDs

V-278218

Rule IDs

SV-278218r1129694_rule

Access by anonymous users must be restricted. If this setting is enabled, anonymous users have the same rights and permissions as the built-in Everyone group. Anonymous users must not have these permissions or rights.

Checks: C-82748r1129692_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ Value Name: EveryoneIncludesAnonymous Value Type: REG_DWORD Value: 0x00000000 (0)

Fix: F-82653r1129693_fix

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

c

Windows Server 2025 must restrict anonymous access to Named Pipes and Shares.

SC-4 - High - CCI-001090 - V-278219 - SV-278219r1129697_rule

RMF Control

SC-4

Severity

H

CCI

Version

WN25-SO-000250

Vuln IDs

V-278219

Rule IDs

SV-278219r1129697_rule

Allowing anonymous access to named pipes or shares provides the potential for unauthorized system access. This setting restricts access to those defined in "Network access: Named Pipes that can be accessed anonymously" and "Network access: Shares that can be accessed anonymously", both of which must be blank under other requirements.

Checks: C-82749r1129695_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\ Value Name: RestrictNullSessAccess Value Type: REG_DWORD Value: 0x00000001 (1)

Fix: F-82654r1129696_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Network access: Restrict anonymous access to Named Pipes and Shares to "Enabled".

b

Windows Server 2025 services using Local System that use Negotiate when reverting to NTLM authentication must use the computer identity instead of authenticating anonymously.

CM-6 - Medium - CCI-000366 - V-278220 - SV-278220r1129700_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-SO-000260

Vuln IDs

V-278220

Rule IDs

SV-278220r1129700_rule

Services using Local System that use Negotiate when reverting to NTLM authentication may gain unauthorized access if allowed to authenticate anonymously versus using the computer identity.

Checks: C-82750r1129698_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Control\LSA\ Value Name: UseMachineId Type: REG_DWORD Value: 0x00000001 (1)

Fix: F-82655r1129699_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Network security: Allow Local System to use computer identity for NTLM to "Enabled".

b

Windows Server 2025 must prevent NTLM from falling back to a Null session.

CM-6 - Medium - CCI-000366 - V-278221 - SV-278221r1129703_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-SO-000270

Vuln IDs

V-278221

Rule IDs

SV-278221r1129703_rule

NTLM sessions that are allowed to fall back to Null (unauthenticated) sessions may gain unauthorized access.

Checks: C-82751r1129701_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Control\LSA\MSV1_0\ Value Name: allownullsessionfallback Type: REG_DWORD Value: 0x00000000 (0)

Fix: F-82656r1129702_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Network security: Allow LocalSystem NULL session fallback to "Disabled".

b

Windows Server 2025 must prevent PKU2U authentication using online identities.

CM-6 - Medium - CCI-000366 - V-278222 - SV-278222r1129706_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-SO-000280

Vuln IDs

V-278222

Rule IDs

SV-278222r1129706_rule

PKU2U is a peer-to-peer authentication protocol. This setting prevents online identities from authenticating to domain-joined systems. Authentication will be centrally managed with Windows user accounts.

Checks: C-82752r1129704_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Control\LSA\pku2u\ Value Name: AllowOnlineID Type: REG_DWORD Value: 0x00000000 (0)

Fix: F-82657r1129705_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Network security: Allow PKU2U authentication requests to this computer to use online identities to "Disabled".

b

Windows Server 2025 Kerberos encryption types must be configured to prevent the use of DES and RC4 encryption suites.

IA-7 - Medium - CCI-000803 - V-278223 - SV-278223r1129709_rule

RMF Control

IA-7

Severity

M

CCI

CCI-000803

Version

WN25-SO-000290

Vuln IDs

V-278223

Rule IDs

SV-278223r1129709_rule

Certain encryption types are no longer considered secure. The DES and RC4 encryption suites must not be used for Kerberos encryption. Note: Organizations with domain controllers running earlier versions of Windows where RC4 encryption is enabled, which select "The other domain supports Kerberos AES Encryption" on domain trusts, may be required to allow client communication across the trust relationship.

Checks: C-82753r1129707_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters\ Value Name: SupportedEncryptionTypes Value Type: REG_DWORD Value: 0x7ffffff8 (2147483640)

Fix: F-82658r1129708_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Network security: Configure encryption types allowed for Kerberos to "Enabled" with only the following selected: AES128_HMAC_SHA1 AES256_HMAC_SHA1 Future encryption types Note: Organizations with domain controllers running earlier versions of Windows where RC4 encryption is enabled, which select "The other domain supports Kerberos AES Encryption" on domain trusts, may be required to allow client communication across the trust relationship.

c

Windows Server 2025 must be configured to prevent the storage of the LAN Manager hash of passwords.

High - CCI-004066 - V-278224 - SV-278224r1129712_rule

RMF Control

Severity

H

CCI

Version

WN25-SO-000300

Vuln IDs

V-278224

Rule IDs

SV-278224r1129712_rule

The LAN Manager hash uses a weak encryption algorithm and there are several tools available that use this hash to retrieve account passwords. This setting controls whether a LAN Manager hash of the password is stored in the SAM the next time the password is changed.

Checks: C-82754r1129710_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ Value Name: NoLMHash Value Type: REG_DWORD Value: 0x00000001 (1)

Fix: F-82659r1129711_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Network security: Do not store LAN Manager hash value on next password change to "Enabled".

c

Windows Server 2025 LAN Manager authentication level must be configured to send NTLMv2 response only and to refuse LM and NTLM.

CM-6 - High - CCI-000366 - V-278225 - SV-278225r1129715_rule

RMF Control

CM-6

Severity

H

CCI

Version

WN25-SO-000310

Vuln IDs

V-278225

Rule IDs

SV-278225r1129715_rule

The Kerberos v5 authentication protocol is the default for authentication of users who are logging on to domain accounts. NTLM, which is less secure, is retained in later Windows versions for compatibility with clients and servers that are running earlier versions of Windows or applications that still use it. It is also used to authenticate logons to standalone or nondomain joined computers that are running later versions.

Checks: C-82755r1129713_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ Value Name: LmCompatibilityLevel Value Type: REG_DWORD Value: 0x00000005 (5)

Fix: F-82660r1129714_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Network security: LAN Manager authentication level to "Send NTLMv2 response only. Refuse LM & NTLM".

b

Windows Server 2025 must be configured to at least negotiate signing for LDAP client signing.

CM-6 - Medium - CCI-000366 - V-278226 - SV-278226r1129718_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-SO-000320

Vuln IDs

V-278226

Rule IDs

SV-278226r1129718_rule

This setting controls the signing requirements for LDAP clients. This must be set to "Negotiate signing" or "Require signing", depending on the environment and type of LDAP server in use.

Checks: C-82756r1129716_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Services\LDAP\ Value Name: LDAPClientIntegrity Value Type: REG_DWORD Value: 0x00000001 (1)

Fix: F-82661r1129717_fix

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

b

Windows Server 2025 session security for NTLM SSP-based clients must be configured to require NTLMv2 session security and 128-bit encryption.

CM-6 - Medium - CCI-000366 - V-278227 - SV-278227r1129721_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-SO-000330

Vuln IDs

V-278227

Rule IDs

SV-278227r1129721_rule

Microsoft has implemented a variety of security support providers for use with Remote Procedure Call (RPC) sessions. All of the options must be enabled to ensure the maximum security level.

Checks: C-82757r1129719_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\ Value Name: NTLMMinClientSec Value Type: REG_DWORD Value: 0x20080000 (537395200)

Fix: F-82662r1129720_fix

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

b

Windows Server 2025 session security for NTLM SSP-based servers must be configured to require NTLMv2 session security and 128-bit encryption.

CM-6 - Medium - CCI-000366 - V-278228 - SV-278228r1129724_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-SO-000340

Vuln IDs

V-278228

Rule IDs

SV-278228r1129724_rule

Microsoft has implemented a variety of security support providers for use with Remote Procedure Call (RPC) sessions. All of the options must be enabled to ensure the maximum security level.

Checks: C-82758r1129722_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\ Value Name: NTLMMinServerSec Value Type: REG_DWORD Value: 0x20080000 (537395200)

Fix: F-82663r1129723_fix

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

b

Windows Server 2025 users must be required to enter a password to access private keys stored on the computer.

IA-5 - Medium - CCI-000186 - V-278229 - SV-278229r1129727_rule

RMF Control

IA-5

Severity

M

CCI

CCI-000186

Version

WN25-SO-000350

Vuln IDs

V-278229

Rule IDs

SV-278229r1129727_rule

If the private key is discovered, an attacker can use the key to authenticate as an authorized user and gain access to the network infrastructure. The cornerstone of the PKI is the private key used to encrypt or digitally sign information. If the private key is stolen, this will lead to the compromise of the authentication and nonrepudiation gained through PKI because the attacker can use the private key to digitally sign documents and pretend to be the authorized user. Both the holders of a digital certificate and the issuing authority must protect the computers, storage devices, or whatever they use to keep the private keys.

Checks: C-82759r1129725_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Policies\Microsoft\Cryptography\ Value Name: ForceKeyProtection Type: REG_DWORD Value: 0x00000002 (2)

Fix: F-82664r1129726_fix

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

b

Windows Server 2025 must be configured to use FIPS-compliant algorithms for encryption, hashing, and signing.

SC-13 - Medium - CCI-002450 - V-278230 - SV-278230r1129730_rule

RMF Control

SC-13

Severity

M

CCI

CCI-002450

Version

WN25-SO-000360

Vuln IDs

V-278230

Rule IDs

SV-278230r1129730_rule

This setting ensures the system uses FIPS-compliant algorithms for encryption, hashing, and signing. FIPS-compliant algorithms meet specific standards established by the U.S. Government and must be the algorithms used for all OS encryption functions.

Checks: C-82760r1129728_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\ Value Name: Enabled Value Type: REG_DWORD Value: 0x00000001 (1) Clients with this setting enabled will not be able to communicate via digitally encrypted or signed protocols with servers that do not support these algorithms. Both the browser and web server must be configured to use TLS; otherwise, the browser will not be able to connect to a secure site.

Fix: F-82665r1129729_fix

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

a

Windows Server 2025 default permissions of global system objects must be strengthened.

CM-6 - Low - CCI-000366 - V-278231 - SV-278231r1129733_rule

RMF Control

CM-6

Severity

L

CCI

Version

WN25-SO-000370

Vuln IDs

V-278231

Rule IDs

SV-278231r1129733_rule

Windows systems maintain a global list of shared system resources such as DOS device names, mutexes, and semaphores. Each type of object is created with a default Discretionary Access Control List (DACL) that specifies who can access the objects with what permissions. When this policy is enabled, the default DACL is stronger, allowing nonadministrative users to read shared objects but not to modify shared objects they did not create.

Checks: C-82761r1129731_chk

If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Control\Session Manager\ Value Name: ProtectionMode Value Type: REG_DWORD Value: 0x00000001 (1)

Fix: F-82666r1129732_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> System objects: Strengthen default permissions of internal system objects (e.g., Symbolic Links) to "Enabled".

b

Windows Server 2025 User Account Control (UAC) approval mode for the built-in Administrator must be enabled.

Medium - CCI-004895 - V-278232 - SV-278232r1129736_rule

RMF Control

Severity

M

CCI

Version

WN25-SO-000380

Vuln IDs

V-278232

Rule IDs

SV-278232r1129736_rule

UAC is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting configures the built-in Administrator account so that it runs in Admin Approval Mode. Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157

Checks: C-82762r1129734_chk

UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2025 versus Server with Desktop Experience). If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ Value Name: FilterAdministratorToken Value Type: REG_DWORD Value: 0x00000001 (1)

Fix: F-82667r1129735_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> User Account Control: Admin Approval Mode for the Built-in Administrator account to "Enabled".

b

Windows Server 2025 UIAccess applications must not be allowed to prompt for elevation without using the secure desktop.

SC-3 - Medium - CCI-001084 - V-278233 - SV-278233r1129739_rule

RMF Control

SC-3

Severity

M

CCI

Version

WN25-SO-000390

Vuln IDs

V-278233

Rule IDs

SV-278233r1129739_rule

User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting prevents User Interface Accessibility programs from disabling the secure desktop for elevation prompts.

Checks: C-82763r1129737_chk

UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2025 versus Server with Desktop Experience). If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ Value Name: EnableUIADesktopToggle Value Type: REG_DWORD Value: 0x00000000 (0)

Fix: F-82668r1129738_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> User Account Control: Allow UIAccess applications to prompt for elevation without using the secure desktop to "Disabled".

b

Windows Server 2025 User Account Control (UAC) must, at a minimum, prompt administrators for consent on the secure desktop.

SC-3 - Medium - CCI-001084 - V-278234 - SV-278234r1129742_rule

RMF Control

SC-3

Severity

M

CCI

Version

WN25-SO-000400

Vuln IDs

V-278234

Rule IDs

SV-278234r1129742_rule

UAC is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting configures the elevation requirements for logged-on administrators to complete a task that requires raised privileges.

Checks: C-82764r1129740_chk

UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2025 versus Server with Desktop Experience). If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ Value Name: ConsentPromptBehaviorAdmin Value Type: REG_DWORD Value: 0x00000002 (2) (Prompt for consent on the secure desktop) 0x00000001 (1) (Prompt for credentials on the secure desktop)

Fix: F-82669r1129741_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode to "Prompt for consent on the secure desktop". The more secure option for this setting, "Prompt for credentials on the secure desktop", would also be acceptable.

b

Windows Server 2025 User Account Control (UAC) must automatically deny standard user requests for elevation.

Medium - CCI-004895 - V-278235 - SV-278235r1129745_rule

RMF Control

Severity

M

CCI

Version

WN25-SO-000410

Vuln IDs

V-278235

Rule IDs

SV-278235r1129745_rule

UAC is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting controls the behavior of elevation when requested by a standard user account. Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157

Checks: C-82765r1129743_chk

UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2025 versus Server with Desktop Experience). If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ Value Name: ConsentPromptBehaviorUser Value Type: REG_DWORD Value: 0x00000000 (0)

Fix: F-82670r1129744_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> User Account Control: Behavior of the elevation prompt for standard users to "Automatically deny elevation requests".

b

Windows Server 2025 User Account Control (UAC) must be configured to detect application installations and prompt for elevation.

SC-3 - Medium - CCI-001084 - V-278236 - SV-278236r1129748_rule

RMF Control

SC-3

Severity

M

CCI

Version

WN25-SO-000420

Vuln IDs

V-278236

Rule IDs

SV-278236r1129748_rule

UAC is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting requires Windows to respond to application installation requests by prompting for credentials.

Checks: C-82766r1129746_chk

UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2025 versus Server with Desktop Experience). If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ Value Name: EnableInstallerDetection Value Type: REG_DWORD Value: 0x00000001 (1)

Fix: F-82671r1129747_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> User Account Control: Detect application installations and prompt for elevation to "Enabled".

b

Windows Server 2025 User Account Control (UAC) must only elevate UIAccess applications that are installed in secure locations.

SC-3 - Medium - CCI-001084 - V-278237 - SV-278237r1129751_rule

RMF Control

SC-3

Severity

M

CCI

Version

WN25-SO-000430

Vuln IDs

V-278237

Rule IDs

SV-278237r1129751_rule

UAC is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting configures Windows to only allow applications installed in a secure location on the file system, such as the Program Files or the Windows\System32 folders, to run with elevated privileges.

Checks: C-82767r1129749_chk

UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2025 versus Server with Desktop Experience). If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ Value Name: EnableSecureUIAPaths Value Type: REG_DWORD Value: 0x00000001 (1)

Fix: F-82672r1129750_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> User Account Control: Only elevate UIAccess applications that are installed in secure locations to "Enabled".

b

Windows Server 2025 User Account Control (UAC) must run all administrators in Admin Approval Mode, enabling UAC.

Medium - CCI-004895 - V-278238 - SV-278238r1129754_rule

RMF Control

Severity

M

CCI

Version

WN25-SO-000440

Vuln IDs

V-278238

Rule IDs

SV-278238r1129754_rule

UAC is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting enables UAC. Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157

Checks: C-82768r1129752_chk

UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2025 versus Server with Desktop Experience). If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ Value Name: EnableLUA Value Type: REG_DWORD Value: 0x00000001 (1)

Fix: F-82673r1129753_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> User Account Control: Run all administrators in Admin Approval Mode to "Enabled".

b

Windows Server 2025 User Account Control (UAC) must virtualize file and registry write failures to per-user locations.

SC-3 - Medium - CCI-001084 - V-278239 - SV-278239r1129757_rule

RMF Control

SC-3

Severity

M

CCI

Version

WN25-SO-000450

Vuln IDs

V-278239

Rule IDs

SV-278239r1129757_rule

UAC is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting configures non-UAC-compliant applications to run in virtualized file and registry entries in per-user locations, allowing them to run.

Checks: C-82769r1129755_chk

UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2025 versus Server with Desktop Experience). If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ Value Name: EnableVirtualization Value Type: REG_DWORD Value: 0x00000001 (1)

Fix: F-82674r1129756_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> User Account Control: Virtualize file and registry write failures to per-user locations to "Enabled".

b

Windows Server 2025 must preserve zone information when saving attachments.

CM-6 - Medium - CCI-000366 - V-278240 - SV-278240r1129760_rule

RMF Control

CM-6

Severity

M

CCI

Version

WN25-UC-000010

Vuln IDs

V-278240

Rule IDs

SV-278240r1129760_rule

Attachments from outside sources may contain malicious code. Preserving zone of origin (internet, intranet, local, restricted) information on file attachments allows Windows to determine risk.

Checks: C-82770r1129758_chk

The default behavior is for Windows to mark file attachments with their zone information. If the registry Value Name below does not exist, this is not a finding. If it exists and is configured with a value of "2", this is not a finding. If it exists and is configured with a value of "1", this is a finding. Registry Hive: HKEY_CURRENT_USER Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Attachments\ Value Name: SaveZoneInformation Value Type: REG_DWORD Value: 0x00000002 (2) (or if the Value Name does not exist)

Fix: F-82675r1129759_fix

The default behavior is for Windows to mark file attachments with their zone information. If this needs to be corrected, configure the policy value for User Configuration >> Administrative Templates >> Windows Components >> Attachment Manager >> Do not preserve zone information in file attachments to "Not Configured" or "Disabled".

b

The Windows Server 2025 "Access Credential Manager as a trusted caller" user right must not be assigned to any groups or accounts.

AC-6 - Medium - CCI-002235 - V-278241 - SV-278241r1129763_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN25-UR-000010

Vuln IDs

V-278241

Rule IDs

SV-278241r1129763_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Access Credential Manager as a trusted caller" user right may be able to retrieve the credentials of other accounts from Credential Manager.

Checks: C-82771r1129761_chk

Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups are granted the "Access Credential Manager as a trusted caller" user right, this is a finding. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If any SIDs are granted the "SeTrustedCredManAccessPrivilege" user right, this is a finding.

Fix: F-82676r1129762_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Access Credential Manager as a trusted caller to be defined but containing no entries (blank).

c

The Windows Server 2025 "Act as part of the operating system" user right must not be assigned to any groups or accounts.

AC-6 - High - CCI-002235 - V-278242 - SV-278242r1129766_rule

RMF Control

AC-6

Severity

H

CCI

Version

WN25-UR-000020

Vuln IDs

V-278242

Rule IDs

SV-278242r1129766_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Act as part of the operating system" user right can assume the identity of any user and gain access to resources that the user is authorized to access. Any accounts with this right can take complete control of a system.

Checks: C-82772r1129764_chk

Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups (to include administrators), are granted the "Act as part of the operating system" user right, this is a finding. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If any SIDs are granted the "SeTcbPrivilege" user right, this is a finding. If an application requires this user right, this is not a finding. Vendor documentation must support the requirement for having the user right. The requirement must be documented with the information system security officer (ISSO). The application account must meet requirements for application account passwords, such as length (WN25-00-000050) and required frequency of changes (WN25-00-000060). Passwords for accounts with this user right must be protected as highly privileged accounts.

Fix: F-82677r1129765_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Act as part of the operating system to be defined but containing no entries (blank).

b

The Windows Server 2025 "Allow log on locally" user right must only be assigned to the Administrators group.

AC-3 - Medium - CCI-000213 - V-278243 - SV-278243r1130222_rule

RMF Control

AC-3

Severity

M

CCI

Version

WN25-UR-000030

Vuln IDs

V-278243

Rule IDs

SV-278243r1130222_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Allow log on locally" user right can log on interactively to a system.

Checks: C-82773r1130220_chk

Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Allow log on locally" user right, this is a finding: - Administrators. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If any SIDs other than the following are granted the "SeInteractiveLogonRight" user right, this is a finding: S-1-5-32-544 (Administrators) If an application requires this user right, this is not a finding. Vendor documentation must support the requirement for having the user right. The requirement must be documented with the information system security officer (ISSO). The application account must meet requirements for application account passwords, such as length (WN25-00-000050) and required frequency of changes (WN25-00-000060).

Fix: F-82678r1130221_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Allow log on locally to include only the following accounts or groups: - Administrators.

b

The Windows Server 2025 "Back up files and directories" user right must only be assigned to the Administrators group.

AC-6 - Medium - CCI-002235 - V-278244 - SV-278244r1130225_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN25-UR-000040

Vuln IDs

V-278244

Rule IDs

SV-278244r1130225_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Back up files and directories" user right can circumvent file and directory permissions and could allow access to sensitive data.

Checks: C-82774r1130223_chk

Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Back up files and directories" user right, this is a finding: - Administrators. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If any SIDs other than the following are granted the "SeBackupPrivilege" user right, this is a finding: S-1-5-32-544 (Administrators) If an application requires this user right, this is not a finding. Vendor documentation must support the requirement for having the user right. The requirement must be documented with the information system security officer (ISSO). The application account must meet requirements for application account passwords, such as length (WN25-00-000050) and required frequency of changes (WN25-00-000060).

Fix: F-82679r1130224_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Back up files and directories to include only the following accounts or groups: - Administrators.

b

The Windows Server 2025 "Create a pagefile" user right must only be assigned to the Administrators group.

AC-6 - Medium - CCI-002235 - V-278245 - SV-278245r1130228_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN25-UR-000050

Vuln IDs

V-278245

Rule IDs

SV-278245r1130228_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Create a pagefile" user right can change the size of a pagefile, which could affect system performance.

Checks: C-82775r1130226_chk

Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Create a pagefile" user right, this is a finding: - Administrators. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If any SIDs other than the following are granted the "SeCreatePagefilePrivilege" user right, this is a finding: S-1-5-32-544 (Administrators)

Fix: F-82680r1130227_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Create a pagefile to include only the following accounts or groups: - Administrators.

c

The Windows Server 2025 "Create a token object" user right must not be assigned to any groups or accounts.

AC-6 - High - CCI-002235 - V-278246 - SV-278246r1129778_rule

RMF Control

AC-6

Severity

H

CCI

Version

WN25-UR-000060

Vuln IDs

V-278246

Rule IDs

SV-278246r1129778_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. The "Create a token object" user right allows a process to create an access token. This could be used to provide elevated rights and compromise a system.

Checks: C-82776r1129776_chk

Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups are granted the "Create a token object" user right, this is a finding. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If any SIDs are granted the "SeCreateTokenPrivilege" user right, this is a finding. If an application requires this user right, this is not a finding. Vendor documentation must support the requirement for having the user right. The requirement must be documented with the information system security officer (ISSO). The application account must meet requirements for application account passwords, such as length (WN25-00-000050) and required frequency of changes (WN25-00-000060). Passwords for application accounts with this user right must be protected as highly privileged accounts.

Fix: F-82681r1129777_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Create a token object to be defined but containing no entries (blank).

b

The Windows Server 2025 "Create global objects" user right must only be assigned to Administrators, Service, Local Service, and Network Service.

AC-6 - Medium - CCI-002235 - V-278247 - SV-278247r1130231_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN25-UR-000070

Vuln IDs

V-278247

Rule IDs

SV-278247r1130231_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Create global objects" user right can create objects that are available to all sessions, which could affect processes in other users' sessions.

Checks: C-82777r1130229_chk

Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Create global objects" user right, this is a finding: - Administrators. - Service. - Local Service. - Network Service. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If any SIDs other than the following are granted the "SeCreateGlobalPrivilege" user right, this is a finding: S-1-5-32-544 (Administrators) S-1-5-6 (Service) S-1-5-19 (Local Service) S-1-5-20 (Network Service) If an application requires this user right, this is not a finding. Vendor documentation must support the requirement for having the user right. The requirement must be documented with the information system security officer (ISSO). The application account must meet requirements for application account passwords, such as length (WN25-00-000050) and required frequency of changes (WN25-00-000060).

Fix: F-82682r1130230_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Create global objects to include only the following accounts or groups: - Administrators. - Service. - Local Service. - Network Service.

b

The Windows Server 2025 "Create permanent shared objects" user right must not be assigned to any groups or accounts.

AC-6 - Medium - CCI-002235 - V-278248 - SV-278248r1130232_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN25-UR-000080

Vuln IDs

V-278248

Rule IDs

SV-278248r1130232_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Create permanent shared objects" user right could expose sensitive data by creating shared objects.

Checks: C-82778r1129782_chk

Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups are granted the "Create permanent shared objects" user right, this is a finding. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If any SIDs are granted the "SeCreatePermanentPrivilege" user right, this is a finding.

Fix: F-82683r1129783_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Create permanent shared objects to be defined but containing no entries (blank).

b

The Windows Server 2025 "Create symbolic links" user right must only be assigned to the Administrators group.

AC-6 - Medium - CCI-002235 - V-278249 - SV-278249r1130235_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN25-UR-000090

Vuln IDs

V-278249

Rule IDs

SV-278249r1130235_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Create symbolic links" user right can create pointers to other objects, which could expose the system to attack.

Checks: C-82779r1130233_chk

Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Create symbolic links" user right, this is a finding: - Administrators. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If any SIDs other than the following are granted the "SeCreateSymbolicLinkPrivilege" user right, this is a finding: S-1-5-32-544 (Administrators) Systems that have the Hyper-V role will also have "Virtual Machines" given this user right (this may be displayed as "NT Virtual Machine\Virtual Machines", SID S-1-5-83-0). This is not a finding.

Fix: F-82684r1130234_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Create symbolic links to include only the following accounts or groups: - Administrators. Systems that have the Hyper-V role will also have "Virtual Machines" given this user right. If this needs to be added manually, enter it as "NT Virtual Machine\Virtual Machines".

c

The Windows Server 2025 "Debug programs" user right must only be assigned to the Administrators group.

AC-6 - High - CCI-002235 - V-278250 - SV-278250r1130238_rule

RMF Control

AC-6

Severity

H

CCI

Version

WN25-UR-000100

Vuln IDs

V-278250

Rule IDs

SV-278250r1130238_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Debug programs" user right can attach a debugger to any process or to the kernel, providing complete access to sensitive and critical operating system components. This right is given to Administrators in the default configuration.

Checks: C-82780r1130236_chk

Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Debug programs" user right, this is a finding: - Administrators. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If any SIDs other than the following are granted the "SeDebugPrivilege" user right, this is a finding: S-1-5-32-544 (Administrators) If an application requires this user right, this is not a finding. Vendor documentation must support the requirement for having the user right. The requirement must be documented with the information system security officer (ISSO). The application account must meet requirements for application account passwords, such as length (WN25-00-000050) and required frequency of changes (WN25-00-000060). Passwords for application accounts with this user right must be protected as highly privileged accounts.

Fix: F-82685r1130237_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Debug programs to include only the following accounts or groups: - Administrators.

b

The Windows Server 2025 "Force shutdown from a remote system" user right must only be assigned to the Administrators group.

AC-6 - Medium - CCI-002235 - V-278251 - SV-278251r1130241_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN25-UR-000110

Vuln IDs

V-278251

Rule IDs

SV-278251r1130241_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Force shutdown from a remote system" user right can remotely shut down a system, which could result in a denial of service.

Checks: C-82781r1130239_chk

Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Force shutdown from a remote system" user right, this is a finding: - Administrators. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If any SIDs other than the following are granted the "SeRemoteShutdownPrivilege" user right, this is a finding: S-1-5-32-544 (Administrators)

Fix: F-82686r1130240_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Force shutdown from a remote system to include only the following accounts or groups: - Administrators.

b

The Windows Server 2025 "Generate security audits" user right must only be assigned to Local Service and Network Service.

AC-6 - Medium - CCI-002235 - V-278252 - SV-278252r1130244_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN25-UR-000120

Vuln IDs

V-278252

Rule IDs

SV-278252r1130244_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. The "Generate security audits" user right specifies users and processes that can generate Security Log audit records, which must only be the system service accounts defined.

Checks: C-82782r1130242_chk

Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Generate security audits" user right, this is a finding: - Local Service. - Network Service. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If any SIDs other than the following are granted the "SeAuditPrivilege" user right, this is a finding: S-1-5-19 (Local Service) S-1-5-20 (Network Service) If an application requires this user right, this is not a finding. Vendor documentation must support the requirement for having the user right. The requirement must be documented with the information system security officer (ISSO). The application account must meet requirements for application account passwords, such as length (WN25-00-000050) and required frequency of changes (WN25-00-000060).

Fix: F-82687r1130243_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Generate security audits to include only the following accounts or groups: - Local Service. - Network Service.

b

The Windows Server 2025 "Impersonate a client after authentication" user right must only be assigned to Administrators, Service, Local Service, and Network Service.

AC-6 - Medium - CCI-002235 - V-278253 - SV-278253r1130247_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN25-UR-000130

Vuln IDs

V-278253

Rule IDs

SV-278253r1130247_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. The "Impersonate a client after authentication" user right allows a program to impersonate another user or account to run on their behalf. An attacker could use this to elevate privileges.

Checks: C-82783r1130245_chk

Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Impersonate a client after authentication" user right, this is a finding: - Administrators. - Service. - Local Service. - Network Service. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If any SIDs other than the following are granted the "SeImpersonatePrivilege" user right, this is a finding: S-1-5-32-544 (Administrators) S-1-5-6 (Service) S-1-5-19 (Local Service) S-1-5-20 (Network Service) If an application requires this user right, this is not a finding. Vendor documentation must support the requirement for having the user right. The requirement must be documented with the information system security officer (ISSO). The application account must meet requirements for application account passwords, such as length (WN25-00-000050) and required frequency of changes (WN25-00-000060).

Fix: F-82688r1130246_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Impersonate a client after authentication to include only the following accounts or groups: - Administrators. - Service. - Local Service. - Network Service.

b

The Windows Server 2025 "Increase scheduling priority" user right must only be assigned to the Administrators group.

AC-6 - Medium - CCI-002235 - V-278254 - SV-278254r1130250_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN25-UR-000140

Vuln IDs

V-278254

Rule IDs

SV-278254r1130250_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Increase scheduling priority" user right can change a scheduling priority, causing performance issues or a denial of service.

Checks: C-82784r1130248_chk

Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Increase scheduling priority" user right, this is a finding: - Administrators. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If any SIDs other than the following are granted the "SeIncreaseBasePriorityPrivilege" user right, this is a finding: S-1-5-32-544 (Administrators) If an application requires this user right, this is not a finding. Vendor documentation must support the requirement for having the user right. The requirement must be documented with the information system security officer (ISSO). The application account must meet requirements for application account passwords, such as length (WN25-00-000050) and required frequency of changes (WN25-00-000060).

Fix: F-82689r1130249_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Increase scheduling priority to include only the following accounts or groups: - Administrators.

b

The Windows Server 2025 "Load and unload device drivers" user right must only be assigned to the Administrators group.

AC-6 - Medium - CCI-002235 - V-278255 - SV-278255r1130253_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN25-UR-000150

Vuln IDs

V-278255

Rule IDs

SV-278255r1130253_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. The "Load and unload device drivers" user right allows a user to load device drivers dynamically on a system. This could be used by an attacker to install malicious code.

Checks: C-82785r1130251_chk

Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Load and unload device drivers" user right, this is a finding: - Administrators. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If any SIDs other than the following are granted the "SeLoadDriverPrivilege" user right, this is a finding: S-1-5-32-544 (Administrators)

Fix: F-82690r1130252_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Load and unload device drivers to include only the following accounts or groups: - Administrators.

b

The Windows Server 2025 "Lock pages in memory" user right must not be assigned to any groups or accounts.

AC-6 - Medium - CCI-002235 - V-278256 - SV-278256r1130254_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN25-UR-000160

Vuln IDs

V-278256

Rule IDs

SV-278256r1130254_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. The "Lock pages in memory" user right allows physical memory to be assigned to processes, which could cause performance issues or a denial of service. Satisfies: SRG-OS-000324-GPOS-00125, SRG-OS-000433-GPOS-00193

Checks: C-82786r1129806_chk

Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups are granted the "Lock pages in memory" user right, this is a finding. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If any SIDs are granted the "SeLockMemoryPrivilege" user right, this is a finding. If an application requires this user right, this is not a finding. Vendor documentation must support the requirement for having the user right. The requirement must be documented with the information system security officer (ISSO). The application account must meet requirements for application account passwords, such as length (WN25-00-000050) and required frequency of changes (WN25-00-000060).

Fix: F-82691r1129807_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Lock pages in memory to be defined but containing no entries (blank).

b

The Windows Server 2025 "Manage auditing and security log" user right must only be assigned to the Administrators group.

AU-9 - Medium - CCI-000162 - V-278257 - SV-278257r1130257_rule

RMF Control

AU-9

Severity

M

CCI

Version

WN25-UR-000170

Vuln IDs

V-278257

Rule IDs

SV-278257r1130257_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Manage auditing and security log" user right can manage the security log and change auditing configurations. This could be used to clear evidence of tampering. Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029, SRG-OS-000063-GPOS-00032, SRG-OS-000337-GPOS-00129

Checks: C-82787r1130255_chk

Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Manage auditing and security log" user right, this is a finding: - Administrators. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If any SIDs other than the following are granted the "SeSecurityPrivilege" user right, this is a finding: S-1-5-32-544 (Administrators) If the organization has an Auditors group, the assignment of this group the assignment of this group to the user right is not a finding. If an application requires this user right, this is not a finding. Vendor documentation must support the requirement for having the user right. The requirement must be documented with the information system security officer (ISSO). The application account must meet requirements for application account passwords, such as length (WN25-00-000050) and required frequency of changes (WN25-00-000060).

Fix: F-82692r1130256_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Manage auditing and security log to include only the following accounts or groups: - Administrators.

b

The Windows Server 2025 "Modify firmware environment values" user right must only be assigned to the Administrators group.

AC-6 - Medium - CCI-002235 - V-278258 - SV-278258r1130260_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN25-UR-000180

Vuln IDs

V-278258

Rule IDs

SV-278258r1130260_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Modify firmware environment values" user right can change hardware configuration environment variables. This could result in hardware failures or a denial of service.

Checks: C-82788r1130258_chk

Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Modify firmware environment values" user right, this is a finding: - Administrators. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If any SIDs other than the following are granted the "SeSystemEnvironmentPrivilege" user right, this is a finding: S-1-5-32-544 (Administrators)

Fix: F-82693r1130259_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Modify firmware environment values to include only the following accounts or groups: - Administrators.

b

The Windows Server 2025 "Perform volume maintenance tasks" user right must only be assigned to the Administrators group.

AC-6 - Medium - CCI-002235 - V-278259 - SV-278259r1130263_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN25-UR-000190

Vuln IDs

V-278259

Rule IDs

SV-278259r1130263_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Perform volume maintenance tasks" user right can manage volume and disk configurations. This could be used to delete volumes, resulting in data loss or a denial of service.

Checks: C-82789r1130261_chk

Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Perform volume maintenance tasks" user right, this is a finding: - Administrators. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If any SIDs other than the following are granted the "SeManageVolumePrivilege" user right, this is a finding: S-1-5-32-544 (Administrators)

Fix: F-82694r1130262_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Perform volume maintenance tasks to include only the following accounts or groups: - Administrators.

b

The Windows Server 2025 "Profile single process" user right must only be assigned to the Administrators group.

AC-6 - Medium - CCI-002235 - V-278260 - SV-278260r1130266_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN25-UR-000200

Vuln IDs

V-278260

Rule IDs

SV-278260r1130266_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Profile single process" user right can monitor nonsystem processes performance. An attacker could use this to identify processes to attack.

Checks: C-82790r1130264_chk

Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Profile single process" user right, this is a finding: - Administrators. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If any SIDs other than the following are granted the "SeProfileSingleProcessPrivilege" user right, this is a finding: S-1-5-32-544 (Administrators)

Fix: F-82695r1130265_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Profile single process to include only the following accounts or groups: - Administrators.

b

The Windows Server 2025 "Restore files and directories" user right must only be assigned to the Administrators group.

AC-6 - Medium - CCI-002235 - V-278261 - SV-278261r1130269_rule

RMF Control

AC-6

Severity

M

CCI

Version

WN25-UR-000210

Vuln IDs

V-278261

Rule IDs

SV-278261r1130269_rule

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Restore files and directories" user right can circumvent file and directory permissions and could allow access to sensitive data. It could also be used to overwrite more current data.

Checks: C-82791r1130267_chk

Verify the effective setting in Local Group Policy Editor. Run gpedit.msc. Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups other than the following are granted the "Restore files and directories" user right, this is a finding: - Administrators. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If any SIDs other than the following are granted the "SeRestorePrivilege" user right, this is a finding: S-1-5-32-544 (Administrators) If an application requires this user right, this is not a finding. Vendor documentation must support the requirement for having the user right. The requirement must be documented with the information system security officer (ISSO). The application account must meet requirements for application account passwords, such as length (WN25-00-000050) and required frequency of changes (WN25-00-000060).

Fix: F-82696r1130268_fix

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Restore files and directories to include only the following accounts or groups: - Administrators.

b

The Windows Server 2025 "Take ownership of files or other objects" user right must only be assigned to the Administrators group.

AC-6 - Medium - CCI-002235 - V-278262 - SV-278262r1130272_rule

RMF Control

AC-6

Severity

M

CCI