Skip to main content
CUI

Documentation - V-261944

V-261944

Crunchy Data Postgres 16 Security Technical Implementation Guide

CAT II

Title

PostgreSQL must generate audit records when privileges/permissions are modified.

Description

<VulnDiscussion>Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized elevation or restriction of privileges could go undetected. Elevated privileges give users access to information and functionality that they should not have; restricted privileges wrongly deny access to authorized users. In an SQL environment, modifying permissions is typically done via the GRANT, REVOKE, and DENY commands.</VulnDiscussion><FalsePosi...

Fix Text (Documentation Requirement)

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. PostgreSQL can be configured to audit these requests using pgaudit. Refer to supplementary content APPENDIX-B for documentation on installing pgaudit. With pgaudit installed, the following configurations can be made: $ sudo su - postgres $ vi ${PGDATA?}/postgresql.conf Add the following parameters (or edit existing parameters): pgaudit.log='role' As the system administrator, reload the server with the new configuration: $ sudo systemctl reload postgresql-${PGVER?}

Documentation Status

Cancel
CUI