STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Crunchy Data PostgreSQL Security Technical Implementation Guide

V-233589

CAT II (Medium)

PostgreSQL must initiate session auditing upon startup.

Rule ID

SV-233589r960888_rule

STIG

Crunchy Data PostgreSQL Security Technical Implementation Guide

Version

V3R1

CCIs

CCI-001464

Discussion

Session auditing is for use when a user's activities are under investigation. To ensure the capture of all activity during those periods when session auditing is in use, it needs to be in operation for the whole time PostgreSQL is running.

Check Content

As the database administrator (shown here as "postgres"), check the current settings by running the following SQL: 

$ sudo su - postgres 
$ psql -c "SHOW shared_preload_libraries" 

If pgaudit is not in the current setting, this is a finding. 

As the database administrator (shown here as "postgres"), check the current settings by running the following SQL: 

$ psql -c "SHOW log_destination" 

If stderr or syslog are not in the current setting, this is a finding.

Fix Text

Configure PostgreSQL to enable auditing.

To ensure logging is enabled, review supplementary content APPENDIX-C for instructions on enabling logging.

For session logging, using pgaudit is recommended. For instructions on how to setup pgaudit, see supplementary content APPENDIX-B.