VMware vSphere 6.7 PostgreSQL Security Technical Implementation Guide


This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: [email protected]


Version / Release: V1R1

Published: 2021-04-15

Updated At: 2021-05-02 21:04:35




Severity Open Not Reviewed Not Applicable Not a Finding
Overall 0 0 0 0
Low 0 0 0 0
Medium 0 0 0 0
High 0 0 0 0
Drop CKL or SCAP (XCCDF) results here.

    Vuln Rule Version CCI Severity Title Description Status Finding Details Comments
    SV-239196r717045_rule VCPG-67-000001 CCI-000054 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 (DoS) attack by exhausting connection resources, and a syst
    SV-239197r717050_rule VCPG-67-000002 CCI-000169 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 embedded database that is only accessible via localhost, VMw
    SV-239198r717049_rule VCPG-67-000003 CCI-000171 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 the security of VMware Postgres. Misconfigured audits can
    SV-239199r717051_rule VCPG-67-000004 CCI-000140 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 to ensure that the logging subsystem overwrites, rather tha
    SV-239200r717052_rule VCPG-67-000005 CCI-000162 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. In addition, access to audit records provides information an
    SV-239201r717053_rule VCPG-67-000008 CCI-001499 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 procedures can be coded using definer's rights. This allows anyone w
    SV-239202r717054_rule VCPG-67-000009 CCI-001499 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 of a robust change management process. Accordingly, only q
    SV-239203r678982_rule VCPG-67-000011 CCI-000382 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 restrict unused or unnecessary physical and logical ports/proto
    SV-239204r717055_rule VCPG-67-000012 CCI-000764 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 client authentication is configured in "pg_hba.conf". In thi
    SV-239205r717059_rule VCPG-67-000013 CCI-000197 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 cases, passwords need to be protected at all times, and encry
    SV-239206r717057_rule VCPG-67-000014 CCI-000186 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 the corresponding private key. If the private key is stol
    SV-239207r717058_rule VCPG-67-000015 CCI-000803 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 modules may not implement algorithms correctly. Unapproved
    SV-239208r717060_rule VCPG-67-000016 CCI-001665 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 system state information helps to facilitate system restart a
    SV-239209r717061_rule VCPG-67-000017 CCI-001084 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 functionality should not be commingled with objects or code implementin
    SV-239211r717062_rule VCPG-67-000019 CCI-001312 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 error messages must contain the minimal amount of informatio
    SV-239212r717063_rule VCPG-67-000020 CCI-001844 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 delayed or incomplete analysis of an ongoing attack. The con
    SV-239213r717065_rule VCPG-67-000021 CCI-001855 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 delayed or incomplete analysis of an ongoing attack. The con
    SV-239214r717064_rule VCPG-67-000022 CCI-001855 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 created, and that those configs are loaded, the log file m
    SV-239215r717066_rule VCPG-67-000023 CCI-001890 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 expressed in UTC, a modern continuation of Greenwich Mean
    SV-239216r717067_rule VCPG-67-000024 CCI-002754 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 system responses to the invalid input may be disruptive or cau