# stig_rules

vuln_id: V-263607
rule_id: SV-263607r982487_rule
severity: CAT II
cci: CCI-004045
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must require users to be individually authenticated before granting access to the shared accounts or resources.

description:
  <VulnDiscussion>Individual authentication prior to shared group authentication mitigates the risk of using group accounts or authenticators.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the DBMS to require users to be individually authenticated before granting access to the shared accounts or resources.

check_text:
  Verify the DBMS is configured to require users to be individually authenticated before granting access to the shared accounts or resources.

  If the DBMS is not configured to require users to be individually authenticated before granting access to the shared accounts or resources, this is a finding.


vuln_id: V-263608
rule_id: SV-263608r981982_rule
severity: CAT II
cci: CCI-004046
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must implement multifactor authentication for local; network; and/or remote access to privileged accounts; and/or nonprivileged accounts such that one of the factors is provided by a device separate from the system gaining access.

description:
  <VulnDiscussion>The purpose of requiring a device that is separate from the system to which the user is attempting to gain access for one of the factors during multifactor authentication is to reduce the likelihood of compromising authenticators or credentials stored on the system. Adversaries may be able to compromise such authenticators or credentials and subsequently impersonate authorized users. Implementing one of the factors on a separate device (e.g., a hardware token), provides a greater strength of mechanism and an increased level of assurance in the authentication process.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the DBMS to implement multifactor authentication for local; network; and/or remote access to privileged accounts; and/or nonprivileged accounts such that one of the factors is provided by a device separate from the system gaining access.

check_text:
  Verify the DBMS is configured to implement multifactor authentication for local; network; and/or remote access to privileged accounts; and/or nonprivileged accounts such that one of the factors is provided by a device separate from the system gaining access.

  If the DBMS is not configured to implement multifactor authentication for local; network; and/or remote access to privileged accounts; and/or nonprivileged accounts such that one of the factors is provided by a device separate from the system gaining access, this is a finding.


vuln_id: V-263609
rule_id: SV-263609r982489_rule
severity: CAT II
cci: CCI-004047
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must implement multifactor authentication for local; network; and/or remote access to privileged accounts; and/or nonprivileged accounts such that the device meets organization-defined strength of mechanism requirements.

description:
  <VulnDiscussion>The purpose of requiring a device that is separate from the system to which the user is attempting to gain access for one of the factors during multifactor authentication is to reduce the likelihood of compromising authenticators or credentials stored on the system. Adversaries may be able to compromise such authenticators or credentials and subsequently impersonate authorized users. Implementing one of the factors on a separate device (e.g., a hardware token), provides a greater strength of mechanism and an increased level of assurance in the authentication process.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the DBMS to implement multifactor authentication for local; network; and/or remote access to privileged accounts; and/or nonprivileged accounts such that the device meets organization-defined strength of mechanism requirements.

check_text:
  Verify the DBMS is configured to implement multifactor authentication for local; network; and/or remote access to privileged accounts; and/or nonprivileged accounts such that the device meets organization-defined strength of mechanism requirements.

  If the DBMS is not configured to implement multifactor authentication for local; network; and/or remote access to privileged accounts; and/or nonprivileged accounts such that the device meets organization-defined strength of mechanism requirements, this is a finding.


vuln_id: V-263610
rule_id: SV-263610r981988_rule
severity: CAT II
cci: CCI-004058
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must, for password-based authentication, maintain a list of commonly used, expected, or compromised passwords on an organization-defined frequency.

description:
  <VulnDiscussion>Password-based authentication applies to passwords regardless of whether they are used in single-factor or multifactor authentication. Long passwords or passphrases are preferable over shorter passwords. Enforced composition rules provide marginal security benefits while decreasing usability. However, organizations may choose to establish certain rules for password generation (e.g., minimum character length for long passwords) under certain circumstances and can enforce this requirement in IA-5(1)(h). Account recovery can occur, for example, in situations when a password is forgotten. Cryptographically protected passwords include salted one-way cryptographic hashes of passwords. The list of commonly used, compromised, or expected passwords includes passwords obtained from previous breach corpuses, dictionary words, and repetitive or sequential characters. The list includes context-specific words, such as the name of the service, username, and derivatives thereof.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the DBMS to maintain a list of commonly used, expected, or compromised passwords on an organization-defined frequency.

check_text:
  Verify the DBMS is configured to maintain a list of commonly used, expected, or compromised passwords on an organization-defined frequency.

  If the DBMS is not configured to maintain a list of commonly used, expected, or compromised passwords on an organization-defined frequency, this is a finding.


vuln_id: V-263611
rule_id: SV-263611r982491_rule
severity: CAT II
fix_text: Configure the DBMS to update the list of passwords on an organization-defined frequency.
cci: CCI-004059
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must, for password-based authentication, update the list of passwords on an organization-defined frequency.

description:
  <VulnDiscussion>Password-based authentication applies to passwords regardless of whether they are used in single-factor or multifactor authentication. Long passwords or passphrases are preferable over shorter passwords. Enforced composition rules provide marginal security benefits while decreasing usability. However, organizations may choose to establish certain rules for password generation (e.g., minimum character length for long passwords) under certain circumstances and can enforce this requirement in IA-5(1)(h). Account recovery can occur, for example, in situations when a password is forgotten. Cryptographically protected passwords include salted one-way cryptographic hashes of passwords. The list of commonly used, compromised, or expected passwords includes passwords obtained from previous breach corpuses, dictionary words, and repetitive or sequential characters. The list includes context-specific words, such as the name of the service, username, and derivatives thereof.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

check_text:
  Verify the DBMS is configured to update the list of passwords on an organization-defined frequency.

  If the DBMS is not configured to update the list of passwords on an organization-defined frequency, this is a finding.


vuln_id: V-263612
rule_id: SV-263612r982493_rule
severity: CAT II
cci: CCI-004060
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must, for password-based authentication, update the list of passwords when organizational passwords are suspected to have been compromised directly or indirectly.

description:
  <VulnDiscussion>Password-based authentication applies to passwords regardless of whether they are used in single-factor or multifactor authentication. Long passwords or passphrases are preferable over shorter passwords. Enforced composition rules provide marginal security benefits while decreasing usability. However, organizations may choose to establish certain rules for password generation (e.g., minimum character length for long passwords) under certain circumstances and can enforce this requirement in IA-5(1)(h). Account recovery can occur, for example, in situations when a password is forgotten. Cryptographically protected passwords include salted one-way cryptographic hashes of passwords. The list of commonly used, compromised, or expected passwords includes passwords obtained from previous breach corpuses, dictionary words, and repetitive or sequential characters. The list includes context-specific words, such as the name of the service, username, and derivatives thereof.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the DBMS to update the list of passwords when organizational passwords are suspected to have been compromised directly or indirectly.

check_text:
  Verify the DBMS is configured to update the list of passwords when organizational passwords are suspected to have been compromised directly or indirectly.

  If the DBMS is not configured to update the list of passwords when organizational passwords are suspected to have been compromised directly or indirectly, this is a finding.


vuln_id: V-263613
rule_id: SV-263613r982495_rule
severity: CAT II
cci: CCI-004061
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must, for password-based authentication, verify that when users create or update passwords, the passwords are not found on the list of commonly-used, expected, or compromised passwords in IA-5 (1) (a).

description:
[cell repeats an earlier one in this file: 1359 characters]

fix_text:
  Configure the DBMS to verify when users create or update passwords, that the passwords are not found on the list of commonly-used, expected, or compromised passwords in IA-5 (1) (a).

check_text:
  Verify the DBMS is configured to verify when users create or update passwords, that the passwords are not found on the list of commonly-used, expected, or compromised passwords in IA-5 (1) (a).

  If the DBMS is not configured to verify when users create or update passwords, that the passwords are not found on the list of commonly-used, expected, or compromised passwords in IA-5 (1) (a), this is a finding.


vuln_id: V-263614
rule_id: SV-263614r982497_rule
severity: CAT II
fix_text: Configure the DBMS to require immediate selection of a new password upon account recovery.
cci: CCI-004063
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must, for password-based authentication, require immediate selection of a new password upon account recovery.

description:
[cell repeats an earlier one in this file: 1359 characters]

check_text:
  Verify the DBMS is configured to require immediate selection of a new password upon account recovery.

  If the DBMS is not configured to require immediate selection of a new password upon account recovery, this is a finding.


vuln_id: V-263615
rule_id: SV-263615r982499_rule
severity: CAT II
cci: CCI-004064
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must, for password-based authentication, allow user selection of long passwords and passphrases, including spaces and all printable characters.

description:
[cell repeats an earlier one in this file: 1359 characters]

fix_text:
  Configure the DBMS to allow user selection of long passwords and passphrases, including spaces and all printable characters.

check_text:
  Verify the DBMS is configured to allow user selection of long passwords and passphrases, including spaces and all printable characters.

  If the DBMS is not configured to allow user selection of long passwords and passphrases, including spaces and all printable characters, this is a finding.


vuln_id: V-263616
rule_id: SV-263616r982501_rule
severity: CAT II
cci: CCI-004065
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must, for password-based authentication, employ automated tools to assist the user in selecting strong password authenticators.

description:
[cell repeats an earlier one in this file: 1359 characters]

fix_text:
  Configure the DBMS to employ automated tools to assist the user in selecting strong password authenticators.

check_text:
  Verify the DBMS is configured to employ automated tools to assist the user in selecting strong password authenticators.

  If the DBMS is not configured to employ automated tools to assist the user in selecting strong password authenticators, this is a finding.


vuln_id: V-263617
rule_id: SV-263617r982009_rule
severity: CAT II
cci: CCI-004068
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must, for public key-based authentication, implement a local cache of revocation data to support path discovery and validation.

description:
  <VulnDiscussion>Public key cryptography is a valid authentication mechanism for individuals, machines, and devices. For PKI solutions, status information for certification paths includes certificate revocation lists or certificate status protocol responses. For PIV cards, certificate validation involves the construction and verification of a certification path to the Common Policy Root trust anchor, which includes certificate policy processing. Implementing a local cache of revocation data to support path discovery and validation also supports system availability in situations where organizations are unable to access revocation information via the network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the DBMS to implement a local cache of revocation data to support path discovery and validation.

check_text:
  Verify the DBMS is configured to implement a local cache of revocation data to support path discovery and validation.

  If the DBMS is not configured to implement a local cache of revocation data to support path discovery and validation, this is a finding.


vuln_id: V-263618
rule_id: SV-263618r982503_rule
severity: CAT II
cci: CCI-004192
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must protect nonlocal maintenance sessions by separating the maintenance session from other network sessions with the system by logically separated communications paths.

description:
  <VulnDiscussion>Nonlocal maintenance and diagnostic activities are conducted by individuals who communicate through either an external or internal network. Communications paths can be logically separated using encryption.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the DBMS to protect nonlocal maintenance sessions by separating the maintenance session from other network sessions with the system by logically separated communications paths.

check_text:
  Verify the DBMS is configured to protect nonlocal maintenance sessions by separating the maintenance session from other network sessions with the system by logically separated communications paths.

  If the DBMS is not configured to protect nonlocal maintenance sessions by separating the maintenance session from other network sessions with the system by logically separated communications paths, this is a finding.


vuln_id: V-263619
rule_id: SV-263619r982505_rule
severity: CAT II
cci: CCI-004909
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must include only approved trust anchors in trust stores or certificate stores managed by the organization.

description:
  <VulnDiscussion>Public key infrastructure (PKI) certificates are certificates with visibility external to organizational systems and certificates related to the internal operations of systems, such as application-specific time services. In cryptographic systems with a hierarchical structure, a trust anchor is an authoritative source (i.e., a certificate authority) for which trust is assumed and not derived. A root certificate for a PKI system is an example of a trust anchor. A trust store or certificate store maintains a list of trusted root certificates.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the DBMS to include only approved trust anchors in trust stores or certificate stores managed by the organization.

check_text:
  Verify the DBMS is configured to include only approved trust anchors in trust stores or certificate stores managed by the organization.

  If the DBMS is not configured to include only approved trust anchors in trust stores or certificate stores managed by the organization, this is a finding.


vuln_id: V-263620
rule_id: SV-263620r982507_rule
severity: CAT II
cci: CCI-004910
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must provide protected storage for cryptographic keys with organization-defined safeguards and/or hardware protected key store.

description:
  <VulnDiscussion>A Trusted Platform Module (TPM) is an example of a hardware-protected data store that can be used to protect cryptographic keys.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the DBMS to provide protected storage for cryptographic keys with organization-defined safeguards and/or hardware protected key store.

check_text:
  Verify the DBMS is configured to provide protected storage for cryptographic keys with organization-defined safeguards and/or hardware protected key store.

  If the DBMS is not configured to provide protected storage for cryptographic keys with organization-defined safeguards and/or hardware protected key store, this is a finding.


vuln_id: V-263621
rule_id: SV-263621r982509_rule
severity: CAT II
title: The DBMS must synchronize system clocks within and between systems or system components.
fix_text: Configure the DBMS to synchronize system clocks within and between systems or system components.
cci: CCI-004922
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>Time synchronization of system clocks is essential for the correct execution of many system services, including identification and authentication processes that involve certificates and time-of-day restrictions as part of access control. Denial of service or failure to deny expired credentials may result without properly synchronized clocks within and between systems and system components. Time is commonly expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC. The granularity of time measurements refers to the degree of synchronization between system clocks and reference clocks, such as clocks synchronizing within hundreds of milliseconds or tens of milliseconds. Organizations may define different time granularities for system components. Time service can be critical to other security capabilities such as access control and identification and authentication depending on the nature of the mechanisms used to support the capabilities.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

check_text:
  Verify the DBMS is configured to synchronize system clocks within and between systems or system components.

  If the DBMS is not configured to synchronize system clocks within and between systems or system components, this is a finding.


vuln_id: V-263622
rule_id: SV-263622r982511_rule
severity: CAT II
cci: CCI-004923
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must compare the internal system clocks on an organization-defined frequency with organization-defined authoritative time source.

description:
  <VulnDiscussion>Synchronization of internal system clocks with an authoritative source provides uniformity of time stamps for systems with multiple system clocks and systems connected over a network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the DBMS to compare the internal system clocks on an organization-defined frequency with organization-defined authoritative time source.

check_text:
  Verify the DBMS is configured to compare the internal system clocks on an organization-defined frequency with organization-defined authoritative time source.

  If the DBMS is not configured to compare the internal system clocks on an organization-defined frequency with organization-defined authoritative time source, this is a finding.


vuln_id: V-265854
rule_id: SV-265854r999381_rule
severity: CAT I
title: DBMS products must be a version supported by the vendor.
fix_text: Upgrade unsupported DBMS or unsupported components to a supported version of the product.
cci: CCI-003376
deprecated_at: 2026-03-06 18:06:20
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 17:52:29
description:
  <VulnDiscussion>Unsupported commercial and database systems should not be used because fixes to newly identified bugs will not be implemented by the vendor. The lack of support can result in potential vulnerabilities.
  Systems at unsupported servicing levels or releases will not receive security updates for new vulnerabilities, which leaves them subject to exploitation.

  When maintenance updates and patches are no longer available, the database software is no longer considered supported and should be upgraded or decommissioned.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

check_text:
  (DBMS Product, Version) is no longer supported by the vendor. If the system is running (DBMS Product, Version), this is a finding.


vuln_id: V-278969
rule_id: SV-278969r1137670_rule
severity: CAT I
title: The DBMS must be a version supported by the vendor.
fix_text: Upgrade or install a version of the DBMS supported by the vendor.
cci: CCI-003376
created_at: 2026-03-06 18:06:20
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>Unsupported software and systems should not be used because fixes to newly identified bugs will not be implemented by the vendor. The lack of support can result in potential vulnerabilities.

  Software and systems at unsupported servicing levels or releases will not receive security updates for new vulnerabilities, which leaves them subject to exploitation.

  When maintenance updates and patches are no longer available, software is no longer considered supported and should be upgraded or decommissioned.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

check_text:
  Verify the DBMS is  a version supported by the vendor.

  If the DBMS is not a version supported by the vendor, this is a finding.


vuln_id: V-254238
rule_id: xccdf_mil.disa.stig_rule_SV-254238r991589_rule
severity: CAT II
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 users with Administrative privileges must have separate accounts for administrative duties and normal operational tasks.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254239
rule_id: xccdf_mil.disa.stig_rule_SV-254239r1153440_rule
severity: CAT II
cci: CCI-004066,CCI-000199
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 passwords for the built-in Administrator account must be changed at least every 60 days.

description:
  <VulnDiscussion>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.

  For domain-joined systems, Windows LAPS must be used to change the built-in Administrator account password.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Change the enabled local Administrator account password at least every 60 days. For domain-joined systems, Windows LAPS must be used to change the built-in Administrator account password.

  More information is available at:
  https://techcommunity.microsoft.com/t5/windows-it-pro-blog/by-popular-demand-windows-laps-available-now/ba-p/3788747
  https://learn.microsoft.com/en-us/windows-server/identity/laps/laps-overview#windows-laps-supported-platforms-and-azure-ad-laps-preview-status


vuln_id: V-254240
rule_id: xccdf_mil.disa.stig_rule_SV-254240r991589_rule
severity: CAT I
cci: CCI-000366,CCI-001312
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 administrative accounts must not be used with applications that access the internet, such as web browsers, or with potential internet sources, such as email.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254241
rule_id: xccdf_mil.disa.stig_rule_SV-254241r991589_rule
severity: CAT II
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 members of the Backup Operators group must have separate accounts for backup duties and normal operational tasks.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254242
rule_id: xccdf_mil.disa.stig_rule_SV-254242r1051087_rule
severity: CAT II
cci: CCI-004066,CCI-000205
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 manually managed application account passwords must be at least 14 characters in length.

description:
  <VulnDiscussion>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 14 characters in length.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254243
rule_id: xccdf_mil.disa.stig_rule_SV-254243r991589_rule
severity: CAT II
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 manually managed application account passwords must be changed at least annually or when a system administrator with knowledge of the password leaves the organization.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254245
rule_id: xccdf_mil.disa.stig_rule_SV-254245r958808_rule
severity: CAT II
cci: CCI-001774
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs.

description:
  <VulnDiscussion>Using an allowlist 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 allowlisting.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure an application allowlisting program to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs.

  Configuration of allowlisting applications will vary by the program. AppLocker is an allowlisting application built 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 at the following link:

  https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-application-control/applocker/applocker-policies-deployment-guide


vuln_id: V-254246
rule_id: xccdf_mil.disa.stig_rule_SV-254246r991589_rule
severity: CAT II
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 domain-joined systems must have a Trusted Platform Module (TPM) enabled and ready for use.

description:
  <VulnDiscussion>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 in order 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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254247
rule_id: xccdf_mil.disa.stig_rule_SV-254247r991589_rule
severity: CAT II
title: Windows Server 2022 must be maintained at a supported servicing level.
fix_text: Update the system to a Version 21H2 (Build 20348.xxx) or greater.
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>


vuln_id: V-254248
rule_id: xccdf_mil.disa.stig_rule_SV-254248r991589_rule
severity: CAT II
title: Windows Server 2022 must use an antivirus program.
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254251
rule_id: xccdf_mil.disa.stig_rule_SV-254251r958702_rule
severity: CAT II
cci: CCI-002165
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 permissions for the system drive root directory (usually C:\) must conform to minimum requirements.

description:
  <VulnDiscussion>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" (WN22-SO-000240).

  Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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" (WN22-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


vuln_id: V-254252
rule_id: xccdf_mil.disa.stig_rule_SV-254252r958702_rule
severity: CAT II
title: Windows Server 2022 permissions for program file directories must conform to minimum requirements.
cci: CCI-002165
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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" (WN22-SO-000240).

  Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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" (WN22-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


vuln_id: V-254253
rule_id: xccdf_mil.disa.stig_rule_SV-254253r958702_rule
severity: CAT II
cci: CCI-002165
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 permissions for the Windows installation directory must conform to minimum requirements.

description:
  <VulnDiscussion>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" (WN22-SO-000240).

  Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Maintain the default file ACLs and configure the Security Option "Network access: Let Everyone permissions apply to anonymous users" to "Disabled" (WN22-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


vuln_id: V-254254
rule_id: xccdf_mil.disa.stig_rule_SV-254254r1153443_rule
severity: CAT II
cci: CCI-002235
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 default permissions for the HKEY_LOCAL_MACHINE registry hive must be maintained.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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
  Authenticated 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 also given Read permission to the SOFTWARE and SYSTEM registry keys in Windows Server 2022 to the following SID:
  S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4053264122-3456934681


vuln_id: V-254255
rule_id: xccdf_mil.disa.stig_rule_SV-254255r1137691_rule
severity: CAT III
cci: CCI-000213
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 nonadministrative accounts or groups must only have print permissions on printer shares.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254257
rule_id: xccdf_mil.disa.stig_rule_SV-254257r958482_rule
severity: CAT II
title: Windows Server 2022 accounts must require passwords.
cci: CCI-000764
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254258
rule_id: xccdf_mil.disa.stig_rule_SV-254258r1051089_rule
severity: CAT II
title: Windows Server 2022 passwords must be configured to expire.
cci: CCI-004066,CCI-000199
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>Passwords that do not expire or are reused increase the exposure of a password with greater probability of being discovered or cracked.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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).


vuln_id: V-254260
rule_id: xccdf_mil.disa.stig_rule_SV-254260r1137695_rule
severity: CAT II
title: Windows Server 2022 nonsystem-created file shares must limit access to groups that require it.
cci: CCI-001090
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254262
rule_id: xccdf_mil.disa.stig_rule_SV-254262r958552_rule
severity: CAT I
cci: CCI-001199,CCI-002475,CCI-002476
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 systems requiring data at rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254263
rule_id: xccdf_mil.disa.stig_rule_SV-254263r958912_rule
severity: CAT II
cci: CCI-002420,CCI-002422
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 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.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254265
rule_id: xccdf_mil.disa.stig_rule_SV-254265r991589_rule
severity: CAT II
title: Windows Server 2022 must have a host-based firewall installed and enabled.
fix_text: Install and enable a host-based firewall on the system.
cci: CCI-000366,CCI-002080
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>


vuln_id: V-254266
rule_id: xccdf_mil.disa.stig_rule_SV-254266r1000154_rule
severity: CAT II
fix_text: Install a DOD-approved ESS software and ensure it is operating continuously.
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must employ automated mechanisms to determine the state of system components with regard to flaw remediation using the following frequency: continuously, where Endpoint Security Solution (ESS) is used; 30 days, for any additional internal network scans not covered by ESS; and annually, for external scans by Computer Network Defense Service Provider (CNDSP).

description:
  <VulnDiscussion>Without the use of automated mechanisms to scan for security flaws on a continuous and/or periodic basis, the operating system or other system components may remain vulnerable to the exploits presented by undetected software flaws. The operating system may have an integrated solution incorporating continuous scanning using ESS and periodic scanning using other tools.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>


vuln_id: V-254267
rule_id: xccdf_mil.disa.stig_rule_SV-254267r958364_rule
severity: CAT II
title: Windows Server 2022 must automatically remove or disable temporary user accounts after 72 hours.
cci: CCI-000016
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254268
rule_id: xccdf_mil.disa.stig_rule_SV-254268r958508_rule
severity: CAT II
cci: CCI-001682
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must automatically remove or disable emergency accounts after the crisis is resolved or within 72 hours.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254270
rule_id: xccdf_mil.disa.stig_rule_SV-254270r958480_rule
severity: CAT II
cci: CCI-000382
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must not have the Microsoft FTP service installed unless required by the organization.

description:
  <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254276
rule_id: xccdf_mil.disa.stig_rule_SV-254276r958478_rule
severity: CAT II
cci: CCI-000381
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must have the Server Message Block (SMB) v1 protocol disabled on the SMB server.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254277
rule_id: xccdf_mil.disa.stig_rule_SV-254277r958478_rule
severity: CAT II
cci: CCI-000381
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must have the Server Message Block (SMB) v1 protocol disabled on the SMB client.

description:
[cell repeats an earlier one in this file: 581 characters]

fix_text:
  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.


vuln_id: V-254278
rule_id: xccdf_mil.disa.stig_rule_SV-254278r958478_rule
severity: CAT II
title: Windows Server 2022 must not have Windows PowerShell 2.0 installed.
cci: CCI-000381
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254281
rule_id: xccdf_mil.disa.stig_rule_SV-254281r1051090_rule
severity: CAT III
title: The Windows Server 2022 time service must synchronize with an appropriate DOD time source.
cci: CCI-004923,CCI-001891
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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 1 time servers, identified at https://www.cnmoc.usff.navy.mil/Our-Commands/United-States-Naval-Observatory/Precise-Time-Department/Network-Time-Protocol-NTP/. Time synchronization will occur through a hierarchy of time servers down to the local level. Clients and lower-level servers will synchronize with an authorized time server in the hierarchy.


vuln_id: V-254282
rule_id: xccdf_mil.disa.stig_rule_SV-254282r991589_rule
severity: CAT II
title: Windows Server 2022 must have orphaned security identifiers (SIDs) removed from user rights.
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254283
rule_id: xccdf_mil.disa.stig_rule_SV-254283r991589_rule
severity: CAT II
fix_text: Configure UEFI firmware to run in "UEFI" mode, not "Legacy BIOS" mode.
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 systems must have Unified Extensible Firmware Interface (UEFI) firmware and be configured to run in UEFI mode, not Legacy BIOS.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>


vuln_id: V-254284
rule_id: xccdf_mil.disa.stig_rule_SV-254284r991589_rule
severity: CAT II
title: Windows Server 2022 must have Secure Boot enabled.
fix_text: Enable Secure Boot in the system firmware.
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>


vuln_id: V-254285
rule_id: xccdf_mil.disa.stig_rule_SV-254285r958736_rule
severity: CAT II
title: Windows Server 2022 account lockout duration must be configured to 15 minutes or greater.
cci: CCI-002238
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>The account lockout feature, when enabled, prevents brute-force password attacks on the system. This parameter specifies the period of time that an account will remain locked after the specified number of failed logon attempts.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy >> Account lockout duration to "15" minutes or greater.

  A value of "0" is also acceptable, requiring an administrator to unlock the account.


vuln_id: V-254286
rule_id: xccdf_mil.disa.stig_rule_SV-254286r958388_rule
severity: CAT II
title: Windows Server 2022 must have the number of allowed bad logon attempts configured to three or less.
cci: CCI-000044
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254287
rule_id: xccdf_mil.disa.stig_rule_SV-254287r958388_rule
severity: CAT II
cci: CCI-000044
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must have the period of time before the bad logon counter is reset configured to 15 minutes or greater.

description:
  <VulnDiscussion>The account lockout feature, when enabled, prevents brute-force password attacks on the system. This parameter specifies the period of time that must pass after failed logon attempts before the counter is reset to "0". The smaller this value is, the less effective the account lockout feature will be in protecting the local system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254288
rule_id: xccdf_mil.disa.stig_rule_SV-254288r1000156_rule
severity: CAT II
title: Windows Server 2022 password history must be configured to 24 passwords remembered.
cci: CCI-004061
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254289
rule_id: xccdf_mil.disa.stig_rule_SV-254289r1051091_rule
severity: CAT II
title: Windows Server 2022 maximum password age must be configured to 60 days or less.
cci: CCI-004066,CCI-000199
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254290
rule_id: xccdf_mil.disa.stig_rule_SV-254290r1051092_rule
severity: CAT II
title: Windows Server 2022 minimum password age must be configured to at least one day.
cci: CCI-004066,CCI-000198
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254292
rule_id: xccdf_mil.disa.stig_rule_SV-254292r1051094_rule
severity: CAT II
title: Windows Server 2022 must have the built-in Windows password complexity policy enabled.
cci: CCI-004066,CCI-000192,CCI-000193,CCI-000194,CCI-001619
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254293
rule_id: xccdf_mil.disa.stig_rule_SV-254293r1051095_rule
severity: CAT I
title: Windows Server 2022 reversible password encryption must be disabled.
cci: CCI-004062,CCI-000196
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254294
rule_id: xccdf_mil.disa.stig_rule_SV-254294r958754_rule
severity: CAT II
cci: CCI-001851
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 audit records must be backed up to a different system or media than the system being audited.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254295
rule_id: xccdf_mil.disa.stig_rule_SV-254295r959008_rule
severity: CAT II
cci: CCI-001851
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must, at a minimum, offload audit records of interconnected systems in real time and offload standalone or nondomain-joined systems weekly.

description:
  <VulnDiscussion>Protection of log data includes assuring the log data is not accidentally lost or deleted. Audit information stored in one location is vulnerable to accidental or incidental deletion or alteration.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254296
rule_id: xccdf_mil.disa.stig_rule_SV-254296r958434_rule
severity: CAT II
cci: CCI-000162,CCI-000163,CCI-000164
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 permissions for the Application event log must prevent access by nonprivileged accounts.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254297
rule_id: xccdf_mil.disa.stig_rule_SV-254297r958434_rule
severity: CAT II
cci: CCI-000162,CCI-000163,CCI-000164
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 permissions for the Security event log must prevent access by nonprivileged accounts.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254298
rule_id: xccdf_mil.disa.stig_rule_SV-254298r958434_rule
severity: CAT II
cci: CCI-000162,CCI-000163,CCI-000164
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 permissions for the System event log must prevent access by nonprivileged accounts.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254299
rule_id: xccdf_mil.disa.stig_rule_SV-254299r991558_rule
severity: CAT II
title: Windows Server 2022 Event Viewer must be protected from unauthorized modification and deletion.
cci: CCI-001494,CCI-001495
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254300
rule_id: xccdf_mil.disa.stig_rule_SV-254300r991578_rule
severity: CAT II
title: Windows Server 2022 must be configured to audit Account Logon - Credential Validation successes.
cci: CCI-000172
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254301
rule_id: xccdf_mil.disa.stig_rule_SV-254301r991578_rule
severity: CAT II
title: Windows Server 2022 must be configured to audit Account Logon - Credential Validation failures.
cci: CCI-000172
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
[cell repeats an earlier one in this file: 928 characters]

fix_text:
  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.


vuln_id: V-254302
rule_id: xccdf_mil.disa.stig_rule_SV-254302r958732_rule
severity: CAT II
cci: CCI-000172,CCI-002234
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must be configured to audit Account Management - Other Account Management Events successes.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254303
rule_id: xccdf_mil.disa.stig_rule_SV-254303r958368_rule
severity: CAT II
cci: CCI-000018,CCI-000172,CCI-001403,CCI-001404,CCI-001405,CCI-002130
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must be configured to audit Account Management - Security Group Management successes.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254304
rule_id: xccdf_mil.disa.stig_rule_SV-254304r958368_rule
severity: CAT II
cci: CCI-000018,CCI-000172,CCI-001403,CCI-001404,CCI-001405,CCI-002130
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must be configured to audit Account Management - User Account Management successes.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254305
rule_id: xccdf_mil.disa.stig_rule_SV-254305r958368_rule
severity: CAT II
cci: CCI-000018,CCI-000172,CCI-001403,CCI-001404,CCI-001405,CCI-002130
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must be configured to audit Account Management - User Account Management failures.

description:
[cell repeats an earlier one in this file: 1114 characters]

fix_text:
  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.


vuln_id: V-254306
rule_id: xccdf_mil.disa.stig_rule_SV-254306r991583_rule
severity: CAT II
title: Windows Server 2022 must be configured to audit Detailed Tracking - Plug and Play Events successes.
cci: CCI-000172
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254307
rule_id: xccdf_mil.disa.stig_rule_SV-254307r958732_rule
severity: CAT II
title: Windows Server 2022 must be configured to audit Detailed Tracking - Process Creation successes.
cci: CCI-000172,CCI-002234
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254309
rule_id: xccdf_mil.disa.stig_rule_SV-254309r991552_rule
severity: CAT II
title: Windows Server 2022 must be configured to audit Logon/Logoff - Account Lockout failures.
cci: CCI-000172,CCI-001404
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254310
rule_id: xccdf_mil.disa.stig_rule_SV-254310r991578_rule
severity: CAT II
title: Windows Server 2022 must be configured to audit Logon/Logoff - Group Membership successes.
cci: CCI-000172
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254311
rule_id: xccdf_mil.disa.stig_rule_SV-254311r991581_rule
severity: CAT II
title: Windows Server 2022 must be configured to audit logoff successes.
cci: CCI-000172
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254312
rule_id: xccdf_mil.disa.stig_rule_SV-254312r958406_rule
severity: CAT II
title: Windows Server 2022 must be configured to audit logon successes.
cci: CCI-000067,CCI-000172
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254313
rule_id: xccdf_mil.disa.stig_rule_SV-254313r958406_rule
severity: CAT II
title: Windows Server 2022 must be configured to audit logon failures.
cci: CCI-000067,CCI-000172
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
[cell repeats an earlier one in this file: 1127 characters]

fix_text:
  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.


vuln_id: V-254314
rule_id: xccdf_mil.disa.stig_rule_SV-254314r991578_rule
severity: CAT II
title: Windows Server 2022 must be configured to audit Logon/Logoff - Special Logon successes.
cci: CCI-000172
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254315
rule_id: xccdf_mil.disa.stig_rule_SV-254315r991578_rule
severity: CAT II
cci: CCI-000172
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must be configured to audit Object Access - Other Object Access Events successes.

description:
[cell repeats an earlier one in this file: 937 characters]

fix_text:
  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.


vuln_id: V-254316
rule_id: xccdf_mil.disa.stig_rule_SV-254316r991578_rule
severity: CAT II
cci: CCI-000172
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must be configured to audit Object Access - Other Object Access Events failures.

description:
[cell repeats an earlier one in this file: 937 characters]

fix_text:
  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.


vuln_id: V-254317
rule_id: xccdf_mil.disa.stig_rule_SV-254317r991583_rule
severity: CAT II
title: Windows Server 2022 must be configured to audit Object Access - Removable Storage successes.
cci: CCI-000172
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254318
rule_id: xccdf_mil.disa.stig_rule_SV-254318r991583_rule
severity: CAT II
title: Windows Server 2022 must be configured to audit Object Access - Removable Storage failures.
cci: CCI-000172
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
[cell repeats an earlier one in this file: 964 characters]

fix_text:
  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.


vuln_id: V-254319
rule_id: xccdf_mil.disa.stig_rule_SV-254319r958732_rule
severity: CAT II
title: Windows Server 2022 must be configured to audit Policy Change - Audit Policy Change successes.
cci: CCI-000172,CCI-002234
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254320
rule_id: xccdf_mil.disa.stig_rule_SV-254320r958732_rule
severity: CAT II
title: Windows Server 2022 must be configured to audit Policy Change - Audit Policy Change failures.
cci: CCI-000172,CCI-002234
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
[cell repeats an earlier one in this file: 1008 characters]

fix_text:
  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.


vuln_id: V-254321
rule_id: xccdf_mil.disa.stig_rule_SV-254321r958732_rule
severity: CAT II
cci: CCI-000172,CCI-002234
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must be configured to audit Policy Change - Authentication Policy Change successes.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254322
rule_id: xccdf_mil.disa.stig_rule_SV-254322r958732_rule
severity: CAT II
cci: CCI-000172,CCI-002234
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must be configured to audit Policy Change - Authorization Policy Change successes.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254325
rule_id: xccdf_mil.disa.stig_rule_SV-254325r958732_rule
severity: CAT II
title: Windows Server 2022 must be configured to audit System - IPsec Driver successes.
cci: CCI-000172,CCI-002234
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254326
rule_id: xccdf_mil.disa.stig_rule_SV-254326r958732_rule
severity: CAT II
title: Windows Server 2022 must be configured to audit System - IPsec Driver failures.
cci: CCI-000172,CCI-002234
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
[cell repeats an earlier one in this file: 1019 characters]

fix_text:
  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.


vuln_id: V-254327
rule_id: xccdf_mil.disa.stig_rule_SV-254327r958732_rule
severity: CAT II
title: Windows Server 2022 must be configured to audit System - Other System Events successes.
cci: CCI-000172,CCI-002234
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254328
rule_id: xccdf_mil.disa.stig_rule_SV-254328r958732_rule
severity: CAT II
title: Windows Server 2022 must be configured to audit System - Other System Events failures.
cci: CCI-000172,CCI-002234
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
[cell repeats an earlier one in this file: 1057 characters]

fix_text:
  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.


vuln_id: V-254329
rule_id: xccdf_mil.disa.stig_rule_SV-254329r958732_rule
severity: CAT II
title: Windows Server 2022 must be configured to audit System - Security State Change successes.
cci: CCI-000172,CCI-002234
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254330
rule_id: xccdf_mil.disa.stig_rule_SV-254330r958732_rule
severity: CAT II
title: Windows Server 2022 must be configured to audit System - Security System Extension successes.
cci: CCI-000172,CCI-002234
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254331
rule_id: xccdf_mil.disa.stig_rule_SV-254331r958732_rule
severity: CAT II
title: Windows Server 2022 must be configured to audit System - System Integrity successes.
cci: CCI-000172,CCI-002234
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254332
rule_id: xccdf_mil.disa.stig_rule_SV-254332r958732_rule
severity: CAT II
title: Windows Server 2022 must be configured to audit System - System Integrity failures.
cci: CCI-000172,CCI-002234
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
[cell repeats an earlier one in this file: 1031 characters]

fix_text:
  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.


vuln_id: V-254333
rule_id: xccdf_mil.disa.stig_rule_SV-254333r958478_rule
severity: CAT II
title: Windows Server 2022 must prevent the display of slide shows on the lock screen.
cci: CCI-000381
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>Slide shows that are displayed on the lock screen could display sensitive information to unauthorized personnel. Turning off this feature will limit access to the information to a logged-on user.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254334
rule_id: xccdf_mil.disa.stig_rule_SV-254334r958478_rule
severity: CAT II
title: Windows Server 2022 must have WDigest Authentication disabled.
cci: CCI-000381
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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 2022. This setting ensures this is enforced.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254335
rule_id: xccdf_mil.disa.stig_rule_SV-254335r991589_rule
severity: CAT III
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 Internet Protocol version 6 (IPv6) source routing must be configured to the highest protection level to prevent IP source routing.

description:
  <VulnDiscussion>Configuring the system to disable IPv6 source routing protects against spoofing.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254336
rule_id: xccdf_mil.disa.stig_rule_SV-254336r991589_rule
severity: CAT III
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 source routing must be configured to the highest protection level to prevent Internet Protocol (IP) source routing.

description:
  <VulnDiscussion>Configuring the system to disable IP source routing protects against spoofing.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254337
rule_id: xccdf_mil.disa.stig_rule_SV-254337r991589_rule
severity: CAT III
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must be configured to prevent Internet Control Message Protocol (ICMP) redirects from overriding Open Shortest Path First (OSPF)-generated routes.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254338
rule_id: xccdf_mil.disa.stig_rule_SV-254338r958902_rule
severity: CAT III
cci: CCI-002385
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must be configured to ignore NetBIOS name release requests except from WINS servers.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254339
rule_id: xccdf_mil.disa.stig_rule_SV-254339r991589_rule
severity: CAT II
title: Windows Server 2022 insecure logons to an SMB server must be disabled.
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>Insecure guest logons allow unauthenticated access to shared folders. Shared resources on a system must require authentication to establish proper access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254340
rule_id: xccdf_mil.disa.stig_rule_SV-254340r991589_rule
severity: CAT II
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 hardened Universal Naming Convention (UNC) paths must be defined to require mutual authentication and integrity for at least the \\*\SYSVOL and \\*\NETLOGON shares.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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 the "Show" button to display):

  Value Name: \\*\SYSVOL
  Value: RequireMutualAuthentication=1, RequireIntegrity=1

  Value Name: \\*\NETLOGON
  Value: RequireMutualAuthentication=1, RequireIntegrity=1


vuln_id: V-254341
rule_id: xccdf_mil.disa.stig_rule_SV-254341r958422_rule
severity: CAT II
title: Windows Server 2022 command line data must be included in process creation events.
cci: CCI-000135
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254342
rule_id: xccdf_mil.disa.stig_rule_SV-254342r991589_rule
severity: CAT II
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must be configured to enable Remote host allows delegation of nonexportable credentials.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254343
rule_id: xccdf_mil.disa.stig_rule_SV-254343r991589_rule
severity: CAT II
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 virtualization-based security must be enabled with the platform security level configured to Secure Boot or Secure Boot with DMA Protection.

description:
  <VulnDiscussion>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).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254344
rule_id: xccdf_mil.disa.stig_rule_SV-254344r991589_rule
severity: CAT II
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 Early Launch Antimalware, Boot-Start Driver Initialization Policy must prevent boot drivers identified as bad.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254345
rule_id: xccdf_mil.disa.stig_rule_SV-254345r1135378_rule
severity: CAT II
title: Windows Server 2022 group policy objects must be reprocessed even if they have not changed.
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254346
rule_id: xccdf_mil.disa.stig_rule_SV-254346r958478_rule
severity: CAT II
title: Windows Server 2022 downloading print driver packages over HTTP must be turned off.
cci: CCI-000381
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254347
rule_id: xccdf_mil.disa.stig_rule_SV-254347r958478_rule
severity: CAT II
title: Windows Server 2022 printing over HTTP must be turned off.
cci: CCI-000381
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254348
rule_id: xccdf_mil.disa.stig_rule_SV-254348r958478_rule
severity: CAT II
cci: CCI-000381
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 network selection user interface (UI) must not be displayed on the logon screen.

description:
  <VulnDiscussion>Enabling interaction with the network selection UI allows users to change connections to available networks without signing in to Windows.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254349
rule_id: xccdf_mil.disa.stig_rule_SV-254349r991589_rule
severity: CAT II
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 users must be prompted to authenticate when the system wakes from sleep (on battery).

description:
  <VulnDiscussion>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).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254350
rule_id: xccdf_mil.disa.stig_rule_SV-254350r991589_rule
severity: CAT II
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 users must be prompted to authenticate when the system wakes from sleep (plugged in).

description:
  <VulnDiscussion>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).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254351
rule_id: xccdf_mil.disa.stig_rule_SV-254351r958478_rule
severity: CAT III
cci: CCI-000381
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 Application Compatibility Program Inventory must be prevented from collecting data and sending the information to Microsoft.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254352
rule_id: xccdf_mil.disa.stig_rule_SV-254352r958804_rule
severity: CAT I
title: Windows Server 2022 Autoplay must be turned off for nonvolume devices.
cci: CCI-001764
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254353
rule_id: xccdf_mil.disa.stig_rule_SV-254353r958804_rule
severity: CAT I
title: Windows Server 2022 default AutoRun behavior must be configured to prevent AutoRun commands.
cci: CCI-001764
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>Allowing AutoRun commands to execute may introduce malicious code to a system. Configuring this setting prevents AutoRun commands from executing.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254354
rule_id: xccdf_mil.disa.stig_rule_SV-254354r958804_rule
severity: CAT I
title: Windows Server 2022 AutoPlay must be disabled for all drives.
cci: CCI-001764
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254355
rule_id: xccdf_mil.disa.stig_rule_SV-254355r958518_rule
severity: CAT II
title: Windows Server 2022 administrator accounts must not be enumerated during elevation.
cci: CCI-001084
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254356
rule_id: xccdf_mil.disa.stig_rule_SV-254356r991589_rule
severity: CAT II
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 Diagnostic Data must be configured to send "required diagnostic data" or "optional diagnostic data".

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254357
rule_id: xccdf_mil.disa.stig_rule_SV-254357r991589_rule
severity: CAT III
title: Windows Server 2022 Windows Update must not obtain updates from other PCs on the internet.
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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:

  HTTP only (0)
  LAN (1)
  Group (2)
  Internet (3)
  Simple (99)


vuln_id: V-254358
rule_id: xccdf_mil.disa.stig_rule_SV-254358r958752_rule
severity: CAT II
title: Windows Server 2022 Application event log size must be configured to 32768 KB or greater.
cci: CCI-001849
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
[cell repeats an earlier one in this file: 559 characters]

fix_text:
  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.


vuln_id: V-254359
rule_id: xccdf_mil.disa.stig_rule_SV-254359r958752_rule
severity: CAT II
title: Windows Server 2022 Security event log size must be configured to 196608 KB or greater.
cci: CCI-001849
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
[cell repeats an earlier one in this file: 559 characters]

fix_text:
  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.


vuln_id: V-254360
rule_id: xccdf_mil.disa.stig_rule_SV-254360r958752_rule
severity: CAT II
title: Windows Server 2022 System event log size must be configured to 32768 KB or greater.
cci: CCI-001849
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
[cell repeats an earlier one in this file: 559 characters]

fix_text:
  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.


vuln_id: V-254361
rule_id: xccdf_mil.disa.stig_rule_SV-254361r958478_rule
severity: CAT II
title: Windows Server 2022 Microsoft Defender antivirus SmartScreen must be enabled.
cci: CCI-000381
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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 2022 includes duplicate policies for this setting. It can also be configured under Computer Configuration >> Administrative Templates >> Windows Components >> Windows Defender SmartScreen >> Explorer.


vuln_id: V-254362
rule_id: xccdf_mil.disa.stig_rule_SV-254362r958928_rule
severity: CAT II
title: Windows Server 2022 Explorer Data Execution Prevention must be enabled.
cci: CCI-002824
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254363
rule_id: xccdf_mil.disa.stig_rule_SV-254363r991589_rule
severity: CAT III
title: Windows Server 2022 Turning off File Explorer heap termination on corruption must be disabled.
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>Legacy plug-in applications may continue to function when a File Explorer session has become corrupt. Disabling this feature will prevent this.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254364
rule_id: xccdf_mil.disa.stig_rule_SV-254364r991589_rule
severity: CAT II
title: Windows Server 2022 File Explorer shell protocol must run in protected mode.
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254365
rule_id: xccdf_mil.disa.stig_rule_SV-254365r1051096_rule
severity: CAT II
title: Windows Server 2022 must not save passwords in the Remote Desktop Client.
cci: CCI-002038
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254366
rule_id: xccdf_mil.disa.stig_rule_SV-254366r1137695_rule
severity: CAT II
title: Windows Server 2022 Remote Desktop Services must prevent drive redirection.
cci: CCI-001090
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254367
rule_id: xccdf_mil.disa.stig_rule_SV-254367r1051097_rule
severity: CAT II
cci: CCI-002038
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 Remote Desktop Services must always prompt a client for passwords upon connection.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254368
rule_id: xccdf_mil.disa.stig_rule_SV-254368r958408_rule
severity: CAT II
cci: CCI-000068,CCI-001453
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 Remote Desktop Services must require secure Remote Procedure Call (RPC) communications.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254369
rule_id: xccdf_mil.disa.stig_rule_SV-254369r958408_rule
severity: CAT II
cci: CCI-000068,CCI-001453
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 Remote Desktop Services must be configured with the client connection encryption set to High Level.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254370
rule_id: xccdf_mil.disa.stig_rule_SV-254370r991589_rule
severity: CAT II
title: Windows Server 2022 must prevent attachments from being downloaded from RSS feeds.
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>Attachments from RSS feeds may not be secure. This setting will prevent attachments from being downloaded from RSS feeds.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254371
rule_id: xccdf_mil.disa.stig_rule_SV-254371r958478_rule
severity: CAT II
title: Windows Server 2022 must disable Basic authentication for RSS feeds over HTTP.
cci: CCI-000381
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
[cell repeats an earlier one in this file: 530 characters]

fix_text:
  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".


vuln_id: V-254372
rule_id: xccdf_mil.disa.stig_rule_SV-254372r958478_rule
severity: CAT II
title: Windows Server 2022 must prevent Indexing of encrypted files.
cci: CCI-000381
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>Indexing of encrypted files may expose sensitive data. This setting prevents encrypted files from being indexed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254373
rule_id: xccdf_mil.disa.stig_rule_SV-254373r1051098_rule
severity: CAT II
title: Windows Server 2022 must prevent users from changing installation options.
cci: CCI-003980,CCI-001812
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>Installation options for applications are typically controlled by administrators. This setting prevents users from changing installation options that may bypass security features.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254374
rule_id: xccdf_mil.disa.stig_rule_SV-254374r1051099_rule
severity: CAT I
cci: CCI-003980,CCI-001812
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must disable the Windows Installer Always install with elevated privileges option.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254375
rule_id: xccdf_mil.disa.stig_rule_SV-254375r991589_rule
severity: CAT II
title: Windows Server 2022 users must be notified if a web-based program attempts to install software.
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254376
rule_id: xccdf_mil.disa.stig_rule_SV-254376r991591_rule
severity: CAT II
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must disable automatically signing in the last interactive user after a system-initiated restart.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254377
rule_id: xccdf_mil.disa.stig_rule_SV-254377r958422_rule
severity: CAT II
title: Windows Server 2022 PowerShell script block logging must be enabled.
cci: CCI-000135
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254378
rule_id: xccdf_mil.disa.stig_rule_SV-254378r958510_rule
severity: CAT I
title: Windows Server 2022 Windows Remote Management (WinRM) client must not use Basic authentication.
cci: CCI-000877
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
[cell repeats an earlier one in this file: 530 characters]

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


vuln_id: V-254379
rule_id: xccdf_mil.disa.stig_rule_SV-254379r958848_rule
severity: CAT II
title: Windows Server 2022 Windows Remote Management (WinRM) client must not allow unencrypted traffic.
cci: CCI-002890,CCI-003123
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254380
rule_id: xccdf_mil.disa.stig_rule_SV-254380r958510_rule
severity: CAT II
title: Windows Server 2022 Windows Remote Management (WinRM) client must not use Digest authentication.
cci: CCI-000877
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254381
rule_id: xccdf_mil.disa.stig_rule_SV-254381r958510_rule
severity: CAT I
title: Windows Server 2022 Windows Remote Management (WinRM) service must not use Basic authentication.
cci: CCI-000877
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
[cell repeats an earlier one in this file: 530 characters]

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


vuln_id: V-254382
rule_id: xccdf_mil.disa.stig_rule_SV-254382r958848_rule
severity: CAT II
title: Windows Server 2022 Windows Remote Management (WinRM) service must not allow unencrypted traffic.
cci: CCI-002890,CCI-003123
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
[cell repeats an earlier one in this file: 606 characters]

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


vuln_id: V-254383
rule_id: xccdf_mil.disa.stig_rule_SV-254383r1051100_rule
severity: CAT II
title: Windows Server 2022 Windows Remote Management (WinRM) service must not store RunAs credentials.
cci: CCI-002038
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>Storage of administrative credentials could allow unauthorized access. Disallowing the storage of RunAs credentials for Windows Remote Management will prevent them from being used with plug-ins.

  Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254385
rule_id: xccdf_mil.disa.stig_rule_SV-254385r958726_rule
severity: CAT I
cci: CCI-002235
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must only allow administrators responsible for the domain controller to have Administrator rights on the system.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the Administrators group to include only administrator groups or accounts that are responsible for the system.

  Remove any standard user accounts.


vuln_id: V-254386
rule_id: xccdf_mil.disa.stig_rule_SV-254386r1051101_rule
severity: CAT II
title: Windows Server 2022 Kerberos user logon restrictions must be enforced.
cci: CCI-001941,CCI-001942
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254387
rule_id: xccdf_mil.disa.stig_rule_SV-254387r1051102_rule
severity: CAT II
cci: CCI-001941,CCI-001942
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 Kerberos service ticket maximum lifetime must be limited to 600 minutes or less.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254388
rule_id: xccdf_mil.disa.stig_rule_SV-254388r1051103_rule
severity: CAT II
title: Windows Server 2022 Kerberos user ticket lifetime must be limited to 10 hours or less.
cci: CCI-001941,CCI-001942
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254389
rule_id: xccdf_mil.disa.stig_rule_SV-254389r1051104_rule
severity: CAT II
cci: CCI-001941,CCI-001942
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 Kerberos policy user ticket renewal maximum lifetime must be limited to seven days or less.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254390
rule_id: xccdf_mil.disa.stig_rule_SV-254390r1051105_rule
severity: CAT II
cci: CCI-001941,CCI-001942
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 computer clock synchronization tolerance must be limited to five minutes or less.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254391
rule_id: xccdf_mil.disa.stig_rule_SV-254391r958726_rule
severity: CAT I
cci: CCI-001314,CCI-002235
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 permissions on the Active Directory data files must only allow System and Administrators access.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254392
rule_id: xccdf_mil.disa.stig_rule_SV-254392r958726_rule
severity: CAT I
cci: CCI-002235
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 Active Directory SYSVOL directory must have the proper access control permissions.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254393
rule_id: xccdf_mil.disa.stig_rule_SV-254393r1081073_rule
severity: CAT I
cci: CCI-002235
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 Active Directory Group Policy objects must have proper access control permissions.

description:
  <VulnDiscussion>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).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254394
rule_id: xccdf_mil.disa.stig_rule_SV-254394r958726_rule
severity: CAT I
cci: CCI-002235
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 Active Directory Domain Controllers Organizational Unit (OU) object must have the proper access control permissions.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254395
rule_id: xccdf_mil.disa.stig_rule_SV-254395r958726_rule
severity: CAT I
cci: CCI-002235
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 organization created Active Directory Organizational Unit (OU) objects must have proper access control permissions.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254396
rule_id: xccdf_mil.disa.stig_rule_SV-254396r1137695_rule
severity: CAT II
cci: CCI-001090
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 data files owned by users must be on a different logical partition from the directory server data files.

description:
  <VulnDiscussion>When directory service data files, especially for directories used for identification, authentication, or authorization, reside on the same logical partition as user-owned files, the directory service data may be more vulnerable to unauthorized access or other availability compromises. Directory service and user-owned data files sharing a partition may be configured with less restrictive permissions in order to allow access to the user data. 

  The directory service may be vulnerable to a denial of service attack when user-owned files on a common partition are expanded to an extent preventing the directory service from acquiring more space for directory or audit data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254397
rule_id: xccdf_mil.disa.stig_rule_SV-254397r958478_rule
severity: CAT II
title: Windows Server 2022 domain controllers must run on a machine dedicated to that function.
cci: CCI-000381
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254398
rule_id: xccdf_mil.disa.stig_rule_SV-254398r987791_rule
severity: CAT II
cci: CCI-002450
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 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.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254399
rule_id: xccdf_mil.disa.stig_rule_SV-254399r991589_rule
severity: CAT I
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 directory data (outside the root DSE) of a nonpublic directory must be configured to prevent anonymous access.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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 check V-8555 in the AD Forest STIG.


vuln_id: V-254400
rule_id: xccdf_mil.disa.stig_rule_SV-254400r970703_rule
severity: CAT III
cci: CCI-001133,CCI-002361
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 directory service must be configured to terminate LDAP-based network connections to the directory server after five minutes of inactivity.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254401
rule_id: xccdf_mil.disa.stig_rule_SV-254401r958732_rule
severity: CAT II
cci: CCI-000172,CCI-002234
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 Active Directory Group Policy objects must be configured with proper audit settings.

description:
  <VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. 

  For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes Group Policy objects. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder.

  Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the audit settings for Group Policy objects to include the following:

  This can be done at the Policy level in Active Directory to apply to all group policies.

  Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc").

  Select "Advanced Features" from the "View" Menu.

  Navigate to [Domain] >> System >> Policies in the left panel.

  Right-click "Policies", select "Properties".

  Select the "Security" tab.

  Select "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


vuln_id: V-254402
rule_id: xccdf_mil.disa.stig_rule_SV-254402r958732_rule
severity: CAT II
title: Windows Server 2022 Active Directory Domain object must be configured with proper audit settings.
cci: CCI-000172,CCI-002234
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. 

  For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the Domain object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder.

  Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc").

  Ensure "Advanced Features" is selected in the "View" menu.

  Select the domain being reviewed in the left pane.

  Right-click the domain name and select "Properties".

  Select the "Security" tab.

  Select "Advanced" and then 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.)


vuln_id: V-254403
rule_id: xccdf_mil.disa.stig_rule_SV-254403r958732_rule
severity: CAT II
cci: CCI-000172,CCI-002234
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 Active Directory Infrastructure object must be configured with proper audit settings.

description:
  <VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. 

  For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the Infrastructure object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder.

  Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc").

  Ensure "Advanced Features" is selected in the "View" menu.

  Select the domain being reviewed in the left pane.

  Right-click the "Infrastructure" object in the right pane and select "Properties".

  Select the "Security" tab.

  Select "Advanced" and then the "Auditing" tab.

  Configure the audit settings for Infrastructure object to include the following:

  Type - Fail
  Principal - Everyone
  Access - Full Control
  Inherited from - None

  The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default.

  Type - Success
  Principal - Everyone
  Access - Special
  Inherited from - None
  (Access - Special = Permissions: Write all properties, All extended rights, Change infrastructure master)

  Two instances with the following summary information will be listed:

  Type - Success
  Principal - Everyone
  Access - (blank)
  Inherited from - (CN of domain)


vuln_id: V-254404
rule_id: xccdf_mil.disa.stig_rule_SV-254404r958732_rule
severity: CAT II
cci: CCI-000172,CCI-002234
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 Active Directory Domain Controllers Organizational Unit (OU) object must be configured with proper audit settings.

description:
  <VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. 

  For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the Domain Controller OU object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder.

  Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc").

  Ensure "Advanced Features" is selected in the "View" menu.

  Select the "Domain Controllers OU" under the domain being reviewed in the left pane.

  Right-click the "Domain Controllers OU" object and select "Properties".

  Select the "Security" tab.

  Select "Advanced" and then 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


vuln_id: V-254405
rule_id: xccdf_mil.disa.stig_rule_SV-254405r958732_rule
severity: CAT II
cci: CCI-000172,CCI-002234
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 Active Directory AdminSDHolder object must be configured with proper audit settings.

description:
  <VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. 

  For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the AdminSDHolder object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder.

  Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc").

  Ensure "Advanced Features" is selected in the "View" menu.

  Select "System" under the domain being reviewed in the left pane.

  Right-click the "AdminSDHolder" object in the right pane and select "Properties".

  Select the "Security" tab.

  Select "Advanced" and then 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


vuln_id: V-254406
rule_id: xccdf_mil.disa.stig_rule_SV-254406r958732_rule
severity: CAT II
cci: CCI-000172,CCI-002234
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 Active Directory RID Manager$ object must be configured with proper audit settings.

description:
  <VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. 

  For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the RID Manager$ object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder.

  Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc").

  Ensure "Advanced Features" is selected in the "View" menu.

  Select "System" under the domain being reviewed in the left pane.

  Right-click the "RID Manager$" object in the right pane and select "Properties".

  Select the "Security" tab.

  Select "Advanced" and then 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)


vuln_id: V-254407
rule_id: xccdf_mil.disa.stig_rule_SV-254407r958368_rule
severity: CAT II
cci: CCI-000018,CCI-000172,CCI-001403,CCI-001404,CCI-001405,CCI-002130
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must be configured to audit Account Management - Computer Account Management successes.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254408
rule_id: xccdf_mil.disa.stig_rule_SV-254408r958732_rule
severity: CAT II
title: Windows Server 2022 must be configured to audit DS Access - Directory Service Access successes.
cci: CCI-000172,CCI-002234
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254409
rule_id: xccdf_mil.disa.stig_rule_SV-254409r958732_rule
severity: CAT II
title: Windows Server 2022 must be configured to audit DS Access - Directory Service Access failures.
cci: CCI-000172,CCI-002234
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
[cell repeats an earlier one in this file: 1038 characters]

fix_text:
  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.


vuln_id: V-254410
rule_id: xccdf_mil.disa.stig_rule_SV-254410r958732_rule
severity: CAT II
title: Windows Server 2022 must be configured to audit DS Access - Directory Service Changes successes.
cci: CCI-000172,CCI-002234
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254413
rule_id: xccdf_mil.disa.stig_rule_SV-254413r1153446_rule
severity: CAT I
fix_text: Obtain a server certificate for the domain controller issued by the DOD PKI or an approved ECA.
cci: CCI-000185
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 domain controller PKI certificates must be issued by the DOD PKI or an approved External Certificate Authority (ECA).

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>


vuln_id: V-254414
rule_id: xccdf_mil.disa.stig_rule_SV-254414r958448_rule
severity: CAT I
cci: CCI-000185
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 PKI certificates associated with user accounts must be issued by a DoD PKI or an approved External Certificate Authority (ECA).

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Map user accounts to PKI certificates using the appropriate User Principal Name (UPN) for the network. See PKE documentation for details.


vuln_id: V-254415
rule_id: xccdf_mil.disa.stig_rule_SV-254415r1081074_rule
severity: CAT II
cci: CCI-000776,CCI-000767,CCI-000768,CCI-001948
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 Active Directory 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.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure all user accounts, including administrator accounts, in Active Directory to enable the option "Smart card is required for interactive logon".

  Run "Active Directory Users and Computers" (available from various menus or run "dsa.msc"):

  Select the 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.


vuln_id: V-254416
rule_id: xccdf_mil.disa.stig_rule_SV-254416r958908_rule
severity: CAT II
title: Windows Server 2022 domain controllers must require LDAP access signing.
cci: CCI-002418,CCI-002421
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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 mode (AH), which performs mutual authentication and packet integrity for Internet Protocol (IP) traffic, can make all types of man-in-the-middle attacks extremely difficult.

  Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254417
rule_id: xccdf_mil.disa.stig_rule_SV-254417r991589_rule
severity: CAT II
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 domain controllers must be configured to allow reset of machine account passwords.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Domain controller: Refuse machine account password changes to "Disabled".


vuln_id: V-254418
rule_id: xccdf_mil.disa.stig_rule_SV-254418r1137691_rule
severity: CAT II
cci: CCI-000213
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 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.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254419
rule_id: xccdf_mil.disa.stig_rule_SV-254419r958726_rule
severity: CAT II
cci: CCI-002235
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 Add workstations to domain user right must only be assigned to the Administrators group on domain controllers.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254420
rule_id: xccdf_mil.disa.stig_rule_SV-254420r1137691_rule
severity: CAT II
cci: CCI-000213
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 Allow log on through Remote Desktop Services user right must only be assigned to the Administrators group on domain controllers.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254421
rule_id: xccdf_mil.disa.stig_rule_SV-254421r1137691_rule
severity: CAT II
cci: CCI-000213
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 Deny access to this computer from the network user right on domain controllers must be configured to prevent unauthenticated access.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254422
rule_id: xccdf_mil.disa.stig_rule_SV-254422r1137691_rule
severity: CAT II
cci: CCI-000213
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 Deny log on as a batch job user right on domain controllers must be configured to prevent unauthenticated access.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254423
rule_id: xccdf_mil.disa.stig_rule_SV-254423r1137691_rule
severity: CAT II
cci: CCI-000213
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 Deny log on as a service user right must be configured to include no accounts or groups (blank) on domain controllers.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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).


vuln_id: V-254424
rule_id: xccdf_mil.disa.stig_rule_SV-254424r1137691_rule
severity: CAT II
cci: CCI-000213
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 Deny log on locally user right on domain controllers must be configured to prevent unauthenticated access.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254425
rule_id: xccdf_mil.disa.stig_rule_SV-254425r958672_rule
severity: CAT II
cci: CCI-002314
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 Deny log on through Remote Desktop Services user right on domain controllers must be configured to prevent unauthenticated access.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254426
rule_id: xccdf_mil.disa.stig_rule_SV-254426r958726_rule
severity: CAT II
cci: CCI-002235
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 Enable computer and user accounts to be trusted for delegation user right must only be assigned to the Administrators group on domain controllers.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254427
rule_id: xccdf_mil.disa.stig_rule_SV-254427r991589_rule
severity: CAT II
title: The password for the krbtgt account on a domain must be reset at least every 180 days.
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254428
rule_id: xccdf_mil.disa.stig_rule_SV-254428r958726_rule
severity: CAT I
cci: CCI-002235
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must only allow administrators responsible for the member server or standalone or nondomain-joined system to have Administrator rights on the system.

description:
  <VulnDiscussion>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 (see V-243468 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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254429
rule_id: xccdf_mil.disa.stig_rule_SV-254429r958518_rule
severity: CAT II
cci: CCI-001084
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 local administrator accounts must have their privileged token filtered to prevent elevated privileges from being used over the network on domain-joined member servers.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254430
rule_id: xccdf_mil.disa.stig_rule_SV-254430r958478_rule
severity: CAT II
title: Windows Server 2022 local users on domain-joined member servers must not be enumerated.
cci: CCI-000381
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

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


vuln_id: V-254431
rule_id: xccdf_mil.disa.stig_rule_SV-254431r971545_rule
severity: CAT II
cci: CCI-001967
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 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.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Remote Procedure Call >> Restrict Unauthenticated RPC clients to "Enabled" with "Authenticated" selected.


vuln_id: V-254432
rule_id: xccdf_mil.disa.stig_rule_SV-254432r991589_rule
severity: CAT II
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must limit the caching of logon credentials to four or less on domain-joined member servers.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254433
rule_id: xccdf_mil.disa.stig_rule_SV-254433r1106522_rule
severity: CAT II
cci: CCI-002235
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must restrict remote calls to the Security Account Manager (SAM) to Administrators on domain-joined member servers and standalone or nondomain-joined systems.

description:
  <VulnDiscussion>The Windows SAM stores users' passwords. Restricting Remote Procedure Call (RPC) connections to the SAM to Administrators helps protect those credentials.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.

  If an application requires this user right, this would not be a finding. Vendor documentation must support the requirement for having the user right. The requirement must be documented and approved by the information system security officer (ISSO).


vuln_id: V-254434
rule_id: xccdf_mil.disa.stig_rule_SV-254434r1137691_rule
severity: CAT II
cci: CCI-000213
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 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.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254435
rule_id: xccdf_mil.disa.stig_rule_SV-254435r1137691_rule
severity: CAT II
cci: CCI-000213
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 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.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254436
rule_id: xccdf_mil.disa.stig_rule_SV-254436r1137691_rule
severity: CAT II
cci: CCI-000213
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 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.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254437
rule_id: xccdf_mil.disa.stig_rule_SV-254437r1137691_rule
severity: CAT II
cci: CCI-000213
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 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.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254438
rule_id: xccdf_mil.disa.stig_rule_SV-254438r1137691_rule
severity: CAT II
cci: CCI-000213
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 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.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254439
rule_id: xccdf_mil.disa.stig_rule_SV-254439r958672_rule
severity: CAT II
cci: CCI-002314
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 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.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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" is referring to the Windows built-in security group.


vuln_id: V-254440
rule_id: xccdf_mil.disa.stig_rule_SV-254440r958726_rule
severity: CAT II
cci: CCI-002235
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 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.

description:
[cell repeats an earlier one in this file: 694 characters]

fix_text:
  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).


vuln_id: V-254441
rule_id: xccdf_mil.disa.stig_rule_SV-254441r991589_rule
severity: CAT I
title: Windows Server 2022 must be running Credential Guard on domain-joined member servers.
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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 requirement 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 10 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.


vuln_id: V-254442
rule_id: xccdf_mil.disa.stig_rule_SV-254442r958448_rule
severity: CAT II
cci: CCI-000185,CCI-002470
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must have the DoD Root Certificate Authority (CA) certificates installed in the Trusted Root Store.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Install the DoD Root CA certificates:

  DoD Root CA 3
  DoD Root CA 4
  DoD Root CA 5
  DoD Root CA 6

  The InstallRoot tool is available on Cyber Exchange at https://cyber.mil/pki-pke/tools-configuration-files. Certificate bundles published by the PKI can be found at https://crl.gds.disa.mil/.


vuln_id: V-254443
rule_id: xccdf_mil.disa.stig_rule_SV-254443r958448_rule
severity: CAT II
cci: CCI-000185,CCI-002470
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must have the DoD Interoperability Root Certificate Authority (CA) cross-certificates installed in the Untrusted Certificates Store on unclassified systems.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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

  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. Certificate bundles published by the PKI can be found at https://crl.gds.disa.mil/.


vuln_id: V-254444
rule_id: xccdf_mil.disa.stig_rule_SV-254444r1081077_rule
severity: CAT II
cci: CCI-000185,CCI-002470
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must have the US DOD CCEB Interoperability Root CA cross-certificates in the Untrusted Certificates Store on unclassified systems.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Install the US DOD CCEB Interoperability Root CA cross-certificate on unclassified systems.

  Issued To - Issued By - Thumbprint

  DOD Root CA 3 - US DOD CCEB Interoperability Root CA 2 - 9B74964506C7ED9138070D08D5F8B969866560C8 
  DOD Root CA 6 -US DOD CCEB Interoperability Root CA 2 - D471CA32F7A692CE6CBB6196BD3377FE4DBCD106

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


vuln_id: V-254445
rule_id: xccdf_mil.disa.stig_rule_SV-254445r958504_rule
severity: CAT II
title: Windows Server 2022 must have the built-in guest account disabled.
cci: CCI-000804
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Accounts: Guest account status to "Disabled".


vuln_id: V-254446
rule_id: xccdf_mil.disa.stig_rule_SV-254446r991589_rule
severity: CAT I
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must prevent local accounts with blank passwords from being used from the network.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254447
rule_id: xccdf_mil.disa.stig_rule_SV-254447r991589_rule
severity: CAT II
title: Windows Server 2022 built-in administrator account must be renamed.
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254448
rule_id: xccdf_mil.disa.stig_rule_SV-254448r991589_rule
severity: CAT II
title: Windows Server 2022 built-in guest account must be renamed.
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254449
rule_id: xccdf_mil.disa.stig_rule_SV-254449r958442_rule
severity: CAT II
cci: CCI-000169
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must force audit policy subcategory settings to override audit policy category settings.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings to "Enabled".


vuln_id: V-254450
rule_id: xccdf_mil.disa.stig_rule_SV-254450r958908_rule
severity: CAT II
cci: CCI-002418,CCI-002421
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 setting Domain member: Digitally encrypt or sign secure channel data (always) must be configured to Enabled.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254451
rule_id: xccdf_mil.disa.stig_rule_SV-254451r958908_rule
severity: CAT II
cci: CCI-002418,CCI-002421
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 setting Domain member: Digitally encrypt secure channel data (when possible) must be configured to Enabled.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254452
rule_id: xccdf_mil.disa.stig_rule_SV-254452r958908_rule
severity: CAT II
cci: CCI-002418,CCI-002421
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 setting Domain member: Digitally sign secure channel data (when possible) must be configured to Enabled.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254453
rule_id: xccdf_mil.disa.stig_rule_SV-254453r971545_rule
severity: CAT II
title: Windows Server 2022 computer account password must not be prevented from being reset.
cci: CCI-001967
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Domain member: Disable machine account password changes to "Disabled".


vuln_id: V-254454
rule_id: xccdf_mil.disa.stig_rule_SV-254454r991589_rule
severity: CAT II
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 maximum age for machine account passwords must be configured to 30 days or less.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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).


vuln_id: V-254455
rule_id: xccdf_mil.disa.stig_rule_SV-254455r958908_rule
severity: CAT II
title: Windows Server 2022 must be configured to require a strong session key.
cci: CCI-002418,CCI-002421
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254456
rule_id: xccdf_mil.disa.stig_rule_SV-254456r958400_rule
severity: CAT II
cci: CCI-000056,CCI-000057,CCI-000060
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 machine inactivity limit must be set to 15 minutes or less, locking the system with the screen saver.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254457
rule_id: xccdf_mil.disa.stig_rule_SV-254457r958390_rule
severity: CAT II
title: Windows Server 2022 required legal notice must be configured to display before console logon.
cci: CCI-000048,CCI-000050,CCI-001384,CCI-001385,CCI-001386,CCI-001387,CCI-001388
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254458
rule_id: xccdf_mil.disa.stig_rule_SV-254458r958390_rule
severity: CAT III
title: Windows Server 2022 title for legal banner dialog box must be configured with the appropriate text.
cci: CCI-000048,CCI-001384,CCI-001385,CCI-001386,CCI-001387,CCI-001388
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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 WN22-SO-000150.


vuln_id: V-254459
rule_id: xccdf_mil.disa.stig_rule_SV-254459r991589_rule
severity: CAT II
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 Smart Card removal option must be configured to Force Logoff or Lock Workstation.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254460
rule_id: xccdf_mil.disa.stig_rule_SV-254460r958908_rule
severity: CAT II
cci: CCI-002418,CCI-002421
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 setting Microsoft network client: Digitally sign communications (always) must be configured to Enabled.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Microsoft network client: Digitally sign communications (always) to "Enabled".


vuln_id: V-254461
rule_id: xccdf_mil.disa.stig_rule_SV-254461r958908_rule
severity: CAT II
cci: CCI-002418,CCI-002421
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 setting Microsoft network client: Digitally sign communications (if server agrees) must be configured to Enabled.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254462
rule_id: xccdf_mil.disa.stig_rule_SV-254462r987796_rule
severity: CAT II
cci: CCI-000197
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 unencrypted passwords must not be sent to third-party Server Message Block (SMB) servers.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254463
rule_id: xccdf_mil.disa.stig_rule_SV-254463r958908_rule
severity: CAT II
cci: CCI-002418,CCI-002421
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 setting Microsoft network server: Digitally sign communications (always) must be configured to Enabled.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Microsoft network server: Digitally sign communications (always) to "Enabled".


vuln_id: V-254464
rule_id: xccdf_mil.disa.stig_rule_SV-254464r958908_rule
severity: CAT II
cci: CCI-002418,CCI-002421
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 setting Microsoft network server: Digitally sign communications (if client agrees) must be configured to Enabled.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254465
rule_id: xccdf_mil.disa.stig_rule_SV-254465r991589_rule
severity: CAT I
title: Windows Server 2022 must not allow anonymous SID/Name translation.
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>Allowing anonymous SID/Name translation can provide sensitive information for accessing a system. Only authorized users must be able to perform such translations.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Network access: Allow anonymous SID/Name translation to "Disabled".


vuln_id: V-254466
rule_id: xccdf_mil.disa.stig_rule_SV-254466r991589_rule
severity: CAT I
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must not allow anonymous enumeration of Security Account Manager (SAM) accounts.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254467
rule_id: xccdf_mil.disa.stig_rule_SV-254467r1137695_rule
severity: CAT I
title: Windows Server 2022 must not allow anonymous enumeration of shares.
cci: CCI-001090
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254468
rule_id: xccdf_mil.disa.stig_rule_SV-254468r991589_rule
severity: CAT II
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must be configured to prevent anonymous users from having the same permissions as the Everyone group.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254469
rule_id: xccdf_mil.disa.stig_rule_SV-254469r1137695_rule
severity: CAT I
title: Windows Server 2022 must restrict anonymous access to Named Pipes and Shares.
cci: CCI-001090
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254470
rule_id: xccdf_mil.disa.stig_rule_SV-254470r991589_rule
severity: CAT II
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 services using Local System that use Negotiate when reverting to NTLM authentication must use the computer identity instead of authenticating anonymously.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254471
rule_id: xccdf_mil.disa.stig_rule_SV-254471r991589_rule
severity: CAT II
title: Windows Server 2022 must prevent NTLM from falling back to a Null session.
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>NTLM sessions that are allowed to fall back to Null (unauthenticated) sessions may gain unauthorized access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> Network security: Allow LocalSystem NULL session fallback to "Disabled".


vuln_id: V-254472
rule_id: xccdf_mil.disa.stig_rule_SV-254472r991589_rule
severity: CAT II
title: Windows Server 2022 must prevent PKU2U authentication using online identities.
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254473
rule_id: xccdf_mil.disa.stig_rule_SV-254473r971535_rule
severity: CAT II
cci: CCI-000803
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 Kerberos encryption types must be configured to prevent the use of DES and RC4 encryption suites.

description:
  <VulnDiscussion>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, selecting "The other domain supports Kerberos AES Encryption" on domain trusts, may be required to allow client communication across the trust relationship.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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, selecting "The other domain supports Kerberos AES Encryption" on domain trusts, may be required to allow client communication across the trust relationship.


vuln_id: V-254474
rule_id: xccdf_mil.disa.stig_rule_SV-254474r1051107_rule
severity: CAT I
title: Windows Server 2022 must be configured to prevent the storage of the LAN Manager hash of passwords.
cci: CCI-004062,CCI-000196
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254475
rule_id: xccdf_mil.disa.stig_rule_SV-254475r991589_rule
severity: CAT I
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 LAN Manager authentication level must be configured to send NTLMv2 response only and to refuse LM and NTLM.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254476
rule_id: xccdf_mil.disa.stig_rule_SV-254476r991589_rule
severity: CAT II
title: Windows Server 2022 must be configured to at least negotiate signing for LDAP client signing.
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254477
rule_id: xccdf_mil.disa.stig_rule_SV-254477r991589_rule
severity: CAT II
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 session security for NTLM SSP-based clients must be configured to require NTLMv2 session security and 128-bit encryption.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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).


vuln_id: V-254478
rule_id: xccdf_mil.disa.stig_rule_SV-254478r991589_rule
severity: CAT II
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 session security for NTLM SSP-based servers must be configured to require NTLMv2 session security and 128-bit encryption.

description:
[cell repeats an earlier one in this file: 571 characters]

fix_text:
  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).


vuln_id: V-254479
rule_id: xccdf_mil.disa.stig_rule_SV-254479r958450_rule
severity: CAT II
cci: CCI-000186
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 users must be required to enter a password to access private keys stored on the computer.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254480
rule_id: xccdf_mil.disa.stig_rule_SV-254480r1137699_rule
severity: CAT II
cci: CCI-002450
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 must be configured to use FIPS-compliant algorithms for encryption, hashing, and signing.

description:
  <VulnDiscussion>This setting ensures the system uses algorithms that are FIPS-compliant for encryption, hashing, and signing. FIPS-compliant algorithms meet specific standards established by the U.S. Government and must be the algorithms used for all OS encryption functions.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254481
rule_id: xccdf_mil.disa.stig_rule_SV-254481r991589_rule
severity: CAT III
title: Windows Server 2022 default permissions of global system objects must be strengthened.
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254482
rule_id: xccdf_mil.disa.stig_rule_SV-254482r1051108_rule
severity: CAT II
cci: CCI-002038
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 User Account Control (UAC) approval mode for the built-in Administrator must be enabled.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254483
rule_id: xccdf_mil.disa.stig_rule_SV-254483r958518_rule
severity: CAT II
cci: CCI-001084
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 UIAccess applications must not be allowed to prompt for elevation without using the secure desktop.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254484
rule_id: xccdf_mil.disa.stig_rule_SV-254484r958518_rule
severity: CAT II
cci: CCI-001084
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 User Account Control (UAC) must, at a minimum, prompt administrators for consent on the secure desktop.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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.


vuln_id: V-254485
rule_id: xccdf_mil.disa.stig_rule_SV-254485r1051109_rule
severity: CAT II
cci: CCI-002038
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 User Account Control (UAC) must automatically deny standard user requests for elevation.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254486
rule_id: xccdf_mil.disa.stig_rule_SV-254486r958518_rule
severity: CAT II
cci: CCI-001084
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 User Account Control (UAC) must be configured to detect application installations and prompt for elevation.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254487
rule_id: xccdf_mil.disa.stig_rule_SV-254487r958518_rule
severity: CAT II
cci: CCI-001084
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 User Account Control (UAC) must only elevate UIAccess applications that are installed in secure locations.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254488
rule_id: xccdf_mil.disa.stig_rule_SV-254488r1051110_rule
severity: CAT II
cci: CCI-002038
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 User Account Control (UAC) must run all administrators in Admin Approval Mode, enabling UAC.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254489
rule_id: xccdf_mil.disa.stig_rule_SV-254489r958518_rule
severity: CAT II
cci: CCI-001084
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 User Account Control (UAC) must virtualize file and registry write failures to per-user locations.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254490
rule_id: xccdf_mil.disa.stig_rule_SV-254490r991589_rule
severity: CAT II
title: Windows Server 2022 must preserve zone information when saving attachments.
cci: CCI-000366
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254491
rule_id: xccdf_mil.disa.stig_rule_SV-254491r958726_rule
severity: CAT II
cci: CCI-002235
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 Access Credential Manager as a trusted caller user right must not be assigned to any groups or accounts.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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).


vuln_id: V-254492
rule_id: xccdf_mil.disa.stig_rule_SV-254492r958726_rule
severity: CAT I
cci: CCI-002235
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 Act as part of the operating system user right must not be assigned to any groups or accounts.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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).


vuln_id: V-254493
rule_id: xccdf_mil.disa.stig_rule_SV-254493r1137691_rule
severity: CAT II
cci: CCI-000213
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 Allow log on locally user right must only be assigned to the Administrators group.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254494
rule_id: xccdf_mil.disa.stig_rule_SV-254494r958726_rule
severity: CAT II
cci: CCI-002235
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 back up files and directories user right must only be assigned to the Administrators group.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254495
rule_id: xccdf_mil.disa.stig_rule_SV-254495r958726_rule
severity: CAT II
title: Windows Server 2022 create a pagefile user right must only be assigned to the Administrators group.
cci: CCI-002235
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254496
rule_id: xccdf_mil.disa.stig_rule_SV-254496r958726_rule
severity: CAT I
cci: CCI-002235
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 create a token object user right must not be assigned to any groups or accounts.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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).


vuln_id: V-254497
rule_id: xccdf_mil.disa.stig_rule_SV-254497r958726_rule
severity: CAT II
cci: CCI-002235
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 create global objects user right must only be assigned to Administrators, Service, Local Service, and Network Service.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254498
rule_id: xccdf_mil.disa.stig_rule_SV-254498r958726_rule
severity: CAT II
cci: CCI-002235
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 create permanent shared objects user right must not be assigned to any groups or accounts.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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).


vuln_id: V-254499
rule_id: xccdf_mil.disa.stig_rule_SV-254499r958726_rule
severity: CAT II
cci: CCI-002235
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 create symbolic links user right must only be assigned to the Administrators group.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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".


vuln_id: V-254500
rule_id: xccdf_mil.disa.stig_rule_SV-254500r958726_rule
severity: CAT I
title: Windows Server 2022 debug programs user right must only be assigned to the Administrators group.
cci: CCI-002235
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254501
rule_id: xccdf_mil.disa.stig_rule_SV-254501r958726_rule
severity: CAT II
cci: CCI-002235
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 force shutdown from a remote system user right must only be assigned to the Administrators group.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254502
rule_id: xccdf_mil.disa.stig_rule_SV-254502r958726_rule
severity: CAT II
cci: CCI-002235
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 generate security audits user right must only be assigned to Local Service and Network Service.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254503
rule_id: xccdf_mil.disa.stig_rule_SV-254503r958726_rule
severity: CAT II
cci: CCI-002235
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 impersonate a client after authentication user right must only be assigned to Administrators, Service, Local Service, and Network Service.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254504
rule_id: xccdf_mil.disa.stig_rule_SV-254504r958726_rule
severity: CAT II
cci: CCI-002235
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 increase scheduling priority: user right must only be assigned to the Administrators group.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254505
rule_id: xccdf_mil.disa.stig_rule_SV-254505r958726_rule
severity: CAT II
cci: CCI-002235
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 load and unload device drivers user right must only be assigned to the Administrators group.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254506
rule_id: xccdf_mil.disa.stig_rule_SV-254506r958726_rule
severity: CAT II
title: Windows Server 2022 lock pages in memory user right must not be assigned to any groups or accounts.
cci: CCI-002235,CCI-002824
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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).


vuln_id: V-254507
rule_id: xccdf_mil.disa.stig_rule_SV-254507r958434_rule
severity: CAT II
cci: CCI-000162,CCI-000163,CCI-000164,CCI-000171,CCI-001914
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 manage auditing and security log user right must only be assigned to the Administrators group.

description:
  <VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254508
rule_id: xccdf_mil.disa.stig_rule_SV-254508r958726_rule
severity: CAT II
cci: CCI-002235
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 modify firmware environment values user right must only be assigned to the Administrators group.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254509
rule_id: xccdf_mil.disa.stig_rule_SV-254509r958726_rule
severity: CAT II
cci: CCI-002235
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 perform volume maintenance tasks user right must only be assigned to the Administrators group.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254510
rule_id: xccdf_mil.disa.stig_rule_SV-254510r958726_rule
severity: CAT II
cci: CCI-002235
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 profile single process user right must only be assigned to the Administrators group.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254511
rule_id: xccdf_mil.disa.stig_rule_SV-254511r958726_rule
severity: CAT II
cci: CCI-002235
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 restore files and directories user right must only be assigned to the Administrators group.

description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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


vuln_id: V-254512
rule_id: xccdf_mil.disa.stig_rule_SV-254512r958726_rule
severity: CAT II
cci: CCI-002235
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
title:
  Windows Server 2022 take ownership of files or other objects user right must only be assigned to the Administrators group.

description:
  <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.

  Accounts with the "Take ownership of files or other objects" user right can take ownership of objects and make changes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> Take ownership of files or other objects to include only the following accounts or groups:

  - Administrators


vuln_id: V-271426
rule_id: xccdf_mil.disa.stig_rule_SV-271426r1137691_rule
severity: CAT II
title: Windows Server 2022 must be configured for certificate-based authentication for domain controllers.
cci: CCI-000213
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>Active Directory domain services elevation of privilege vulnerability could allow a user rights to the system, such as administrative and other high-level capabilities.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  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)


vuln_id: V-271427
rule_id: xccdf_mil.disa.stig_rule_SV-271427r1137691_rule
severity: CAT II
title: Windows Server 2022 must be configured for name-based strong mappings for certificates.
cci: CCI-000213
created_at: 2026-03-12 15:44:32
updated_at: 2026-03-12 15:44:32
description:
  <VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the policy value for Computer Configuration >> Administrative Template >> System >> KDC >> Allow name-based strong mappings for certificates to "Enabled".


vuln_id: xccdf_mil.disa.stig_group_V-278953
rule_id: xccdf_mil.disa.stig_rule_SV-278953r1135550_rule
severity: CAT II
title: HTTPAPI Server version must be removed from the HTTP Response Header information.
cci: CCI-001312
created_at: 2026-03-12 19:38:14
updated_at: 2026-03-12 19:38:14
description:
[cell repeats an earlier one in this file: 657 characters]

fix_text:
  Navigate to "HKLM\System\CurrentControlSet\Services\HTTP\Parameters".

  Create REG_DWORD "DisableServerHeader” and set it to "2".

  Note: This can be performed multiple ways; this is an example.


vuln_id: xccdf_mil.disa.stig_group_V-279940
rule_id: xccdf_mil.disa.stig_rule_SV-279940r1156561_rule
severity: CAT II
title: Access to Microsoft 365 Copilot writing assistance must be disabled.
cci: CCI-000381
created_at: 2026-03-12 19:38:14
updated_at: 2026-03-12 19:38:14
description:
  <VulnDiscussion>This policy controls whether users can use writing support features in Microsoft Edge for Business, such as Rewrite, which utilizes Microsoft 365 Copilot Chat.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Set the policy value for "Control access to Microsoft 365 Copilot writing assistance in Microsoft Edge for Business" to "disabled".


vuln_id: V-279940
rule_id: SV-279940r1156561_rule
severity: CAT II
title: Access to Microsoft 365 Copilot writing assistance must be disabled.
cci: CCI-000381
created_at: 2026-03-12 19:56:39
updated_at: 2026-03-12 19:56:39
description:
  <VulnDiscussion>This policy controls whether users can use writing support features in Microsoft Edge for Business, such as Rewrite, which utilizes Microsoft 365 Copilot Chat.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Set the policy value for "Control access to Microsoft 365 Copilot writing assistance in Microsoft Edge for Business" to "disabled".

check_text:
  The policy value for "Computer Configuration/Administrative Templates/Microsoft Edge/Control access to Microsoft 365 Copilot writing assistance in Microsoft Edge for Business" must be set to "disabled".

  Use the Windows Registry Editor to navigate to the following key:
  HKLM\SOFTWARE\Policies\Microsoft\Edge

  If the value for "ComposeInlineEnabled" is not set to "REG_DWORD = 0", this is a finding.


vuln_id: V-278953
rule_id: SV-278953r1135550_rule
severity: CAT II
title: HTTPAPI Server version must be removed from the HTTP Response Header information.
cci: CCI-001312
created_at: 2026-03-12 20:00:16
updated_at: 2026-03-12 20:00:16
description:
[cell repeats an earlier one in this file: 657 characters]

fix_text:
  Navigate to "HKLM\System\CurrentControlSet\Services\HTTP\Parameters".

  Create REG_DWORD "DisableServerHeader” and set it to "2".

  Note: This can be performed multiple ways; this is an example.

check_text:
  Note: If the server is hosting WSUS, this is not applicable.

  Open Registry Editor.

  Navigate to "HKLM\System\CurrentControlSet\Services\HTTP\Parameters".

  Verify "DisableServerHeader” is set to "2".

  If REG_DWORD DisableServerHeader is not set to "2", this is a finding.

  If the system administrator can show that Server Version information has been removed via other means, such as using a rewrite outbound rule, this is not a finding.


