V2R5 changes
VMware vSphere 8.0 vCenter STIG V2R5 (2026-09-30) replaced V2R4 (2026-07-01): 6 checks updated. It has 67 checks, against 67 in V2R4.
V2R5 checklistV2R4 checklist Compare V2R4 and V2R5 in STIG Compare
- 0 added
- 0 removed
- 6 updated
Updated fields: Check text 3Fix text 3Title 3Discussion 3Severity 1
Updated in V2R5 (6)
V-258906CAT IIThe vCenter Server must display the Standard Mandatory DoW Notice and Consent Banner before logon.Title, Check text, Fix text, Discussion
Title
The vCenter Server must display the Standard Mandatory DODoW Notice and Consent Banner before logon.
Check text
From the vSphere Client, go to Administration >> Single Sign On >> Configuration >> Login Message.
If the selection box next to "Show login message" is disabled, "Details of login message" is not configured to the standard DODDoW User Agreement, or the "Consent checkbox" is disabled, this is a finding.
Note: Refer to vulnerability discussion for user agreement language.
Fix text
From the vSphere Client, go to Administration >> Single Sign On >> Configuration >> Login Message.
Click "Edit".
Click the "Show login message" slider to enable.
Configure the "Login message" to "DODDoW User Agreement".
Click the "Consent checkbox" slider to enable.
Set the "Details of login message" to the Standard Mandatory DODDoW Notice and Consent Banner text.
Click "Save".
Discussion
Display of the DODDoW-approved use notification before granting access to the application ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.
System use notifications are required only for access via login interfaces with human users and are not required when such human interfaces do not exist.
The banner must be formatted in accordance with DTM-08-060. Use the following verbiage for applications that can accommodate banners of 1300 characters:
"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."
Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner:
"I've read (literal ampersand) consent to terms in IS user agreem't."
Satisfies: SRG-APP-000068, SRG-APP-000069, SRG-APP-000070
V-258917CAT IThe vCenter Server must enable FIPS-validated cryptography.Discussion
Discussion
FIPS 140-2 is the current standard for validating that mechanisms used to access cryptographic modules use authentication that meets DODDoW requirements.
In vSphere 6.7 and later, ESXi and vCenter Server use FIPS-validated cryptography to protect management interfaces and the VMware Certificate Authority (VMCA).
vSphere 7.0 Update 2 and later adds additional FIPS-validated cryptography to vCenter Server Appliance. By default, this FIPS validation option is disabled and must be enabled.
Satisfies: SRG-APP-000172, SRG-APP-000179, SRG-APP-000224, SRG-APP-000231, SRG-APP-000412, SRG-APP-000514, SRG-APP-000555, SRG-APP-000600, SRG-APP-000610, SRG-APP-000620, SRG-APP-000630, SRG-APP-000635
V-258918CAT IIThe vCenter Server must enforce a 90-day maximum password lifetime restriction.Check text, Fix text
Check text
From the vSphere Client, go to Administration >> Single Sign On >> Configuration >> Local Accounts >> Password Policy.
View the value of the "Maximum lifetime" setting.
Maximum lifetime: Password must be changed every 90180 days
If the password policy is not configured with "Maximum lifetime" policy of "90180" or less, this is a finding.
Fix text
From the vSphere Client, go to Administration >> Single Sign On >> Configuration >> Local Accounts >> Password Policy.
Click "Edit".
Set "Maximum lifetime" to "90180" and click "Save".
V-258928CAT IIThe vCenter Server Machine Secure Sockets Layer (SSL) certificate must be issued by a DoW certificate authority.Title, Check text, Fix text, Discussion
Title
The vCenter Server Machine Secure Sockets Layer (SSL) certificate must be issued by a DODoW certificate authority.
Check text
From the vSphere Client, go to Administration >> Certificates >> Certificate Management >> Machine SSL Certificate.
Click "View Details" and examine the "Issuer Information" block.
If the issuer specified is not a DODDoW approved certificate authority, this is a finding.
Fix text
Obtain a DODDoW-issued certificate and private key for each vCenter in the system following the requirements below:
Key size: 2048 bits or more (PEM encoded)
CRT format (Base-64)
x509 version 3
SubjectAltName must contain DNS Name=<machine_FQDN>
Contains the following Key Usages: Digital Signature, Non Repudiation, Key Encipherment
Export the entire certificate issuing chain up to the root in Base-64 format. Concatenate the individual certificates into one file with the ".cer" extension.
From the vSphere Client, go to Administration >> Certificates >> Certificate Management >> Machine SSL Certificate.
Click Actions >> Import and Replace Certificate.
Select the "Replace with external CA certificate" radio button and click "Next".
Supply the CA-issued certificate , the exported roots file, and the private key.
Click "Replace".
Discussion
Untrusted certificate authorities (CA) can issue certificates, but they may be issued by organizations or individuals that seek to compromise DODDoW systems or by organizations with insufficient security controls. If the CA used for verifying the certificate is not a DODDoW-approved CA, trust of this CA has not been established.
The DODDoW will only accept public key infrastructure (PKI) certificates obtained from a DODDoW-approved internal or external certificate authority. Reliance on CAs for the establishment of secure sessions includes, for example, the use of Transport Layer Security (TLS) certificates.
The default self-signed, VMware Certificate Authority (VMCA)-issued vCenter reverse proxy certificate must be replaced with a DODDoW-approved certificate. The use of a DODDoW certificate on the vCenter reverse proxy and other services assures clients that the service they are connecting to is legitimate and trusted.
V-258929CAT IThe vCenter Server must enable data at rest encryption for vSAN.Severity
V-265978CAT IIThe vCenter Server must use DoW-approved encryption to protect the confidentiality of network sessions.Title
Title
The vCenter Server must use DODoW-approved encryption to protect the confidentiality of network sessions.
How these changes are found
Checks are matched across the two releases by V-number. A check counts as updated when DISA gave it a new rule revision (the r number in its SV-…_rule id) and its title, severity, check text, fix text, discussion, CCIs or other fields changed — the same comparison STIG Compare makes. Added checks are new V-numbers; removed checks are V-numbers V2R5 no longer has.
Comparing other releases, or this one against an older release? Pick any two in STIG Compare.