| V-239207 ||High ||VMware Postgres must use FIPS 140-2 approved TLS ciphers. ||Use of weak or unvalidated cryptographic algorithms undermines the purposes of using encryption and digital signatures to protect data. Weak algorithms can be broken, and unvalidated cryptographic... |
| V-239205 ||High ||VMware Postgres must be configured to use TLS. ||The DoD standard for authentication is DoD-approved PKI certificates. Authentication based on user ID and password may be used only when it is not possible to employ a PKI certificate.
In such... |
| V-239206 ||High ||VMware Postgres must enforce authorized access to all PKI private keys. ||The DoD standard for authentication is DoD-approved PKI certificates. PKI certificate-based authentication is performed by requiring the certificate holder to cryptographically prove possession of... |
| V-239204 ||High ||VMware Postgres must require authentication on all connections. ||To ensure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.
VMware Postgres... |
| V-239209 ||Medium ||VMware Postgres must not allow schema access to unauthorized accounts. ||Database management systems typically separate security functionality from non-security functionality via separate databases or schemas. Database objects or code implementing security... |
| V-239208 ||Medium ||VMware Postgres must write log entries to disk prior to returning operation success or failure. ||Failure to a known secure state helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of the information system or a component of the system. Preserving ... |
| V-239203 ||Medium ||VMware Postgres must be configured to use the correct port. ||To prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or... |
| V-239202 ||Medium ||VMware Postgres must limit modify privileges to authorized accounts. ||If VMware Postgres were to allow any user to make changes to database structure or logic, those changes might be implemented without undergoing the appropriate testing and approvals that are part... |
| V-239212 ||Medium ||VMware Postgres must have log collection enabled. ||Without the ability to centrally manage the content captured in the audit records, identification, troubleshooting, and correlation of suspicious behavior would be difficult and could lead to a... |
| V-239200 ||Medium ||VMware Postgres database must protect log files from unauthorized access and modification. ||If audit data were to become compromised, competent forensic analysis and discovery of the true source of potentially malicious system activity would be difficult, if not impossible, to achieve.... |
| V-239215 ||Medium ||VMware Postgres must use Coordinated Universal Time (UTC) for log timestamps. ||If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis. Time stamps generated by VMware Postgres must include date and time... |
| V-239213 ||Medium ||VMware Postgres must be configured to log to stderr. ||Without the ability to centrally manage the content captured in the audit records, identification, troubleshooting, and correlation of suspicious behavior would be difficult and could lead to a... |
| V-239199 ||Medium ||VMware Postgres must be configured to overwrite older logs when necessary. ||Without proper configuration, log files for VMware Postgres can grow without bound, filling the partition and potentially affecting the availability of the VCSA. One part of this configuration is... |
| V-239198 ||Medium ||VMware Postgres configuration files must not be accessible by unauthorized users. ||VMware Postgres has several configuration files that directly control the security posture of the DBMS. Protecting these files from unauthorized access and modification is fundamental to ensuring... |
| V-239216 ||Medium ||VMware Postgres must set client-side character encoding to UTF-8. ||A common vulnerability is unplanned behavior when invalid inputs are received. This requirement guards against adverse or unintended system behavior caused by invalid inputs, where information... |
| V-239211 ||Medium ||VMware Postgres must provide non-privileged users with minimal error information. ||Any DBMS or associated application providing too much information in error messages on the screen or printout risks compromising the data and security of the system. The structure and content of... |
| V-239214 ||Medium ||Rsyslog must be configured to monitor VMware Postgres logs. ||For performance reasons, rsyslog file monitoring is preferred over configuring VMware Postgres to send events to a syslog facility. Without ensuring that logs are created, that rsyslog configs are... |
| V-239197 ||Medium ||VMware Postgres log files must contain required fields. ||Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
As an... |
| V-239201 ||Medium ||All VCDB tables must be owned by the "vc" user account. ||Within the database, object ownership implies full privileges to the owned object, including the privilege to assign access to the owned objects to other subjects. Database functions and... |
| V-239196 ||Medium ||VMware Postgres must limit the number of connections. ||Database management includes the ability to control the number of users and user sessions utilizing a DBMS. Unlimited concurrent connections to the DBMS could allow a successful denial-of-service... |