| Checked | Name | Title |
|---|
| ☐ | SV-253666r960735_rule | MariaDB must limit the number of concurrent sessions to an organization-defined number per user for all accounts and/or account types. |
| ☐ | SV-253667r1136896_rule | MariaDB must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals. |
| ☐ | SV-253668r1137654_rule | MariaDB must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. |
| ☐ | SV-253669r960864_rule | MariaDB must protect against a user falsely repudiating having performed organization-defined actions. |
| ☐ | SV-253670r960879_rule | MariaDB must provide audit record generation capability for DoD-defined auditable events within all DBMS/database components. |
| ☐ | SV-253671r960882_rule | MariaDB must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited. |
| ☐ | SV-253672r960885_rule | MariaDB must be able to generate audit records when privileges/permissions are retrieved. |
| ☐ | SV-253673r960885_rule | MariaDB must be able to generate audit records when unsuccessful attempts to retrieve privileges/permissions occur. |
| ☐ | SV-253674r960888_rule | MariaDB must initiate session auditing upon startup. |
| ☐ | SV-253675r960891_rule | MariaDB must produce audit records containing sufficient information to establish what type of events occurred. |
| ☐ | SV-253676r960909_rule | MariaDB must include additional, more detailed, organization-defined information in the audit records for audit events identified by type, location, or subject. |
| ☐ | SV-253677r1043188_rule | MariaDB 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. |
| ☐ | SV-253678r1043188_rule | MariaDB 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. |
| ☐ | SV-253679r960930_rule | The audit information produced by MariaDB must be protected from unauthorized read access. |
| ☐ | SV-253680r960933_rule | The audit information produced by MariaDB must be protected from unauthorized modification. |
| ☐ | SV-253681r960936_rule | The audit information produced by MariaDB must be protected from unauthorized deletion. |
| ☐ | SV-253682r960939_rule | MariaDB must protect its audit features from unauthorized access. |
| ☐ | SV-253683r960942_rule | MariaDB must protect its audit configuration from unauthorized modification. |
| ☐ | SV-253684r960945_rule | MariaDB must protect its audit features from unauthorized removal. |
| ☐ | SV-253685r960960_rule | MariaDB must limit privileges to change software modules, to include stored procedures, functions and triggers, and links to software external to the DBMS. |
| ☐ | SV-253686r960960_rule | The MariaDB software installation account must be restricted to authorized users. |
| ☐ | SV-253687r960960_rule | Database software, including MariaDB configuration files, must be stored in dedicated directories, separate from the host OS and other applications. |
| ☐ | SV-253688r960960_rule | Database 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. |
| ☐ | SV-253689r960960_rule | The 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. |
| ☐ | SV-253690r960963_rule | Default demonstration and sample databases, database objects, and applications must be removed. |
| ☐ | SV-253691r960963_rule | Unused database components, DBMS software, and database objects must be removed. |
| ☐ | SV-253692r960963_rule | Access to external executables must be disabled or restricted. |
| ☐ | SV-253693r1043177_rule | MariaDB 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. |
| ☐ | SV-253694r1051115_rule | MariaDB must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users). |
| ☐ | SV-253695r1018598_rule | If MariaDB authentication, using passwords, is employed, then MariaDB must enforce the DOD standards for password complexity. |
| ☐ | SV-253696r1018599_rule | If MariaDB authentication using passwords is employed, MariaDB must enforce the DOD standards for password lifetime. |
| ☐ | SV-253697r1018600_rule | If passwords are used for authentication, MariaDB must store only hashed, salted representations of passwords. |
| ☐ | SV-253698r961029_rule | If passwords are used for authentication, MariaDB must transmit only encrypted representations of passwords. |
| ☐ | SV-253699r961038_rule | MariaDB, when utilizing PKI-based authentication, must validate certificates by performing RFC 5280-compliant certification path validation. |
| ☐ | SV-253700r961041_rule | MariaDB must enforce authorized access to all PKI private keys stored/used by the DBMS. |
| ☐ | SV-253701r961044_rule | MariaDB must map PKI ID to an associated user account. |
| ☐ | SV-253702r961047_rule | MariaDB must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals. |
| ☐ | SV-253703r1136902_rule | MariaDB must use NIST FIPS 140-2/140-3 validated cryptographic modules for cryptographic operations. |
| ☐ | SV-253704r961053_rule | The MariaDB must uniquely identify and authenticate nonorganizational users (or processes acting on behalf of nonorganizational users). |
| ☐ | SV-253705r1137655_rule | MariaDB must separate user functionality (including user interface services) from database management functionality. |
| ☐ | SV-253706r1043179_rule | MariaDB must invalidate session identifiers upon user logout or other session termination. |
| ☐ | SV-253707r1043181_rule | MariaDB must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values. |
| ☐ | SV-253708r961122_rule | MariaDB must fail to a secure state if system initialization fails, shutdown fails, or aborts fail. |
| ☐ | SV-253709r961125_rule | In 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. |
| ☐ | SV-253710r961128_rule | MariaDB must protect the confidentiality and integrity of all information at rest. |
| ☐ | SV-253711r1137656_rule | Database contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy. |
| ☐ | SV-253712r1137657_rule | MariaDB must prevent unauthorized and unintended information transfer via shared system resources. |
| ☐ | SV-253713r1137658_rule | Access to database files must be limited to relevant processes and to authorized, administrative users. |
| ☐ | SV-253714r961158_rule | MariaDB must check the validity of all data inputs except those specifically identified by the organization. |
| ☐ | SV-253715r961158_rule | MariaDB and associated applications must reserve the use of dynamic code execution for situations that require it. |
| ☐ | SV-253716r961158_rule | MariaDB and associated applications, when making use of dynamic code execution, must scan input data for invalid values that may indicate a code injection attack. |
| ☐ | SV-253717r1043182_rule | MariaDB must automatically terminate a user's session after organization-defined conditions or trigger events requiring session disconnect. |
| ☐ | SV-253718r961224_rule | MariaDB must provide logout functionality to allow the user to manually terminate a session initiated by that user. |
| ☐ | SV-253719r1138540_rule | MariaDB must associate organization-defined types of security labels having organization-defined security label values with information in storage. |
| ☐ | SV-253720r1138541_rule | MariaDB must associate organization-defined types of security labels having organization-defined security label values with information in process. |
| ☐ | SV-253721r1138542_rule | MariaDB must associate organization-defined types of security labels having organization-defined security label values with information in transmission. |
| ☐ | SV-253722r961317_rule | MariaDB must enforce discretionary access control policies, as defined by the data owner, over defined subjects, and objects. |
| ☐ | SV-253723r961353_rule | MariaDB must prevent nonprivileged users from executing privileged functions, to include disabling, circumventing, or altering implemented security safeguards/countermeasures. |
| ☐ | SV-253724r961359_rule | Execution of software modules (to include stored procedures, functions, and triggers) with elevated privileges must be restricted to necessary cases only. |
| ☐ | SV-253727r961392_rule | MariaDB must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements. |
| ☐ | SV-253728r961398_rule | MariaDB must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75 percent of maximum audit record storage capacity. |
| ☐ | SV-253729r961401_rule | MariaDB must provide an immediate real-time alert to appropriate support staff of all audit failure events requiring real-time alerts. |
| ☐ | SV-253730r961443_rule | MariaDB must record time stamps, in audit records and application data, that can be mapped to Coordinated Universal Time (UTC, formerly GMT). |
| ☐ | SV-253731r1018601_rule | MariaDB must prohibit user installation of logic modules (stored procedures, functions, triggers, views, etc.) without explicit privileged status. |
| ☐ | SV-253732r961461_rule | MariaDB must enforce access restrictions associated with changes to the configuration of MariaDB or database(s). |
| ☐ | SV-253733r1018602_rule | MariaDB must produce audit records of its enforcement of access restrictions associated with changes to the configuration of the DBMS or database(s). |
| ☐ | SV-253734r961470_rule | MariaDB 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. |
| ☐ | SV-253735r1050788_rule | MariaDB must require users to reauthenticate when organization-defined circumstances or situations require reauthentication. |
| ☐ | SV-253736r961521_rule | MariaDB must prohibit the use of cached authenticators after an organization-defined time period. |
| ☐ | SV-253737r1117186_rule | MariaDB must use NSA-approved cryptography to protect classified information in accordance with the data owner's requirements. |
| ☐ | SV-253738r1193220_rule | 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. |
| ☐ | SV-253739r1018554_rule | MariaDB 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. |
| ☐ | SV-253740r1018555_rule | MariaDB must implement cryptographic mechanisms preventing the unauthorized disclosure of organization-defined information at rest on organization-defined information system components. |
| ☐ | SV-253741r961638_rule | MariaDB must maintain the confidentiality and integrity of information during preparation for transmission. |
| ☐ | SV-253742r961641_rule | MariaDB must maintain the confidentiality and integrity of information during reception. |
| ☐ | SV-253743r961656_rule | When invalid inputs are received, MariaDB must behave in a predictable and documented manner that reflects organizational and system objectives. |
| ☐ | SV-253744r961677_rule | When updates are applied to the MariaDB software, any software components that have been replaced or made unnecessary must be removed. |
| ☐ | SV-253745r1137667_rule | 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). |
| ☐ | SV-253746r961791_rule | MariaDB must be able to generate audit records when security objects are accessed. |
| ☐ | SV-253747r961791_rule | MariaDB must generate audit records when unsuccessful attempts to access security objects occur. |
| ☐ | SV-253748r961797_rule | MariaDB must generate audit records when categories of information (e.g., classification levels/security levels) are accessed. |
| ☐ | SV-253749r961797_rule | MariaDB must generate audit records when unsuccessful attempts to access categories of information (e.g., classification levels/security levels) occur. |
| ☐ | SV-253750r961800_rule | MariaDB must generate audit records when privileges/permissions are added. |
| ☐ | SV-253751r961800_rule | MariaDB must generate audit records when unsuccessful attempts to add privileges/permissions occur. |
| ☐ | SV-253752r961800_rule | MariaDB must generate audit records when privileges/permissions are modified. |
| ☐ | SV-253753r961800_rule | MariaDB must generate audit records when unsuccessful attempts to modify privileges/permissions occur. |
| ☐ | SV-253754r961803_rule | MariaDB must generate audit records when security objects are modified. |
| ☐ | SV-253755r961803_rule | MariaDB must generate audit records when unsuccessful attempts to modify security objects occur. |
| ☐ | SV-253756r961809_rule | MariaDB must generate audit records when categories of information (e.g., classification levels/security levels) are modified. |
| ☐ | SV-253757r961809_rule | MariaDB must generate audit records when unsuccessful attempts to modify categories of information (e.g., classification levels/security levels) occur. |
| ☐ | SV-253758r961812_rule | MariaDB must generate audit records when privileges/permissions are deleted. |
| ☐ | SV-253759r961812_rule | MariaDB must generate audit records when unsuccessful attempts to delete privileges/permissions occur. |
| ☐ | SV-253760r961818_rule | MariaDB must generate audit records when security objects are deleted. |
| ☐ | SV-253761r961818_rule | MariaDB must generate audit records when unsuccessful attempts to delete security objects occur. |
| ☐ | SV-253762r961821_rule | MariaDB must generate audit records when categories of information (e.g., classification levels/security levels) are deleted. |
| ☐ | SV-253763r961821_rule | MariaDB must generate audit records when unsuccessful attempts to delete categories of information (e.g., classification levels/security levels) occur. |
| ☐ | SV-253764r961824_rule | MariaDB must generate audit records when successful logons or connections occur. |
| ☐ | SV-253765r961824_rule | MariaDB must generate audit records when unsuccessful logons or connection attempts occur. |
| ☐ | SV-253766r961827_rule | MariaDB must generate audit records for all privileged activities or other system-level access. |
| ☐ | SV-253767r961827_rule | MariaDB must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur. |
| ☐ | SV-253768r961830_rule | MariaDB must generate audit records showing starting and ending time for user access to the database(s). |
| ☐ | SV-253769r961833_rule | MariaDB must generate audit records when concurrent logons/connections by the same user from different workstations occur. |
| ☐ | SV-253770r961836_rule | MariaDB must be able to generate audit records when successful accesses to objects occur. |
| ☐ | SV-253771r961836_rule | MariaDB must generate audit records when unsuccessful accesses to objects occur. |
| ☐ | SV-253772r961839_rule | MariaDB must generate audit records for all direct access to the database(s). |
| ☐ | SV-253776r961860_rule | MariaDB 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. |
| ☐ | SV-265882r1193305_rule | MariaDB products must be an enterprise version supported by the vendor. |
STIGQter: STIG Summary: