Detections
Analytics
MADB-10-006700 - MariaDB must enforce discretionary access control policies, as defined by the data owner, over defined subjects, and objects.
Information
Discretionary Access Control (DAC) is based on the notion that individual users are owners of objects and therefore have discretion over who should be authorized to access the object and in which mode (e.g., read or write). Ownership is usually acquired as a consequence of creating the object or via specified ownership assignment. DAC allows the owner to determine who will have access to objects they control. An example of DAC includes user-controlled table permissions.When discretionary access control policies are implemented, subjects are not constrained with regard to what actions they can take with information for which they have already been granted access. Thus, subjects that have been granted access to information are not prevented from passing (i.e., the subjects have the discretion to pass) the information to other subjects or objects.
A subject that is constrained in its operation by Mandatory Access Control policies is still able to operate under the less rigorous constraints of this requirement. Thus, while Mandatory Access Control imposes constraints preventing a subject from passing information to another subject operating at a different sensitivity level, this requirement permits the subject to pass the information to any subject at the same sensitivity level.
The policy is bounded by the information system boundary. Once the information is passed outside of the control of the information system, additional means may be required to ensure the constraints remain in effect. While the older, more traditional definitions of discretionary access control require identity-based access control, that limitation is not required for this use of discretionary access control.
NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.
Solution
Implement the organization's DAC policy in the security configuration of the database and DBMS, and, if applicable, the security configuration of the application(s) using the database.To grant and revoke privileges, as the database administrator, use the following SQL syntax:
**To Grant User and Role privileges:
MariaDB> GRANT privilege ON database . table TO user|role ;
**To Revoke User and Role privileges:
MariaDB> REVOKE privilege_type ON database . table FROM user|role ;
See Also
https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_MariaDB_Enterprise_10-x_V2R1_STIG.zip
Item Details
Audit Name: DISA MariaDB Enterprise 10.x v2r1 DB
Category: ACCESS CONTROL
References: 800-53|AC-3(4), CAT|II, CCI|CCI-002165, Rule-ID|SV-253722r961317_rule, STIG-ID|MADB-10-006700, Vuln-ID|V-253722
Plugin: MySQLDB
Control ID: f55c7ad2c62031b225a010599997ba4348479563fff57d3d39a69fbd406a2c13