STIGhubSTIGhub
STIGhub— A free STIG search and compliance tool·STIGs updated 2 hours ago
Powered by Pylon·Privacy·Terms·Feedback·© 2026 Beacon Cloud Solutions, Inc.
← Back to MariaDB Enterprise Server Security Technical Implementation Guide

V-286197

CAT I (High)

MariaDB must use NIST FIPS 140-3-validated cryptographic modules for cryptographic operations.

Rule ID

SV-286197r1294923_rule

STIG

MariaDB Enterprise Server Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-000803CCI-002450

Discussion

Use of weak or not validated cryptographic algorithms undermines the purposes of using encryption and digital signatures to protect data. Weak algorithms can be easily broken and not validated cryptographic modules may not implement algorithms correctly. Unapproved cryptographic modules or algorithms should not be relied on for authentication, confidentiality or integrity. Weak cryptography could allow an attacker to gain access to and modify data stored in the database as well as the administration settings of the DBMS. Applications, including DBMSs, using cryptography are required to use approved NIST FIPS 140-3-validated cryptographic modules that meet the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. The security functions validated as part of FIPS 140-3 for cryptographic modules are described in FIPS 140-3 Annex A. NSA Type-X (where X=1, 2, 3, 4) products are NSA-certified, hardware-based encryption modules. Satisfies: SRG-APP-000179-DB-000114, SRG-APP-000514-DB-000381, SRG-APP-000514-DB-000382, SRG-APP-000514-DB-000383

Check Content

MariaDB relies on the underlying OS for FIPS compliance. Verify FIPS is enabled for the OS. Following are example Linux commands:

# sysctl crypto.fips_enabled
crypto.fips_enabled = 1
 
If crypto.fips_enabled = 0, this is a finding. 

OR

$ sudo fips-mode-setup --check
FIPS mode is enabled.

If FIPS mode is not enabled, this is a finding.

Verify the server is using OpenSSL:

MariaDB> SHOW GLOBAL VARIABLES LIKE '%have_openssl';

If the value of "have_openssl" is not "YES", this is a finding.

MariaDB> SHOW GLOBAL VARIABLES LIKE '%version_ssl_library%';

Note: FIPS-compliant libraries for OpenSSL 1.x.x contain "fips" in the version.

If the value of "version_ssl_library" is not FIPS compliant, this is a finding.

If using OpenSSL 3.x , check the providers: 

openssl list -providers

Providers:
default
name: OpenSSL Default Provider
version: 3.2.2
status: active

fips
    name: Red Hat Enterprise Linux 9 - OpenSSL FIPS Provider
    version: 3.2.2-622cc79c634cbbef
    status: active

If the response does not list a FIPS provider with a status of "active", this is a finding.

Fix Text

Configure OpenSSL to meet FIPS compliance following Red Hat documentation.