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 MySQL Database Server 8.0, etc.) must be restricted to authorized users.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-235166MYS8-00-008700SV-235166r960960_ruleCCI-001499medium
Description
If the DBMS 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 will 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
Oracle MySQL 8.0 Security Technical Implementation Guide2024-09-04

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-235166r960960_chk)

MySQL database objects do not have an owner. MySQL is a single instance and single database with multiple schemas (aliased to be called either schema or database). Permissions are based on schemas and schema objects and privileges include grants to objects or grants to allow users to further grants access to objects. To reiterate, there is not an object owner just rights assigned to schemas and the objects within them. To determine rights to objects via schema, table, or user privileges run the following: SELECT * FROM `information_schema`.`SCHEMA_PRIVILEGES`; SELECT * FROM `information_schema`.`TABLE_PRIVILEGES`; SELECT * FROM `information_schema`.`COLUMN_PRIVILEGES`; SELECT * FROM `information_schema`.`USER_PRIVILEGES`; SELECT * FROM `information_schema`.`ROLE_COLUMN_GRANTS`; SELECT * FROM `information_schema`.`ROLE_TABLE_GRANTS`; On a per-user basis, for example: show grants for 'test'@'%'; If any database objects are found to have access by users not authorized to the database objects, this is a finding.

Fix Text (F-38348r623619_fix)

Assign ownership of authorized objects to authorized object owner accounts. Review user accounts with the GRANT OPTION. REVOKE GRANT OPTION to limit users with grant privileges.