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

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-253764	MADB-10-011200	SV-253764r844267_rule		Medium

Description
For completeness of forensic analysis, it is necessary to track who/what (a user or other principal) logs on to the DBMS.

STIG	Date
MariaDB Enterprise 10.x Security Technical Implementation Guide	2022-08-24

Details

Check Text ( C-57216r844266_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. 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 Text ( C-57216r844266_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.

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.

Fix Text (F-57167r841816_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", "DISCONNECT" ] }' ));