UCF STIG Viewer Logo

PostgreSQL must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements.


Finding ID Version Rule ID IA Controls Severity
V-214066 PGS9-00-002100 SV-214066r508027_rule Medium
In order to ensure sufficient storage capacity for the audit logs, PostgreSQL must be able to allocate audit record storage capacity. Although another requirement (SRG-APP-000515-DB-000318) mandates that audit data be off-loaded to a centralized log management system, it remains necessary to provide space on the database server to serve as a buffer against outages and capacity limits of the off-loading mechanism. The task of allocating audit record storage capacity is usually performed during initial installation of PostgreSQL and is closely associated with the DBA and system administrator roles. The DBA or system administrator will usually coordinate the allocation of physical drive space with the application owner/installer and the application will prompt the installer to provide the capacity information, the physical location of the disk, or both. In determining the capacity requirements, consider such factors as: total number of users; expected number of concurrent users during busy periods; number and type of events being monitored; types and amounts of data being captured; the frequency/speed with which audit records are off-loaded to the central log management system; and any limitations that exist on PostgreSQL's ability to reuse the space formerly occupied by off-loaded records.
PostgreSQL 9.x Security Technical Implementation Guide 2022-06-13


Check Text ( C-15282r360829_chk )
Investigate whether there have been any incidents where PostgreSQL ran out of audit log space since the last time the space was allocated or other corrective measures were taken.

If there have been incidents where PostgreSQL ran out of audit log space, this is a finding.
Fix Text (F-15280r360830_fix)
Allocate sufficient audit file/table space to support peak demand.