VMW vRealize Automation 7.x PostgreSQL Security Technical Implementation Guide

The VMW vRealize Automation 7.x PostgreSQL Security Technical Implementation Guide (V1 R2) has 69 STIG checks. New to STIG checklists? Read What is a STIG checklist?, CKL vs CKLB, and STIG vs SCAP benchmark.

Find STIG checks

69STIG checks

Search filters this STIG's checks locally. Separate terms must all match (use quotes for an exact phrase). A search you ran on the Search page carries over here.

Severity

Version

V1 · R2

CurrentPublished Wed Oct 25 2023 What changed in V1R2

The vRA PostgreSQL database must set the log_statement to all.

VMW vRealize Automation 7.x PostgreSQL Security Technical Implementation Guide

Assessment Title

Rule Text

The vRA PostgreSQL database must set the log_statement to all.

Description

Discussion Text

The removal of security objects from the database/DBMS would seriously degrade a system's information assurance posture. If such an event occurs, it must be logged.

New to STIG checklists? Read What is a STIG checklist? and CKL vs CKLB.

Objective

V-240322

Rule

SV-240322r879872_rule

Severity

medium

Rule Version

VRAU-PG-000405

Documentable

false

IA Controls

NIST SP 800-53

Rev 5

Assessment Procedure

Check Text

At the command prompt, execute the following command:

# grep '^\s*log_statement\b' /storage/db/pgdata/postgresql.conf

If "log_statement" is not all, this is a finding.

Implementation Procedure

Fix Text

At the command prompt, execute the following commands:

# /opt/vmware/vpostgres/current/bin/psql -U postgres -c "ALTER SYSTEM SET log_statement TO 'all';"
# /opt/vmware/vpostgres/current/bin/psql -U postgres -c "SELECT pg_reload_conf();"

STIG check 47 of 69 in the VMW vRealize Automation 7.x PostgreSQL STIG checklist

← Previous · V-240321The vRA PostgreSQL database must set the log_statement to all.Next · V-240323 →The vRA PostgreSQL database must set the log_statement to all.