Title

The EDB Postgres Advanced Server must protect against a user falsely repudiating having performed organization-defined actions. (Cat II impact)

Discussion

Nonrepudiation of actions taken is required in order to maintain data integrity. Examples of particular actions taken by individuals include creating information, sending a message, approving information (e.g., indicating concurrence or signing a contract), and receiving a message. Nonrepudiation protects against later claims by a user of not having created, modified, or deleted a particular data item or collection of data in the database. In designing a database, the organization must define the types of data and the user actions that must be protected from repudiation. The implementation must then include building audit features into the application data tables, and configuring the DBMS' audit tools to capture the necessary audit trail. Design and implementation also must ensure that applications pass individual user identification to the DBMS, even where the application connects to the DBMS with a standard, group account.

Check Content

Execute the following SQL as the "enterprisedb" operating system user: > psql edb -c "SHOW edb_audit" If the result is not "csv" or "xml", this is a finding.

Fix Text

Execute the following SQL as the "enterprisedb" operating system user: > psql edb -c "ALTER SYSTEM SET edb_audit = csv" > psql edb -c "SELECT pg_reload_conf()" or > psql edb -c "ALTER SYSTEM SET edb_audit = xml" > psql edb -c "SELECT pg_reload_conf()"

Additional Identifiers

Rule ID: SV-259213r938692_rule

Vulnerability ID: V-259213

Group Title: SRG-APP-000080-DB-000063

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.