The DBMS must generate audit records for all privileged activities or other system-level access.

From Database Security Requirements Guide

Part of SRG-APP-000504-DB-000354

Associated with: CCI-000172

SV-72545r1_rule The DBMS must generate audit records for all privileged activities or other system-level access.

Vulnerability discussion

Without tracking privileged activity, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. System documentation should include a definition of the functionality considered privileged.A privileged function in this context is any operation that modifies the structure of the database, its built-in logic, or its security settings. This would include all Data Definition Language (DDL) statements and all security-related statements. In an SQL environment, it encompasses, but is not necessarily limited to:CREATEALTERDROPGRANTREVOKEDENYThere may also be Data Manipulation Language (DML) statements that, subject to context, should be regarded as privileged. Possible examples in SQL include:TRUNCATE TABLE;DELETE, orDELETE affecting more than n rows, for some n, orDELETE without a WHERE clause;UPDATE orUPDATE affecting more than n rows, for some n, orUPDATE without a WHERE clause;any SELECT, INSERT, UPDATE, or DELETE to an application-defined security table executed by other than a security principal.Depending on the capabilities of the DBMS and the design of the database and associated applications, audit logging may be achieved by means of DBMS auditing features, database triggers, other mechanisms, or a combination of these.Note that it is particularly important to audit, and tightly control, any action that weakens the implementation of this requirement itself, since the objective is to have a complete audit trail of all administrative activity.

Check content

Review DBMS documentation to verify that authorized administrative users can designate actions as privileged and that audit records can be produced when privileged actions occur. If the DBMS is not capable of this, this is a finding. Review the system documentation to obtain the definition of the database/DBMS functionality considered privileged in the context of the system in question. Review the DBMS/database security and audit configurations and/or other means used to implement audit logging. If audit logging covers at least all of the actions defined as privileged, this is not a finding; otherwise, this is a finding.

Fix text

Deploy a DBMS capable of producing the required audit records when privileged actions occur. Configure the DBMS to produce audit records when privileged actions occur.

Pro Tips

Powered by sagemincer