OpenControls Logo

STIG Viewer

STIGViewer Support

The role(s)/group(s) used to modify database structure (including but not necessarily limited to tables, indexes, storage, etc.) and logic modules (stored procedures, functions, triggers, links to software external to the MariaDB, etc.) must be restricted to authorized users.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-253689MADB-10-003000SV-253689r960960_ruleCCI-001499medium
Description
If the MariaDB were to allow any user to make changes to database structure or logic, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. Accordingly, only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications. Unmanaged changes that occur to the database software libraries or configuration can lead to unauthorized or compromised installations.
STIGDate
MariaDB Enterprise 10.x Security Technical Implementation Guide2026-03-02

Related Frameworks

1 mapping across 3 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

CHG-04.5Library Privileges
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (56) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-17(1)Monitoring and Control
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(10)Shared and Group Account Credential Change
1.00
AC-2(2)Automated Temporary and Emergency Account Management
1.00
AC-2(3)Disable Accounts
1.00
AC-2(4)Automated Audit Actions
1.00
AC-3Access Enforcement
1.00
AC-3(7)Role-based Access Control
1.00
AC-4Information Flow Enforcement
1.00
AC-6(10)Prohibit Non-privileged Users from Executing Privileged Functions
1.00

+46 more (top 10 by confidence shown)

CCI1 mapping
CCI-001499
1.00

Details

Check Text (C-253689r960960_chk)

Gather a list of SHOW GRANTS commands. This list will include users and roles: MariaDB> SELECT DISTINCT CONCAT( 'SHOW GRANTS FOR ', user,'@', host,';') AS grantQuery FROM mysql.user; Run each SHOW GRANTS commands and verify that all objects have the correct privileges, if they do not, this is a finding. MariaDB> SHOW GRANTS FOR 'user'@'host'; Find the data directory and verify its operating system privileges. MariaDB> SHOW GLOBAL VARIABLES LIKE '%datadir%'; # ls -al /path/to/datadir If permissions of the database directory are not limited to an authorized user account, this is a finding.

Fix Text (F-57092r841591_fix)

As the database administrator, revoke any permissions from a role that are deemed unnecessary by running the following SQL: MariaDB> REVOKE PERMISSION FROM ROLE_NAME ; Revoke any roles from a user if they are deemed unnecessary by running the following SQL: MariaDB> REVOKE ROLE_NAME FROM test_user ; If the revoked role is the default role for the user, the REVOKE command should be followed by a command to set a new default role that has appropriate permissions, or no default role: MariaDB> SET DEFAULT ROLE NONE FOR test_user ; MariaDB> SET DEFAULT ROLE ROLE_NAME for test_user ;