MariaDB must generate audit records for all direct access to the database(s).
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-253772 | MADB-10-012000 | SV-253772r961839_rule | CCI-000172 | medium |
| Description | ||||
| In this context, direct access is any query, command, or call to MariaDB that comes from any source other than the application(s) that it supports. Examples would be the command line or a database management utility program. The intent is to capture all activity from administrative and nonstandard sources. | ||||
| STIG | Date | |||
| MariaDB Enterprise 10.x Security Technical Implementation Guide | 2024-12-05 | |||
Details
Check Text (C-253772r961839_chk)
Check what filters are in place by running the following as an administrative user:
MariaDB> SELECT * FROM mysql.server_audit_filters;
Verify connect_events include connect in audit filters. If not, this is a finding.
Fix Text (F-57175r841840_fix)
Edit the necessary filters to include connect_events connect. 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"
}'
));