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 just now
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to EnterpriseDB Postgres Advanced Server (EPAS) Security Technical Implementation Guide

V-259321

CAT II (Medium)

The EDB Postgres Advanced Server must generate audit records when concurrent logons/connections by the same user from different workstations occur.

Rule ID

SV-259321r961833_rule

STIG

EnterpriseDB Postgres Advanced Server (EPAS) Security Technical Implementation Guide

Version

V2R1

CCIs

CCI-000172

Discussion

For completeness of forensic analysis, it is necessary to track who logs on to the DBMS. Concurrent connections by the same user from multiple workstations may be valid use of the system; or such connections may be due to improper circumvention of the requirement to use the CAC for authentication; or they may indicate unauthorized account sharing; or they may be because an account has been compromised. If multiple concurrent logons by a given user can be reliably reconstructed from the log entries for other events (logons/connections; voluntary and involuntary disconnections), then it is not mandatory to create additional log entries specifically for this.

Check Content

Execute the following SQL as the "enterprisedb" operating system user:

> psql edb -c "SHOW edb_audit_connect"

If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix Text

Execute the following SQL as the "enterprisedb" operating system user:

> psql edb -c "ALTER SYSTEM SET edb_audit_connect = 'all'"
> psql edb -c "ALTER SYSTEM SET edb_audit_disconnect = 'all'"
> psql edb -c "SELECT pg_reload_conf()"

or

Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.