Rule ID
SV-286224r1292212_rule
Version
V1R1
MariaDB handling data requiring data at rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest. These cryptographic mechanisms may be native to the MariaDB or implemented via additional software or operating system/file system settings, as appropriate to the situation. Selection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields). The decision whether and what to encrypt rests with the data owner and is also influenced by the physical measures taken to secure the equipment and media on which the information resides. Satisfies: SRG-APP-000428-DB-000386, SRG-APP-000429-DB-000387
Review the security guide to determine whether the organization has defined the information at rest that is to be protected from disclosure, which must include, at a minimum, PII and classified information. If the documentation indicates no information requires such protections, this is not a finding. Review the configuration of MariaDB, operating system/file system, and additional software as relevant. One possible way to encrypt data within MariaDB is to use the file key management plugin. To determine if this is installed, check the following variables as the DBA: SHOW PLUGINS; Confirm the "file_key_management.so" is listed. SHOW GLOBAL VARIABLES LIKE 'file_key%'; SHOW GLOBAL VARIABLES LIKE 'aria_en%'; SHOW GLOBAL VARIABLES LIKE 'innodb_encrypt_tables'; SHOW GLOBAL VARIABLES LIKE 'innodb_encrypt_log'; SHOW GLOBAL VARIABLES LIKE 'innodb_tablespace%'; SHOW GLOBAL VARIABLES LIKE 'encrypt%'; Confirm these are "ON". If this is required and is not found, this is a finding. If any of the information defined as requiring protection is not encrypted in a manner that provides the required level of protection and is not physically secured to the required level, this is a finding.
Configure MariaDB, the operating system/file system, and any supporting software to provide the required level of cryptographic protection. MariaDB data-at-rest encryption can be implemented using a key management and encryption plugin such as the File Key Management Plugin. After the File Key Management Plugin has been enabled and configured, encrypted tables may be created using the "ENCRYPTED" table option. Example: CREATE TABLE t (i INT) ENGINE=InnoDB ENCRYPTED=YES; When a table is created with the "ENCRYPTED" option enabled, the table data is encrypted using the encryption key defined in the configured key management file. Ensure that the encryption key file is stored in a protected location with appropriate operating system permissions and that only authorized administrators have access to the key material.