Audit records must be generated when unsuccessful attempts to modify categorized information (e.g., classification levels/security levels) occur.

From EDB Postgres Advanced Server Security Technical Implementation Guide

Part of SRG-APP-000498-DB-000347

Associated with: CCI-000172

SV-83693r2_rule Audit records must be generated when unsuccessful attempts to modify categorized information (e.g., classification levels/security levels) occur.

Vulnerability discussion

Changes in categorized information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected.To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.For detailed information on categorizing information, refer to FIPS Publication 199, Standards for Security Categorization of Federal Information and Information Systems, and FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems.

Check content

Review the system documentation to determine whether it is required to track categorized information, such as classification or sensitivity level. If it is not, this is not applicable (NA). Execute the following SQL as enterprisedb: SHOW edb_audit_statement; 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 enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

Pro Tips

Powered by sagemincer