VMware vSphere 6.7 PostgreSQL Security Technical Implementation Guide

Overview

Version	Date	Finding Count (22)			Downloads
1	2021-03-18 2021-04-15 2021-04-15	CAT I (High): 4	CAT II (Med): 18	CAT III (Low): 0	Excel	JSON	XML

STIG Description
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: disa.stig_spt@mail.mil.

Available Profiles

Classified	Public	Sensitive
I - Mission Critical Classified	I - Mission Critical Public	I - Mission Critical Sensitive	II - Mission Support Classified	II - Mission Support Public	II - Mission Support Sensitive	III - Administrative Classified	III - Administrative Public	III - Administrative Sensitive

Findings (MAC II - Mission Support Sensitive)

Finding ID	Severity	Title	Description
V-239207	High	VMware Postgres must use FIPS 140-2 approved TLS ciphers.	Use of weak or not validated cryptographic algorithms undermines the purposes of using encryption and digital signatures to protect data. Weak algorithms can be easily broken, and not validated...
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-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 and...
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. Organizational...
V-239210	Medium	Data from the vPostgres database must be protected from unauthorized transfer.	Applications, including DBMSs, must prevent unauthorized and unintended information transfer via shared system resources. Data used for the development and testing of applications often involves...
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-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-239213	Medium	VMware Postgres must be configured to log to stderr.	Organizations are required to use a central log management system so, under normal conditions, the audit space allocated to the DBMS on its own server will not be an issue. However, space will...
V-239214	Medium	Rsyslog must be configured to monitor VMware Postgres logs.	Organizations are required to use a central log management system, so, under normal conditions, the audit space allocated to the DBMS on its own server will not be an issue. However, space will...
V-239215	Medium	VMware Postgres must use Coordinated Universal Time (UTC) for log timestamps.	If time stamps are not applied consistently and there is no common time reference, it is difficult to perform forensic analysis. Time stamps generated by the DBMS must include date and time. Time...
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-239217	Medium	The vPostgres database security updates and patches must be installed in a timely manner in accordance with site policy.	Security flaws with software applications, including database management systems, are discovered daily. Vendors are constantly updating and patching their products to address newly discovered...
V-239209	Medium	VMware Postgres must not allow schema access to unauthorized accounts.	An isolation boundary provides access control and protects the integrity of the hardware, software, and firmware that perform security functions. Security functions are the hardware, software,...
V-239208	Medium	VMware Postgres must write log entries to disk prior to returning operation success or failure.	Failure to a known state can address safety or security in accordance with the mission/business needs of the organization. Failure to a known secure state helps prevent a loss of confidentiality,...
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 the DBMS 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...
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-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-239199	Medium	VMware Postgres must be configured to overwrite older logs when necessary.	It is critical that when the DBMS is at risk of failing to process audit logs as required, it take action to mitigate the failure. Audit processing failures include software/hardware errors,...
V-239198	Medium	VMware Postgres configuration files must not be accessible by unauthorized users.	Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent or interfere with the auditing of critical...
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. Audit...
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...