UCF STIG Viewer Logo

The vRA PostgreSQL database must have the correct ownership on the log files.


Overview

Finding ID Version Rule ID IA Controls Severity
V-89355 VRAU-PG-000100 SV-100005r1_rule Medium
Description
If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. To ensure the veracity of audit data the information system and/or the application must protect audit information from unauthorized modification. This requirement can be achieved through multiple methods that will depend upon system architecture and design. Some commonly employed methods include ensuring log files enjoy the proper file system permissions and limiting log data locations. Applications providing a user interface to audit data will leverage user permissions and roles identifying the user accessing the data and the corresponding rights that the user enjoys in order to make access decisions regarding the modification of audit data. Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity. Modification of database audit data could mask the theft of, or the unauthorized modification of, sensitive data stored in the database.
STIG Date
VMW vRealize Automation 7.x PostgreSQL Security Technical Implementation Guide 2018-10-12

Details

Check Text ( C-89047r1_chk )
At the command prompt, enter the following command:

# ls -l /storage/db/pgdata/pg_log/*.log

If the owner of any log files are not "postgres:users", this is a finding.
Fix Text (F-96097r1_fix)
At the command prompt, enter the following command:

# chown postgres:users /storage/db/pgdata/pg_log/

Replace with files to be modified.