STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 1 hour ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to STIGs

MariaDB Enterprise 10.x Security Technical Implementation Guide

Version

V2R5

Release Date

Mar 2, 2026

SCAP Benchmark ID

MariaDB_Enterprise_10-x_STIG

Total Checks

107

Tags

other
CAT I: 14CAT II: 92CAT III: 1

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.

Export CKLExport CSVExport JSONDownload STIG ZIP

Checks (107)

V-253666LOWMariaDB must limit the number of concurrent sessions to an organization-defined number per user for all accounts and/or account types.V-253667HIGHMariaDB must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals.V-253668HIGHMariaDB must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.V-253669MEDIUMMariaDB must protect against a user falsely repudiating having performed organization-defined actions.V-253670MEDIUMMariaDB must provide audit record generation capability for DoD-defined auditable events within all DBMS/database components.V-253671MEDIUMMariaDB must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited.V-253672MEDIUMMariaDB must be able to generate audit records when privileges/permissions are retrieved.V-253673MEDIUMMariaDB must be able to generate audit records when unsuccessful attempts to retrieve privileges/permissions occur.V-253674MEDIUMMariaDB must initiate session auditing upon startup.V-253675MEDIUMMariaDB must produce audit records containing sufficient information to establish what type of events occurred.V-253676MEDIUMMariaDB must include additional, more detailed, organization-defined information in the audit records for audit events identified by type, location, or subject.V-253677MEDIUMMariaDB must by default shut down upon audit failure, to include the unavailability of space for more audit log records; or must be configurable to shut down upon audit failure.V-253678MEDIUMMariaDB must be configurable to overwrite audit log records, oldest first (First-In-First-Out - FIFO), in the event of unavailability of space for more audit log records.V-253679MEDIUMThe audit information produced by MariaDB must be protected from unauthorized read access.V-253680MEDIUMThe audit information produced by MariaDB must be protected from unauthorized modification.V-253681MEDIUMThe audit information produced by MariaDB must be protected from unauthorized deletion.V-253682MEDIUMMariaDB must protect its audit features from unauthorized access.V-253683MEDIUMMariaDB must protect its audit configuration from unauthorized modification.V-253684MEDIUMMariaDB must protect its audit features from unauthorized removal.V-253685MEDIUMMariaDB must limit privileges to change software modules, to include stored procedures, functions and triggers, and links to software external to the DBMS.V-253686HIGHThe MariaDB software installation account must be restricted to authorized users.V-253687MEDIUMDatabase software, including MariaDB configuration files, must be stored in dedicated directories, separate from the host OS and other applications.V-253688MEDIUMDatabase objects (including but not limited to tables, indexes, storage, stored procedures, functions, triggers, links to software external to MariaDB, etc.) must be owned by database/MariaDB principals authorized for ownership.V-253689MEDIUMThe role(s)/group(s) used to modify database structure (including but not necessarily limited to tables, indexes, storage, etc.) and logic modules (stored procedures, functions, triggers, links to software external to the MariaDB, etc.) must be restricted to authorized users.V-253690MEDIUMDefault demonstration and sample databases, database objects, and applications must be removed.V-253691MEDIUMUnused database components, DBMS software, and database objects must be removed.V-253692MEDIUMAccess to external executables must be disabled or restricted.V-253693MEDIUMMariaDB must be configured to prohibit or restrict the use of organization-defined functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments.V-253694MEDIUMMariaDB must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).V-253695HIGHIf MariaDB authentication, using passwords, is employed, then MariaDB must enforce the DOD standards for password complexity.V-253696MEDIUMIf MariaDB authentication using passwords is employed, MariaDB must enforce the DOD standards for password lifetime.V-253697HIGHIf passwords are used for authentication, MariaDB must store only hashed, salted representations of passwords.V-253698HIGHIf passwords are used for authentication, MariaDB must transmit only encrypted representations of passwords.V-253699MEDIUMMariaDB, when utilizing PKI-based authentication, must validate certificates by performing RFC 5280-compliant certification path validation.V-253700HIGHMariaDB must enforce authorized access to all PKI private keys stored/used by the DBMS.V-253701MEDIUMMariaDB must map PKI ID to an associated user account.V-253702HIGHMariaDB must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.V-253703HIGHMariaDB must use NIST FIPS 140-2/140-3 validated cryptographic modules for cryptographic operations.V-253704MEDIUMThe MariaDB must uniquely identify and authenticate nonorganizational users (or processes acting on behalf of nonorganizational users).V-253705MEDIUMMariaDB must separate user functionality (including user interface services) from database management functionality.V-253706MEDIUMMariaDB must invalidate session identifiers upon user logout or other session termination.V-253707MEDIUMMariaDB must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values.V-253708MEDIUMMariaDB must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.V-253709MEDIUMIn the event of a system failure, MariaDB must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes.V-253710HIGHMariaDB must protect the confidentiality and integrity of all information at rest.V-253711MEDIUMDatabase contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy.V-253712MEDIUMMariaDB must prevent unauthorized and unintended information transfer via shared system resources.V-253713MEDIUMAccess to database files must be limited to relevant processes and to authorized, administrative users.V-253714MEDIUMMariaDB must check the validity of all data inputs except those specifically identified by the organization.V-253715MEDIUMMariaDB and associated applications must reserve the use of dynamic code execution for situations that require it.V-253716MEDIUMMariaDB and associated applications, when making use of dynamic code execution, must scan input data for invalid values that may indicate a code injection attack.V-253717MEDIUMMariaDB must automatically terminate a user's session after organization-defined conditions or trigger events requiring session disconnect.V-253718MEDIUMMariaDB must provide logout functionality to allow the user to manually terminate a session initiated by that user.V-253719MEDIUMMariaDB must associate organization-defined types of security labels having organization-defined security label values with information in storage.V-253720MEDIUMMariaDB must associate organization-defined types of security labels having organization-defined security label values with information in process.V-253721MEDIUMMariaDB must associate organization-defined types of security labels having organization-defined security label values with information in transmission.V-253722MEDIUMMariaDB must enforce discretionary access control policies, as defined by the data owner, over defined subjects, and objects.V-253723MEDIUMMariaDB must prevent nonprivileged users from executing privileged functions, to include disabling, circumventing, or altering implemented security safeguards/countermeasures.V-253724MEDIUMExecution of software modules (to include stored procedures, functions, and triggers) with elevated privileges must be restricted to necessary cases only.V-253727MEDIUMMariaDB must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements.V-253728MEDIUMMariaDB must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75 percent of maximum audit record storage capacity.V-253729MEDIUMMariaDB must provide an immediate real-time alert to appropriate support staff of all audit failure events requiring real-time alerts.V-253730MEDIUMMariaDB must record time stamps, in audit records and application data, that can be mapped to Coordinated Universal Time (UTC, formerly GMT).V-253731MEDIUMMariaDB must prohibit user installation of logic modules (stored procedures, functions, triggers, views, etc.) without explicit privileged status.V-253732MEDIUMMariaDB must enforce access restrictions associated with changes to the configuration of MariaDB or database(s).V-253733MEDIUMMariaDB must produce audit records of its enforcement of access restrictions associated with changes to the configuration of the DBMS or database(s).V-253734MEDIUMMariaDB must disable network functions, ports, protocols, and services deemed by the organization to be nonsecure, in accord with the Ports, Protocols, and Services Management (PPSM) guidance.V-253735MEDIUMMariaDB must require users to reauthenticate when organization-defined circumstances or situations require reauthentication.V-253736MEDIUMMariaDB must prohibit the use of cached authenticators after an organization-defined time period.V-253737HIGHMariaDB must use NSA-approved cryptography to protect classified information in accordance with the data owner's requirements.V-253738MEDIUMMariaDB must only accept end entity certificates issued by DoD PKI or DoD-approved PKI Certification Authorities (CAs) for the establishment of all encrypted sessions.V-253739HIGHMariaDB must implement cryptographic mechanisms to prevent unauthorized modification of organization-defined information at rest (to include, at a minimum, PII and classified information) on organization-defined information system components.V-253740HIGHMariaDB must implement cryptographic mechanisms preventing the unauthorized disclosure of organization-defined information at rest on organization-defined information system components.V-253741MEDIUMMariaDB must maintain the confidentiality and integrity of information during preparation for transmission.V-253742MEDIUMMariaDB must maintain the confidentiality and integrity of information during reception.V-253743MEDIUMWhen invalid inputs are received, MariaDB must behave in a predictable and documented manner that reflects organizational and system objectives.V-253744MEDIUMWhen updates are applied to the MariaDB software, any software components that have been replaced or made unnecessary must be removed.V-253745MEDIUMSecurity-relevant software updates to MariaDB must be installed within the time period directed by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs).V-253746MEDIUMMariaDB must be able to generate audit records when security objects are accessed.V-253747MEDIUMMariaDB must generate audit records when unsuccessful attempts to access security objects occur.V-253748MEDIUMMariaDB must generate audit records when categories of information (e.g., classification levels/security levels) are accessed.V-253749MEDIUMMariaDB must generate audit records when unsuccessful attempts to access categories of information (e.g., classification levels/security levels) occur.V-253750MEDIUMMariaDB must generate audit records when privileges/permissions are added.V-253751MEDIUMMariaDB must generate audit records when unsuccessful attempts to add privileges/permissions occur.V-253752MEDIUMMariaDB must generate audit records when privileges/permissions are modified.V-253753MEDIUMMariaDB must generate audit records when unsuccessful attempts to modify privileges/permissions occur.V-253754MEDIUMMariaDB must generate audit records when security objects are modified.V-253755MEDIUMMariaDB must generate audit records when unsuccessful attempts to modify security objects occur.V-253756MEDIUMMariaDB must generate audit records when categories of information (e.g., classification levels/security levels) are modified.V-253757MEDIUMMariaDB must generate audit records when unsuccessful attempts to modify categories of information (e.g., classification levels/security levels) occur.V-253758MEDIUMMariaDB must generate audit records when privileges/permissions are deleted.V-253759MEDIUMMariaDB must generate audit records when unsuccessful attempts to delete privileges/permissions occur.V-253760MEDIUMMariaDB must generate audit records when security objects are deleted.V-253761MEDIUMMariaDB must generate audit records when unsuccessful attempts to delete security objects occur.V-253762MEDIUMMariaDB must generate audit records when categories of information (e.g., classification levels/security levels) are deleted.V-253763MEDIUMMariaDB must generate audit records when unsuccessful attempts to delete categories of information (e.g., classification levels/security levels) occur.V-253764MEDIUMMariaDB must generate audit records when successful logons or connections occur.V-253765MEDIUMMariaDB must generate audit records when unsuccessful logons or connection attempts occur.V-253766MEDIUMMariaDB must generate audit records for all privileged activities or other system-level access.V-253767MEDIUMMariaDB must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur.V-253768MEDIUMMariaDB must generate audit records showing starting and ending time for user access to the database(s).V-253769MEDIUMMariaDB must generate audit records when concurrent logons/connections by the same user from different workstations occur.V-253770MEDIUMMariaDB must be able to generate audit records when successful accesses to objects occur.V-253771MEDIUMMariaDB must generate audit records when unsuccessful accesses to objects occur.V-253772MEDIUMMariaDB must generate audit records for all direct access to the database(s).V-253776MEDIUMMariaDB must off-load audit data to a separate log management facility; this must be continuous and in near real time for systems with a network connection to the storage facility and weekly or more often for stand-alone systems.V-265882HIGHMariaDB products must be an enterprise version supported by the vendor.