Skip to content

MariaDB must generate audit records when unsuccessful accesses to objects occur.

An XCCDF Rule

Description

<VulnDiscussion>Without tracking all or selected types of access to all or selected objects (tables, views, procedures, functions, etc.), it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. In an SQL environment, types of access include, but are not necessarily limited to: SELECT INSERT UPDATE DELETE EXECUTE To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

ID
SV-253771r879878_rule
Severity
Medium
References
Updated



Remediation - Manual Procedure

If the MariaDB Enterprise Audit plugin is not active, enable it in one of the two following ways. 

1. Config file (requires restart): 

[mariadb]
server_audit_logging = ON