STIGQter STIGQter: STIG Summary: MariaDB Enterprise 10.x Security Technical Implementation Guide Version: 2 Release: 5 Benchmark Date: 01 Apr 2026:

MariaDB must generate audit records when successful logons or connections occur.

DISA Rule

SV-253764r961824_rule

Vulnerability Number

V-253764

Group Title

SRG-APP-000503-DB-000350

Rule Version

MADB-10-011200

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

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",
"DISCONNECT"
]
}'
));

Check Contents

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.

Log in to and out of the MariaDB database server. Verify the connect is logged in the audit logfile or syslog depending on how it is configured.

If connect is not logged this is a finding.

Vulnerability Number

V-253764

Documentable

False

Rule Version

MADB-10-011200

Severity Override Guidance

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.

Log in to and out of the MariaDB database server. Verify the connect is logged in the audit logfile or syslog depending on how it is configured.

If connect is not logged this is a finding.

Check Content Reference

M

Target Key

5475