CD12-00-012600 - PostgreSQL must generate audit records when successful accesses to objects occur.

Information

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 a SQL environment, types of access include, but are not necessarily limited to:

SELECT
INSERT
UPDATE
DELETE
EXECUTE

Solution

Note: The following instructions use the PGDATA and PGVER environment variables. See supplementary content APPENDIX-F for instructions on configuring PGDATA and APPENDIX-H for PGVER. To ensure logging is enabled, review supplementary content APPENDIX-C for instructions on enabling logging.

If logging is enabled, the following configurations must be made to log unsuccessful connections, date/time, username, and session identifier.

As the database administrator (shown here as 'postgres'), edit postgresql.conf:

$ sudo su - postgres
$ vi ${PGDATA?}/postgresql.conf

Edit the following parameters:

log_connections = on
log_line_prefix = '< %m %u %c: >'
pgaudit.log = 'read, write'

Where:
* %m is the time and date
* %u is the username
* %c is the session ID for the connection

As the system administrator, reload the server with the new configuration:

$ sudo systemctl reload postgresql-${PGVER?}

Item Details

Audit Name: DISA STIG Crunchy Data PostgreSQL DB v3r1

Category: AUDIT AND ACCOUNTABILITY

Plugin: PostgreSQLDB

Control ID: 66e8c04c51fde079a8a12222923d757335202f2852fd3ebbca882aa1357200b8

Detections

Analytics

CD12-00-012600 - PostgreSQL must generate audit records when successful accesses to objects occur.

Information

Solution

See Also

Item Details