Title

MariaDB must associate organization-defined types of security labels having organization-defined security label values with information in storage. (Cat II impact)

Discussion

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.

Check Content

If security labeling is not required, this is not a finding. If security labeling requirements have been specified, but the security labeling is not implemented or does not reliably maintain labels on information in storage, this is a finding.

Fix Text

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/

Additional Identifiers

Rule ID: SV-253719r879689_rule

Vulnerability ID: V-253719

Group Title: SRG-APP-000311-DB-000308

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.