DISA MariaDB Enterprise 10.x v2r4 OS Linux

Name: DISA MariaDB Enterprise 10.x v2r4 OS Linux

Updated: 12/19/2025

Authority: DISA STIG

Plugin: Unix

Revision: 1.0

Estimated Item Count: 8

Filename: DISA_STIG_MariaDB_Enterprise_10.x_v2r4_OS_Linux.audit

Size: 25.2 kB

MD5: 030f19a1bb54cc2deb37ae3ac423b792

SHA256: e1d9a335a2f4a8d6f6bf9f4d933627a4cd6e365b73a731fdd27489902dc739f4

Description	Categories
DISA_STIG_MariaDB_Enterprise_10.x_v2r4_OS_Linux.audit from DISA MariaDB Enterprise 10.x v2r4 STIG
MADB-10-004400 - MariaDB must use NIST FIPS 140-2/140-3 validated cryptographic modules for cryptographic operations.	IDENTIFICATION AND AUTHENTICATION
MADB-10-008500 - MariaDB must only accept end entity certificates issued by DoD PKI or DoD-approved PKI Certification Authorities (CAs) for the establishment of all encrypted sessions.	SYSTEM AND COMMUNICATIONS PROTECTION
MADB-10-009200 - When updates are applied to the MariaDB software, any software components that have been replaced or made unnecessary must be removed.	SYSTEM AND INFORMATION INTEGRITY
MADB-10-009300 - Security-relevant software updates to MariaDB must be installed within the time period directed by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs).	SYSTEM AND INFORMATION INTEGRITY
MADB-10-012100 - MariaDB must implement NIST FIPS 140-2 validated cryptographic modules to provision digital signatures.	SYSTEM AND COMMUNICATIONS PROTECTION
MADB-10-012200 - MariaDB must implement NIST FIPS 140-2 validated cryptographic modules to generate and validate cryptographic hashes.	SYSTEM AND COMMUNICATIONS PROTECTION
MADB-10-012300 - MariaDB must implement NIST FIPS 140-2 validated cryptographic modules to protect unclassified information requiring confidentiality and cryptographic protection, in accordance with the data owners requirements.	SYSTEM AND COMMUNICATIONS PROTECTION