MADB-10-006400 - MariaDB must associate organization-defined types of security labels having organization-defined security label values with information in storage.

Information

Without the association of security labels to information, there is no basis for MariaDB to make security-related access-control decisions.

Security labels are abstractions representing the basic properties or characteristics of an entity (e.g., subjects and objects) with respect to safeguarding information.

These labels are typically associated with internal data structures (e.g., tables, rows) within the database and are used to enable the implementation of access control and flow control policies, reflect special dissemination, handling or distribution instructions, or support other aspects of the information security policy.

One example includes marking data as classified or CUI. These security labels may be assigned manually or during data processing, but, either way, it is imperative these assignments are maintained while the data is in storage. If the security labels are lost when the data is stored, there is the risk of a data compromise.

The mechanism used to support security labeling may be a feature of the DBMS product, a third-party product, or custom application code.

NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.

Solution

Add custom data structures, data elements and application code, to provide reliable security labeling of information in transmission. Write Custom Code: https://mariadb.com/resources/blog/protect-your-data-row-level-security-in-mariadb-10-0/

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_MariaDB_Enterprise_10-x_V2R1_STIG.zip

Item Details

Category: ACCESS CONTROL

References: 800-53|AC-16a., CAT|II, CCI|CCI-002262, Rule-ID|SV-253719r961269_rule, STIG-ID|MADB-10-006400, Vuln-ID|V-253719

Plugin: MySQLDB

Control ID: df9124a343bb6f3c8234632b3970e7d9cc73fb1ddba8fa7458b3442f8f22fcf4