Title

MariaDB must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur. (Cat II impact)

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: CREATE ALTER DROP GRANT REVOKE 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. To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

Check Content

Check what filters are in place by running the following as an administrative user: MariaDB> SELECT * FROM mysql.server_audit_filters; Verify audit filters are correctly configured to log desired actions per user. If not, this is a finding.

Fix Text

Edit the necessary filters to include the desired logging actions. Exact steps vary depending on desired logging. Example named audit filter assigned to specific user: MariaDB> INSERT INTO mysql.server_audit_users (host, user, filtername) VALUES ("%", "user1", "filter_example"); MariaDB> SET GLOBAL server_audit_reload_filters=ON;

Additional Identifiers

Rule ID: SV-253767r961827_rule

Vulnerability ID: V-253767

Group Title: SRG-APP-000504-DB-000355

Expert Comments

CCIs tied to check.

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