What changed in VMW vRealize Automation 7.x PostgreSQL STIG V1R2V1R2 changes

VMW vRealize Automation 7.x PostgreSQL STIG V1R2 (2023-10-25) replaced V1R1 (2018-09-28): 69 checks added, 69 removed. It has 69 checks, against 69 in V1R1.

V1R2 checklistV1R1 checklist Compare V1R1 and V1R2 in STIG Compare

  • 69 added
  • 69 removed
  • 0 updated

Added in V1R2 (69)

  • V-240276CAT IIvRA PostgreSQL database log file data must contain required data elements.
  • V-240277CAT IIThe vRA PostgreSQL configuration file must not be accessible by unauthorized users.
  • V-240278CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-240279CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-240280CAT IIvRA PostgreSQL database log file data must contain required data elements.
  • V-240281CAT IIvRA PostgreSQL database log file data must contain required data elements.
  • V-240282CAT IIvRA PostgreSQL database log file data must contain required data elements.
  • V-240283CAT IIvRA PostgreSQL database log file data must contain required data elements.
  • V-240284CAT IIvRA PostgreSQL database log file data must contain required data elements.
  • V-240285CAT IIvRA PostgreSQL database log file data must contain required data elements.
  • V-240286CAT IIvRA PostgreSQL database log file data must contain required data elements.
  • V-240287CAT IIIvRA PostgreSQL database must have log_truncate_on_rotation enabled.
  • V-240288CAT IIThe vRA PostgreSQL database must have the correct permissions on the log files.
  • V-240289CAT IIThe vRA PostgreSQL database must have the correct ownership on the log files.
  • V-240290CAT IIThe vRA PostgreSQL database must have the correct group-ownership on the log files.
  • V-240291CAT IIThe vRA PostgreSQL configuration files must have the correct permissions.
  • V-240292CAT IIThe vRA PostgreSQL configuration files must have the correct ownership.
  • V-240293CAT IIThe vRA PostgreSQL configuration files must have the correct group-ownership.
  • V-240294CAT IIvRA PostgreSQL database objects must only be accessible to the postgres account.
  • V-240295CAT IIThe vRA PostgreSQL database must limit modify privileges to authorized accounts.
  • V-240296CAT IIThe vRA PostgreSQL database must not contain sample data.
  • V-240297CAT IIThe vRA PostgreSQL database must be limited to authorized accounts.
  • V-240298CAT IIThe vRA PostgreSQL database must use md5 for authentication.
  • V-240299CAT IIThe vRA PostgreSQL database must be configured to use ssl.
  • V-240300CAT IIThe vRA PostgreSQL database must complete writing log entries prior to returning results.
  • V-240301CAT IIThe vRA PostgreSQL must not allow access to unauthorized accounts.
  • V-240302CAT IIData from the vRA PostgreSQL database must be protected from unauthorized transfer.
  • V-240303CAT IIThe vRA PostgreSQL error file must be protected from unauthorized access.
  • V-240304CAT IIThe vRA PostgreSQL database must have log collection enabled.
  • V-240305CAT IIThe vRA PostgreSQL database must be configured to use a syslog facility.
  • V-240306CAT IIThe vRA PostgreSQL database must be configured to use a syslog facility.
  • V-240307CAT IIThe vRA PostgreSQL database must use UTC for log timestamps.
  • V-240308CAT IIvRA PostgreSQL database log file data must contain required data elements.
  • V-240309CAT IIThe DBMS must enforce access restrictions associated with changes to the configuration of the DBMS or database(s).
  • V-240310CAT IIvRA PostgreSQL database must be configured to validate character encoding to UTF-8.
  • V-240311CAT IThe vRA PostgreSQL database security updates and patches must be installed in a timely manner in accordance with site policy.
  • V-240312CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-240313CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-240314CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-240315CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-240316CAT IIThe DBMS must generate audit records when privileges/permissions are modified.
  • V-240317CAT IIThe DBMS must generate audit records when unsuccessful attempts to modify privileges/permissions occur.
  • V-240318CAT IIThe DBMS must generate audit records when security objects are modified.
  • V-240319CAT IIThe DBMS must generate audit records when unsuccessful attempts to modify security objects occur.
  • V-240320CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-240321CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-240322CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-240323CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-240324CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-240325CAT IIThe vRA PostgreSQL database must set log_connections to on.
  • V-240326CAT IIThe vRA PostgreSQL database must set the log_min_messages to warning.
  • V-240327CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-240328CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-240329CAT IIThe vRA PostgreSQL database must set log_connections to on.
  • V-240330CAT IIThe vRA PostgreSQL database must set log_connections to on.
  • V-240331CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-240332CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-240333CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-240334CAT IThe vRA PostgreSQL database must use FIPS 140-2 ciphers.
  • V-240335CAT IThe vRA PostgreSQL database must use FIPS 140-2 ciphers.
  • V-240336CAT IThe vRA PostgreSQL database must use FIPS 140-2 ciphers.
  • V-240337CAT IIThe vRA PostgreSQL database must be configured to use a syslog facility.
  • V-240338CAT IIvRA PostgreSQL must have the latest approved security-relevant software updates installed.
  • V-240339CAT IThe DBMS must use NIST FIPS 140-2 validated cryptographic modules for cryptographic operations.
  • V-240340CAT IIvRA Postgres must be configured to use the correct port.
  • V-240341CAT IIThe vRA PostgreSQL database must have log collection enabled.
  • V-240342CAT IIvRA Postgres must be configured to use the correct port.
  • V-240343CAT IIvRA PostgreSQL must limit the number of connections.
  • V-258453CAT IThe version of vRealize Automation 7.x PostgreSQL running on the system must be a supported version.

Removed since V1R1 (69)

  • V-89327CAT IIvRA PostgreSQL database log file data must contain required data elements.
  • V-89329CAT IIThe vRA PostgreSQL configuration file must not be accessible by unauthorized users.
  • V-89331CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-89333CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-89335CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-89337CAT IIvRA PostgreSQL database log file data must contain required data elements.
  • V-89339CAT IIvRA PostgreSQL database log file data must contain required data elements.
  • V-89341CAT IIvRA PostgreSQL database log file data must contain required data elements.
  • V-89343CAT IIvRA PostgreSQL database log file data must contain required data elements.
  • V-89345CAT IIvRA PostgreSQL database log file data must contain required data elements.
  • V-89347CAT IIvRA PostgreSQL database log file data must contain required data elements.
  • V-89349CAT IIvRA PostgreSQL database log file data must contain required data elements.
  • V-89351CAT IIIvRA PostgreSQL database must have log_truncate_on_rotation enabled.
  • V-89353CAT IIThe vRA PostgreSQL database must have the correct permissions on the log files.
  • V-89355CAT IIThe vRA PostgreSQL database must have the correct ownership on the log files.
  • V-89357CAT IIThe vRA PostgreSQL database must have the correct group-ownership on the log files.
  • V-89359CAT IIThe vRA PostgreSQL configuration files must have the correct permissions.
  • V-89361CAT IIThe vRA PostgreSQL configuration files must have the correct ownership.
  • V-89363CAT IIThe vRA PostgreSQL configuration files must have the correct group-ownership.
  • V-89365CAT IIvRA PostgreSQL database objects must only be accessible to the postgres account.
  • V-89367CAT IIThe vRA PostgreSQL database must limit modify privileges to authorized accounts.
  • V-89369CAT IIThe vRA PostgreSQL database must not contain sample data.
  • V-89371CAT IIThe vRA PostgreSQL database must be limited to authorized accounts.
  • V-89373CAT IIThe vRA PostgreSQL database must use md5 for authentication.
  • V-89375CAT IIThe vRA PostgreSQL database must be configured to use ssl.
  • V-89377CAT IIThe vRA PostgreSQL database must complete writing log entries prior to returning results.
  • V-89379CAT IIThe vRA PostgreSQL must not allow access to unauthorized accounts.
  • V-89381CAT IIData from the vRA PostgreSQL database must be protected from unauthorized transfer.
  • V-89383CAT IIThe vRA PostgreSQL error file must be protected from unauthorized access.
  • V-89385CAT IIThe vRA PostgreSQL database must have log collection enabled.
  • V-89387CAT IIThe vRA PostgreSQL database must be configured to use a syslog facility.
  • V-89389CAT IIThe vRA PostgreSQL database must be configured to use a syslog facility.
  • V-89391CAT IIThe vRA PostgreSQL database must use UTC for log timestamps.
  • V-89393CAT IIvRA PostgreSQL database log file data must contain required data elements.
  • V-89395CAT IIThe DBMS must enforce access restrictions associated with changes to the configuration of the DBMS or database(s).
  • V-89397CAT IIvRA PostgreSQL database must be configured to validate character encoding to UTF-8.
  • V-89399CAT IThe vRA PostgreSQL database security updates and patches must be installed in a timely manner in accordance with site policy.
  • V-89401CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-89403CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-89405CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-89407CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-89409CAT IIThe DBMS must generate audit records when privileges/permissions are modified.
  • V-89411CAT IIThe DBMS must generate audit records when unsuccessful attempts to modify privileges/permissions occur.
  • V-89413CAT IIThe DBMS must generate audit records when security objects are modified.
  • V-89415CAT IIThe DBMS must generate audit records when unsuccessful attempts to modify security objects occur.
  • V-89417CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-89419CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-89421CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-89423CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-89425CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-89427CAT IIThe vRA PostgreSQL database must set log_connections to on.
  • V-89429CAT IIThe vRA PostgreSQL database must set the log_min_messages to warning.
  • V-89431CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-89433CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-89435CAT IIThe vRA PostgreSQL database must set log_connections to on.
  • V-89437CAT IIThe vRA PostgreSQL database must set log_connections to on.
  • V-89439CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-89441CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-89443CAT IIThe vRA PostgreSQL database must set the log_statement to all.
  • V-89445CAT IThe vRA PostgreSQL database must use FIPS 140-2 ciphers.
  • V-89447CAT IThe vRA PostgreSQL database must use FIPS 140-2 ciphers.
  • V-89449CAT IThe vRA PostgreSQL database must use FIPS 140-2 ciphers.
  • V-89451CAT IIThe vRA PostgreSQL database must be configured to use a syslog facility.
  • V-89453CAT IIvRA PostgreSQL must have the latest approved security-relevant software updates installed.
  • V-89455CAT IThe DBMS must use NIST FIPS 140-2 validated cryptographic modules for cryptographic operations.
  • V-89457CAT IIvRA Postgres must be configured to use the correct port.
  • V-89459CAT IIThe vRA PostgreSQL database must have log collection enabled.
  • V-89461CAT IIvRA Postgres must be configured to use the correct port.
  • V-89463CAT IIvRA PostgreSQL must limit the number of connections.

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 V1R2 no longer has.

Comparing other releases, or this one against an older release? Pick any two in STIG Compare.