STIGUI
V-253756CAT II — Medium severitySV-253756r961809_rule

MariaDB must generate audit records when categories of information (e.g., classification levels/security levels) are modified.

Rule version MADB-10-010400 · STIG v2 · 2026-08-25

Discussion

Changes in categories of information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected.

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

If category tracking is not required in the database, this is not applicable.

Verify the MariaDB Enterprise Audit plugin is loaded and actively logging:

MariaDB> SHOW GLOBAL STATUS LIKE 'Server_audit_active';

If the MariaDB Enterprise Audit is not active, this is a finding.

Check what filters are in place by running the following as an administrative user:

MariaDB> SELECT * FROM mysql.server_audit_filters;

Verify query_events ALL is included in corresponding audit filters. If not, this is a finding.

Fix

The MariaDB Enterprise Audit plugin can be configured to audit these changes.

Update necessary audit filters to include query_event ALL. Example:

MariaDB> DELETE FROM mysql.server_audit_filters WHERE filtername = 'default';

MariaDB> INSERT INTO mysql.server_audit_filters (filtername, rule) VALUES ('default', JSON_COMPACT( '{ "connect_event": [ "CONNECT", "DISCONNECT" ], "query_event": [ "ALL" ] }' ));

Identifiers

Group ID
V-253756
Group title
SRG-APP-000498-DB-000346
Rule ID
SV-253756r961809_rule
Check ID
C-57208r841791_chk
Fix ID
F-57159r841792_fix