The EDB Postgres Advanced Server must generate audit records when unsuccessful accesses to objects occur.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-69073	PPS9-00-012500	SV-83677r1_rule		Medium

Description
Without tracking all or selected types of access to all or selected objects (tables, views, procedures, functions, etc.), it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. In an SQL environment, types of access include, but are not necessarily limited to: SELECT INSERT UPDATE DELETE EXECUTE To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

Description

Without tracking all or selected types of access to all or selected objects (tables, views, procedures, functions, etc.), it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. In an SQL environment, types of access include, but are not necessarily limited to: SELECT INSERT UPDATE DELETE EXECUTE To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

STIG	Date
EDB Postgres Advanced Server Security Technical Implementation Guide	2016-08-19

Details

Check Text ( C-69547r1_chk )
Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all", this is a finding.

Fix Text (F-75259r1_fix)
Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf();