MADB-10-009500 - MariaDB must generate audit records when unsuccessful attempts to access security objects occur.

Information

Changes to the security configuration must be tracked.

This requirement applies to situations where security data is retrieved or modified via data manipulation operations, as opposed to via specialized security functionality.

In an SQL environment, types of access include, but are not necessarily limited to:
SELECT
CREATE
INSERT
UPDATE
DELETE
EXECUTE
ALTER
DROP

To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.

Solution

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

Item Details

Audit Name: DISA MariaDB Enterprise 10.x v2r4 DB

Category: AUDIT AND ACCOUNTABILITY

Plugin: MySQLDB

Control ID: 6c9cab5551d4556f9f88d19a8cc57013a7cc1f3dd886ae7e75ea47b4ce3adaa4

Detections

Analytics

MADB-10-009500 - MariaDB must generate audit records when unsuccessful attempts to access security objects occur.

Information

Solution

See Also

Item Details