OpenControls Logo

STIG Viewer

STIGViewer Support

MariaDB, when utilizing PKI-based authentication, must validate certificates by performing RFC 5280-compliant certification path validation.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-253699MADB-10-004000SV-253699r961038_ruleCCI-000185medium
Description
The DoD standard for authentication is DoD-approved PKI certificates. A certificate's certification path is the path from the end entity certificate to a trusted root certification authority (CA). Certification path validation is necessary for a relying party to make an informed decision regarding acceptance of an end entity certificate. Certification path validation includes checks such as certificate issuer trust, time validity and revocation status for each certificate in the certification path. Revocation status information for CA and subject certificates in a certification path is commonly provided via certificate revocation lists (CRLs) or online certificate status protocol (OCSP) responses. Database Management Systems that do not validate certificates by performing RFC 5280-compliant certification path validation are in danger of accepting certificates that are invalid and/or counterfeit. This could allow unauthorized access to the database.
STIGDate
MariaDB Enterprise 10.x Security Technical Implementation Guide2026-03-02

Related Frameworks

1 mapping across 3 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

IAC-10.2PKI-Based Authentication
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (53) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-12Session Termination
1.00
AC-17(10)Authenticate Remote Commands
1.00
AC-17(2)Protection of Confidentiality and Integrity Using Encryption
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(11)Usage Conditions
1.00
AC-2(2)Automated Temporary and Emergency Account Management
1.00
AC-2(3)Disable Accounts
1.00
AC-2(4)Automated Audit Actions
1.00
AC-3Access Enforcement
1.00
AC-4(17)Domain Authentication
1.00

+43 more (top 10 by confidence shown)

CCI1 mapping
CCI-000185
1.00

Details

Check Text (C-253699r961038_chk)

As the database administrator, list all users and their SSL setup by running the following: MariaDB> SELECT user, host, ssl_type FROM mysql.user; Use the result of the next query to verify the MariaDB Server is using certificates: MariaDB> STATUS; Verify the line beginning with "SSL:" returns expected SSL information. Using the following query, verify SSL is configured as expected: MariaDB> SHOW GLOBAL VARIABLES LIKE %ssl% ; If not configured as expected, this is a finding.

Fix Text (F-57102r841621_fix)

As the administrator locate the MariaDB configuration file to change. This varies depending on setup and how configuration files are managed but should be in /etc/my.cnf.d/. It is recommended to have a separate configuration file within this directory for SSL connection information. In the [server] section add the lines for SSL: ssl-ca=/path/to/ssl/ca-cert.pem ssl-cert=/path/to/ssl/server-cert.pem ssl-key=/path/to/ssl/server-key.pem To fully implement SSL for MariaDB, the client settings and user accounts need to be set up as well. More information can be found here: https://mariadb.com/kb/en/securing-connections-for-client-and-server/