Detections
Analytics

CD16-00-011200 - PostgreSQL must generate audit records when successful logons or connections occur.

Information

For completeness of forensic analysis, it is necessary to track who/what (a user or other principal) logs on to PostgreSQL.

Solution

Note: The following instructions use the PGDATA and PGVER environment variables. Refer to APPENDIX-F for instructions on configuring PGDATA and APPENDIX-H for PGVER.

To ensure logging is enabled, see the instructions in the supplementary content APPENDIX-C.

If logging is enabled the following configurations must be made to log 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 as such:

log_connections = on
log_line_prefix = '< %m %u %d %c: >'

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

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

$ sudo systemctl reload postgresql-${PGVER?}

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_CD_Postgres_16_V1R2_STIG.zip

Item Details

Category: AUDIT AND ACCOUNTABILITY

References: 800-53|AU-12c., CAT|II, CCI|CCI-000172, Rule-ID|SV-261956r1000975_rule, STIG-ID|CD16-00-011200, Vuln-ID|V-261956

Plugin: PostgreSQLDB

Control ID: 1c73a579eb9ee02ef5a05d31cf190e6915d34ca66fb02b2d0ead2793b005f75b