STIGhubSTIGhub
STIGhub— A free STIG search and compliance tool·STIGs updated 4 hours ago
Powered by Pylon·Privacy·Terms·Feedback·© 2026 Beacon Cloud Solutions, Inc.
← Back to MariaDB Enterprise Server Security Technical Implementation Guide

V-286190

CAT II (Medium)

MariaDB must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).

Rule ID

SV-286190r1291864_rule

STIG

MariaDB Enterprise Server Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-000764

Discussion

To ensure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system. Organizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and any processes acting on behalf of users) must be uniquely identified and authenticated for all accesses, except the following: (i) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and (ii) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals using shared accounts, for detailed accountability of individual activity.

Check Content

Connect to MariaDB using an administrative account from the operating system shell:

mariadb -u root -p

After connecting to the MariaDB client, run:

SELECT user, host FROM mysql.user WHERE is_role='Y';

If the query returns any unauthorized roles, this is a finding.

Fix Text

Configure MariaDB settings to uniquely identify and authenticate all organizational users who log on/connect to the system.

To create roles, run:

CREATE ROLE app_read_role [options];