| Finding ID |
Severity |
Title |
Description |
|
V-256331
|
High |
The vCenter Server must enable FIPS-validated cryptography. |
FIPS 140-2 is the current standard for validating that mechanisms used to access cryptographic modules use authentication that meets DOD 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... |
|
V-256318
|
High |
The vCenter Server must use TLS 1.2, at a minimum, to protect the confidentiality of sensitive data during electronic dissemination using remote access. |
Using older unauthorized versions or incorrectly configuring protocol negotiation makes the gateway vulnerable to known and unknown attacks that exploit vulnerabilities in this protocol.
Satisfies: SRG-APP-000014, SRG-APP-000645, SRG-APP-000156, SRG-APP-000157, SRG-APP-000219, SRG-APP-000439, SRG-APP-000440, SRG-APP-000441, SRG-APP-000442, SRG-APP-000560, SRG-APP-000565, SRG-APP-000625 |
|
V-256374
|
Medium |
vCenter Native Key Providers must be backed up with a strong password. |
The vCenter Native Key Provider feature was introduced in U2 and acts as a key provider for encryption-based capabilities, such as encrypted virtual machines without requiring an external KMS solution. When enabling this feature, a backup must be taken that is a PKCS#12 formatted file. If no password is provided... |
|
V-256373
|
Medium |
vCenter task and event retention must be set to at least 30 days. |
vCenter tasks and events contain valuable historical actions, useful in troubleshooting availability issues and for incident forensics. While vCenter events are sent to central log servers in real time, it is important that administrators have quick access to this information when needed.
vCenter retains 30 days of tasks and events... |
|
V-256372
|
Medium |
The vCenter server configuration must be backed up on a regular basis. |
vCenter server is the control plane for the vSphere infrastructure and all the workloads it hosts. As such, vCenter is usually a highly critical system in its own right. Backups of vCenter can now be made at a data and configuration level versus traditional storage/image-based backups. This reduces recovery time... |
|
V-256371
|
Medium |
The vCenter Server must limit membership to the "TrustedAdmins" Single Sign-On (SSO) group. |
The vSphere "TrustedAdmins" group grants additional rights to administer the vSphere Trust Authority feature.
To force accountability and nonrepudiation, the SSO group "TrustedAdmins" must be severely restricted. |
|
V-256370
|
Medium |
The vCenter Server must limit membership to the "SystemConfiguration.BashShellAdministrators" Single Sign-On (SSO) group. |
vCenter SSO integrates with PAM in the underlying Photon operating system so members of the "SystemConfiguration.BashShellAdministrators" SSO group can log on to the operating system without needing a separate account. However, even though unique SSO users log on, they are transparently using a group account named "sso-user" as far as... |
|
V-256369
|
Medium |
The vCenter Server must use a limited privilege account when adding a Lightweight Directory Access Protocol (LDAP) identity source. |
When adding an LDAP identity source to vSphere Single Sign-On (SSO), the account used to bind to Active Directory must be minimally privileged. This account only requires read rights to the base domain name specified. Any other permissions inside or outside of that organizational unit are unnecessary and violate least... |
|
V-256368
|
Medium |
The vCenter Server must use secure Lightweight Directory Access Protocol (LDAPS) when adding an LDAP identity source. |
LDAP is an industry standard protocol for querying directory services such as Active Directory. This protocol can operate in clear text or over a Secure Sockets Layer (SSL)/Transport Layer Security (TLS) encrypted tunnel. To protect confidentiality of LDAP communications, secure LDAP (LDAPS) must be explicitly configured when adding an LDAP... |
|
V-256367
|
Medium |
The vCenter Server must have new Key Encryption Keys (KEKs) reissued at regular intervals for vSAN encrypted datastore(s). |
The KEK for a vSAN encrypted datastore is generated by the Key Management Server (KMS) and serves as a wrapper and lock around the Disk Encryption Key (DEK). The DEK is generated by the host and is used to encrypt and decrypt the datastore. A shallow rekey is a procedure... |
|
V-256366
|
Medium |
The vCenter Server must have Mutual Challenge Handshake Authentication Protocol (CHAP) configured for vSAN Internet Small Computer System Interface (iSCSI) targets. |
When enabled, vSphere performs bidirectional authentication of both the iSCSI target and host. When not authenticating both the iSCSI target and host, the potential exists for a man-in-the-middle attack in which an attacker might impersonate either side of the connection to steal data. Bidirectional authentication mitigates this risk. |
|
V-256365
|
Medium |
The vCenter Server must restrict access to cryptographic permissions. |
These permissions must be reserved for cryptographic administrators where virtual machine encryption and/or vSAN encryption is in use. Catastrophic data loss can result from poorly administered cryptography. |
|
V-256364
|
Medium |
The vCenter Server must restrict access to the default roles with cryptographic permissions. |
In vSphere, a number of default roles contain permission to perform cryptographic operations such as Key Management Server (KMS) functions and encrypting and decrypting virtual machine disks. These roles must be reserved for cryptographic administrators where virtual machine encryption and/or vSAN encryption is in use.
A new built-in role called... |
|
V-256362
|
Medium |
The vCenter Server must configure the vSAN Datastore name to a unique name. |
A vSAN Datastore name by default is "vsanDatastore". If more than one vSAN cluster is present in vCenter, both datastores will have the same name by default, potentially leading to confusion and manually misplaced workloads. |
|
V-256361
|
Medium |
The vCenter Server must disable or restrict the connectivity between vSAN Health Check and public Hardware Compatibility List (HCL) by use of an external proxy server. |
The vSAN Health Check is able to download the HCL from VMware to check compliance against the underlying vSAN Cluster hosts. To ensure the vCenter server is not directly downloading content from the internet, this functionality must be disabled. If this feature is necessary, an external proxy server must be... |
|
V-256360
|
Medium |
The vCenter server must be configured to send events to a central log server. |
vCenter server generates volumes of security-relevant application-level events. Examples include logins, system reconfigurations, system degradation warnings, and more. To ensure these events are available for forensic analysis and correlation, they must be sent to the syslog and forwarded on to the configured Security Information and Event Management (SIEM) system and/or... |
|
V-256359
|
Medium |
The vCenter Server must protect the confidentiality and integrity of transmitted information by isolating Internet Protocol (IP)-based storage traffic. |
Virtual machines might share virtual switches and virtual local area networks (VLAN) with the IP-based storage configurations.
IP-based storage includes vSAN, Internet Small Computer System Interface (iSCSI), and Network File System (NFS). This configuration might expose IP-based storage traffic to unauthorized virtual machine users. IP-based storage frequently is not encrypted.... |
|
V-256358
|
Medium |
The vCenter Server must use unique service accounts when applications connect to vCenter. |
To not violate nonrepudiation (i.e., deny the authenticity of who is connecting to vCenter), when applications need to connect to vCenter they must use unique service accounts. |
|
V-256357
|
Medium |
The vCenter Server must be isolated from the public internet but must still allow for patch notification and delivery. |
vCenter and the embedded Lifecycle Manager system must never have a direct route to the internet. Despite this, updates and patches sourced from VMware on the internet must be delivered in a timely manner.
There are two methods to accomplish this: a proxy server and the Update Manager Download Service... |
|
V-256356
|
Medium |
The vCenter Server must configure the "vpxuser" password to meet length policy. |
The "vpxuser" password default length is 32 characters. Ensure this setting meets site policies; if not, configure to meet password length policies.
Longer passwords make brute-force password attacks more difficult. The "vpxuser" password is added by vCenter, meaning no manual intervention is normally required. The "vpxuser" password length must never... |
|
V-256355
|
Medium |
The vCenter Server must configure the "vpxuser" auto-password to be changed every 30 days. |
By default, vCenter will change the "vpxuser" password automatically every 30 days. Ensure this setting meets site policies. If it does not, configure it to meet password aging policies.
Note: It is very important the password aging policy is not shorter than the default interval that is set to automatically... |
|
V-256354
|
Medium |
The vCenter Server must not configure all port groups to virtual local area network (VLAN) values reserved by upstream physical switches. |
Certain physical switches reserve certain VLAN IDs for internal purposes and often disallow traffic configured to these values. For example, Cisco Catalyst switches typically reserve VLANs 1001 to 1024 and 4094, while Nexus switches typically reserve 3968 to 4094.
Check with the documentation for the organization's specific switch. Using a... |
|
V-256353
|
Medium |
The vCenter Server must not configure VLAN Trunking unless Virtual Guest Tagging (VGT) is required and authorized. |
When a port group is set to VLAN Trunking, the vSwitch passes all network frames in the specified range to the attached virtual machines without modifying the virtual local area network (VLAN) tags. In vSphere, this is referred to as VGT.
The virtual machine must process the VLAN information itself... |
|
V-256352
|
Medium |
The vCenter Server must configure all port groups to a value other than that of the native virtual local area network (VLAN). |
ESXi does not use the concept of native VLAN. Frames with VLAN specified in the port group will have a tag, but frames with VLAN not specified in the port group are not tagged and therefore will end up belonging to native VLAN of the physical switch.
For example, frames... |
|
V-256351
|
Medium |
The vCenter Server must only send NetFlow traffic to authorized collectors. |
The distributed virtual switch can export NetFlow information about traffic crossing the switch. NetFlow exports are not encrypted and can contain information about the virtual network, making it easier for a man-in-the-middle attack to be executed successfully. If NetFlow export is required, verify that all NetFlow target Internet Protocols (IPs)... |
|
V-256350
|
Medium |
The vCenter Server must set the distributed port group Promiscuous Mode policy to "Reject". |
When promiscuous mode is enabled for a virtual switch, all virtual machines connected to the port group have the potential of reading all packets across that network, meaning only the virtual machines connected to that port group.
Promiscuous mode is disabled by default on the ESXi Server, and this is... |
|
V-256349
|
Medium |
The vCenter Server must set the distributed port group Media Access Control (MAC) Address Change policy to "Reject". |
If the virtual machine operating system changes the MAC address, it can send frames with an impersonated source MAC address at any time. This allows it to stage malicious attacks on the devices in a network by impersonating a network adaptor authorized by the receiving network.
This will prevent virtual... |
|
V-256348
|
Medium |
The vCenter Server must set the distributed port group Forged Transmits policy to "Reject". |
If the virtual machine operating system changes the Media Access Control (MAC) address, the operating system can send frames with an impersonated source MAC address at any time. This allows an operating system to stage malicious attacks on the devices in a network by impersonating a network adaptor authorized by... |
|
V-256346
|
Medium |
The vCenter Server must require an administrator to unlock an account locked due to excessive login failures. |
By requiring that Single Sign-On (SSO) accounts be unlocked manually, the risk of unauthorized access via user password guessing, otherwise known as brute forcing, is reduced. When the account unlock time is set to zero, once an account is locked it can only be unlocked manually by an administrator. |
|
V-256345
|
Medium |
The vCenter server must disable SNMPv1/2 receivers. |
SNMPv3 supports commercial-grade security, including authentication, authorization, access control, and privacy. Previous versions of the protocol contained well-known security weaknesses that were easily exploited. Therefore, SNMPv1/2 receivers must be disabled, while SNMPv3 is configured in another control. vCenter exposes SNMP v1/2 in the UI and SNMPv3 in the CLI. |
|
V-256344
|
Medium |
The vCenter server must enforce SNMPv3 security features where SNMP is required. |
SNMPv3 supports commercial-grade security, including authentication, authorization, access control, and privacy. Previous versions of the protocol contained well-known security weaknesses that were easily exploited. SNMPv3 can be configured for identification and cryptographically based authentication.
SNMPv3 defines a user-based security model (USM) and a view-based access control model (VACM). SNMPv3 USM... |
|
V-256343
|
Medium |
The vCenter Server must disable the Customer Experience Improvement Program (CEIP). |
The VMware CEIP sends VMware anonymized system information that is used to improve the quality, reliability, and functionality of VMware products and services. For confidentiality purposes this feature must be disabled. |
|
V-256342
|
Medium |
The vCenter Server Machine Secure Sockets Layer (SSL) certificate must be issued by a DOD certificate authority. |
Untrusted certificate authorities (CA) can issue certificates, but they may be issued by organizations or individuals that seek to compromise DOD systems or by organizations with insufficient security controls. If the CA used for verifying the certificate is not a DOD-approved CA, trust of this CA has not been established.... |
|
V-256341
|
Medium |
The vCenter Server must compare internal information system clocks at least every 24 hours with an authoritative time server. |
Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. Sources outside of the configured acceptable allowance (drift) may be inaccurate. Additionally,... |
|
V-256340
|
Medium |
vCenter must provide an immediate real-time alert to the system administrator (SA) and information system security officer (ISSO), at a minimum, of all audit failure events requiring real-time alerts. |
It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without a real-time alert, security personnel may be unaware of an impending failure of the audit capability and system operation may be adversely affected.
Alerts provide... |
|
V-256339
|
Medium |
The vCenter Server must be configured to send logs to a central log server. |
vCenter must be configured to send near real-time log data to syslog collectors so information will be available to investigators in the case of a security incident or to assist in troubleshooting. |
|
V-256338
|
Medium |
The vCenter Server must set the interval for counting failed login attempts to at least 15 minutes. |
By limiting the number of failed login attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute forcing, is reduced. Limits are imposed by locking the account. |
|
V-256337
|
Medium |
The vCenter Server must provide an immediate real-time alert to the system administrator (SA) and information system security officer (ISSO), at a minimum, on every Single Sign-On (SSO) account action. |
Once an attacker establishes initial access to a system, they often attempt to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to create a new account. They may also try to hijack an existing account by changing a password or enabling a... |
|
V-256336
|
Medium |
The vCenter Server must manage excess capacity, bandwidth, or other redundancy to limit the effects of information flooding types of denial-of-service (DoS) attacks by enabling Network I/O Control (NIOC). |
DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity.
Managing excess capacity ensures sufficient capacity is available to counter flooding attacks. Employing increased capacity and service redundancy may reduce the... |
|
V-256335
|
Medium |
The vCenter Server users must have the correct roles assigned. |
Users and service accounts must only be assigned privileges they require. Least privilege requires that these privileges must only be assigned if needed to reduce risk of confidentiality, availability, or integrity loss.
Satisfies: SRG-APP-000211, SRG-APP-000233, SRG-APP-000380 |
|
V-256334
|
Medium |
The vCenter Server must terminate vSphere Client sessions after 10 minutes of inactivity. |
Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminating an idle session will also free resources committed by the... |
|
V-256333
|
Medium |
The vCenter Server must enable revocation checking for certificate-based authentication. |
The system must establish the validity of the user-supplied identity certificate using Online Certificate Status Protocol (OCSP) and/or Certificate Revocation List (CRL) revocation checking.
Satisfies: SRG-APP-000175, SRG-APP-000392, SRG-APP-000401, SRG-APP-000403 |
|
V-256332
|
Medium |
The vCenter Server must enforce a 60-day maximum password lifetime restriction. |
Any password, no matter how complex, can eventually be cracked. Therefore, passwords must be changed at specific intervals.
One method of minimizing this risk is to use complex passwords and periodically change them. If the application does not limit the lifetime of passwords and force users to change their passwords,... |
|
V-256330
|
Medium |
The vCenter Server passwords must contain at least one special character. |
Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
Password complexity is one factor in determining how long it takes to... |
|
V-256329
|
Medium |
The vCenter Server passwords must contain at least one numeric character. |
Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
Password complexity is one factor of several that determine how long it... |
|
V-256328
|
Medium |
The vCenter Server passwords must contain at least one lowercase character. |
Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
Password complexity is one factor of several that determine how long it... |
|
V-256327
|
Medium |
The vCenter Server passwords must contain at least one uppercase character. |
Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
Password complexity is one factor of several that determine how long it... |
|
V-256326
|
Medium |
The vCenter Server must prohibit password reuse for a minimum of five generations. |
Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
To meet password policy requirements, passwords must be changed at specific policy-based intervals.
If the information system or application allows the user to consecutively reuse their password when that... |
|
V-256325
|
Medium |
The vCenter Server passwords must be at least 15 characters in length. |
The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised.
Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password length is one factor of several that... |
|
V-256324
|
Medium |
The vCenter Server must require multifactor authentication. |
Without the use of multifactor authentication, the ease of access to privileged functions is greatly increased.
Multifactor authentication requires using two or more factors to achieve authentication.
Factors include:
(i) something a user knows (e.g., password/PIN);
(ii) something a user has (e.g., cryptographic identification device, token); or
(iii) something a... |
|
V-256323
|
Medium |
The vCenter Server must uniquely identify and authenticate users or processes acting on behalf of users. |
To ensure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.
Organizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and any processes acting on behalf of... |
|
V-256322
|
Medium |
vCenter Server plugins must be verified. |
The vCenter Server includes a vSphere Client extensibility framework, which provides the ability to extend the vSphere Client with menu selections or toolbar icons that provide access to vCenter Server add-on components or external, web-based functionality.
vSphere Client plugins or extensions run at the same privilege level as the user.... |
|
V-256321
|
Medium |
The vCenter Server must produce audit records containing information to establish what type of events occurred. |
Without establishing what types of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack. |
|
V-256320
|
Medium |
The vCenter Server must display the Standard Mandatory DOD Notice and Consent Banner before login. |
Display of the DOD-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... |
|
V-256319
|
Medium |
The vCenter Server must enforce the limit of three consecutive invalid login attempts by a user. |
By limiting the number of failed login attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute forcing, is reduced. Limits are imposed by locking the account. |
|
V-256363
|
Low |
The vCenter Server must disable Username/Password and Windows Integrated Authentication. |
All forms of authentication other than Common Access Card (CAC) must be disabled. Password authentication can be temporarily reenabled for emergency access to the local Single Sign-On (SSO) accounts or Active Directory user/pass accounts, but it must be disabled as soon as CAC authentication is functional. |
|
V-256347
|
Low |
The vCenter Server must disable the distributed virtual switch health check. |
Network health check is disabled by default. Once enabled, the health check packets contain information on host#, vds#, and port#, which an attacker would find useful. It is recommended that network health check be used for troubleshooting and turned off when troubleshooting is finished. |
