Title

MariaDB must generate audit records when concurrent logons/connections by the same user from different workstations occur. (Cat II impact)

Discussion

For completeness of forensic analysis, it is necessary to track who logs on to MariaDB. Concurrent connections by the same user from multiple workstations may be valid use of the system; or such connections may be due to improper circumvention of the requirement to use the CAC for authentication; or they may indicate unauthorized account sharing; or they may be because an account has been compromised. (If the fact of multiple, concurrent logons by a given user can be reliably reconstructed from the log entries for other events (logons/connections; voluntary and involuntary disconnections), then it is not mandatory to create additional log entries specifically for this.)

Check Content

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

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

Additional Identifiers

Rule ID: SV-253769r879877_rule

Vulnerability ID: V-253769

Group Title: SRG-APP-000506-DB-000353

Expert Comments

CCIs tied to check.

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