Rule ID
SV-286194r1294920_rule
Version
V1R1
CCIs
The DoW standard for authentication is DoW-approved PKI certificates. PKI certificate-based authentication is performed by requiring the certificate holder to cryptographically prove possession of the corresponding private key. If the private key is stolen, an attacker can use the private key(s) to impersonate the certificate holder. In cases where the MariaDB-stored private keys are used to authenticate MariaDB to the system’s clients, loss of the corresponding private keys would allow an attacker to successfully perform undetected man in the middle attacks against the MariaDB system and its clients. Both the holder of a digital certificate and the issuing authority must take careful measures to protect the corresponding private key. Private keys should always be generated and protected in FIPS 140-3-validated cryptographic modules. All access to the private key(s) of MariaDB must be restricted to authorized and authenticated users. If unauthorized users have access to one or more of the MariaDB s private keys, an attacker could gain access to the key(s) and use them to impersonate the database on the network or otherwise perform unauthorized actions.
As the DBA (root), verify the following settings: SHOW GLOBAL VARIABLES LIKE 'ssl_ca'; SHOW GLOBAL VARIABLES LIKE 'ssl_cert'; SHOW GLOBAL VARIABLES LIKE 'ssl_key'; Example location: /etc/my.cnf.d/certs/ ls -l /etc/my.cnf.d/certs/ If the "owner:group" is not the database owner (mysql:mysql), this is a finding. If permissions are not "600", this is a finding.
Ensure the TLS private key file permissions restrict access to authorized users only. Example: chown mysql:mysql /etc/my.cnf.d/certs/server-key.pem chmod 600 /etc/my.cnf.d/certs/server-key.pem