EnterpriseDB Postgres Advanced Server (EPAS) STIG Version Comparison

There are 4 differences between versions v1 r1 (Dec. 13, 2023) (the "left" version) and v2 r1 (July 24, 2024) (the "right" version).

Check EPAS-00-007700 was removed from the benchmark in the "right" version. The text below reflects the old wording.

This check's original form is available here.

Title

The EDB Postgres Advanced Server must utilize centralized management of the content captured in audit records generated by all components of the EDB Postgres Advanced Server.

Check Content

If a centralized log collecting tool such as Postgres Enterprise Manager (PEM) is not installed and configured to automatically collect audit logs, this is a finding. Review the system documentation for a description of how audit records are off-loaded and how local audit log space is managed.

Discussion

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 content captured in audit records must be managed from a central location (necessitating automation). Centralized management of audit records and logs provides for efficiency in maintenance and management of records, as well as the backup and archiving of those records. The DBMS may write audit records to database tables, to files in the file system, to other kinds of local repository, or directly to a centralized log management system. Whatever the method used, it must be compatible with off-loading the records to the centralized system.

Fix

Install a centralized log collecting tool and configure it as instructed in its documentation. If using PEM Log Manager, find the instructions here: https://www.enterprisedb.com/docs/pem/latest/monitoring_performance/log_manager/