| V-253669 | | MariaDB must protect against a user falsely repudiating having performed organization-defined actions. | Nonrepudiation of actions taken is required in order to maintain data integrity. Examples of particular actions taken by individuals include creating ... |
| V-253670 | | MariaDB must provide audit record generation capability for DoD-defined auditable events within all DBMS/database components. | Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or... |
| V-253671 | | MariaDB must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited. | Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent or i... |
| V-253672 | | MariaDB must be able to generate audit records when privileges/permissions are retrieved. | Under some circumstances, it may be useful to monitor who/what is reading privilege/permission/role information. Therefore, it must be possible to con... |
| V-253673 | | MariaDB must be able to generate audit records when unsuccessful attempts to retrieve privileges/permissions occur. | Under some circumstances, it may be useful to monitor who/what is reading privilege/permission/role information. Therefore, it must be possible to con... |
| V-253674 | | MariaDB must initiate session auditing upon startup. | Session auditing is for use when a user's activities are under investigation. To be sure of capturing all activity during those periods when session a... |
| V-253675 | | MariaDB must produce audit records containing sufficient information to establish what type of events occurred. | Information system auditing capability is critical for accurate forensic analysis. Without establishing what type of event occurred, it would be diffi... |
| V-253676 | | MariaDB must include additional, more detailed, organization-defined information in the audit records for audit events identified by type, location, or subject. | Information system auditing capability is critical for accurate forensic analysis. Reconstruction of harmful events or forensic analysis is not possib... |
| V-253677 | | 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. | It is critical that when MariaDB is at risk of failing to process audit logs as required, an action is taken to mitigate the failure. Audit processing... |
| V-253678 | | 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. | It is critical that when MariaDB is at risk of failing to process audit logs as required, it take action to mitigate the failure. Audit processing fai... |
| V-253679 | | The audit information produced by MariaDB must be protected from unauthorized read access. | If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity i... |
| V-253680 | | The audit information produced by MariaDB must be protected from unauthorized modification. | If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity i... |
| V-253681 | | The audit information produced by MariaDB must be protected from unauthorized deletion. | If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity i... |
| V-253682 | | MariaDB must protect its audit features from unauthorized access. | Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data.
Depending upon the log format and app... |
| V-253683 | | MariaDB must protect its audit configuration from unauthorized modification. | Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is ne... |
| V-253684 | | MariaDB must protect its audit features from unauthorized removal. | Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is ne... |
| V-253685 | | MariaDB must limit privileges to change software modules, to include stored procedures, functions and triggers, and links to software external to the DBMS. | If the system were to allow any user to make changes to software libraries, those changes might be implemented without undergoing the appropriate test... |
| V-253687 | | Database software, including MariaDB configuration files, must be stored in dedicated directories, separate from the host OS and other applications. | When dealing with change control issues, it should be noted any changes to the hardware, software, and/or firmware components of the information syste... |
| V-253688 | | 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. | Within the database, object ownership implies full privileges to the owned object, including the privilege to assign access to the owned objects to ot... |
| V-253689 | | 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. | If the MariaDB were to allow any user to make changes to database structure or logic, then those changes might be implemented without undergoing the a... |
| V-253690 | | Default demonstration and sample databases, database objects, and applications must be removed. | Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may no... |
| V-253691 | | Unused database components, DBMS software, and database objects must be removed. | Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may no... |
| V-253692 | | Access to external executables must be disabled or restricted. | Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may no... |
| V-253693 | | 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. | To prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within d... |
| V-253694 | | MariaDB must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users). | To ensure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and... |
| V-253696 | | If MariaDB authentication using passwords is employed, MariaDB must enforce the DOD standards for password lifetime. | OS/enterprise authentication and identification must be used (SRG-APP-000023-DB-000001). Native MariaDB authentication may be used only when circumsta... |
| V-253699 | | MariaDB, when utilizing PKI-based authentication, must validate certificates by performing RFC 5280-compliant certification path validation. | The DoD standard for authentication is DoD-approved PKI certificates.
A certificate's certification path is the path from the end entity certificate ... |
| V-253701 | | MariaDB must map PKI ID to an associated user account. | The DoD standard for authentication is DoD-approved PKI certificates. Once a PKI is validated, it is mapped to the DBMS user account for the authentic... |
| V-253704 | | The MariaDB must uniquely identify and authenticate nonorganizational users (or processes acting on behalf of nonorganizational users). | Nonorganizational users include all information system users other than organizational users, which include organizational employees or individuals th... |
| V-253705 | | MariaDB must separate user functionality (including user interface services) from database management functionality. | Information system management functionality includes functions necessary to administer databases, network components, workstations, or servers and typ... |
| V-253706 | | MariaDB must invalidate session identifiers upon user logout or other session termination. | Captured sessions can be reused in replay attacks. This requirement limits the ability of adversaries to capture and continue to employ previously val... |
| V-253707 | | MariaDB must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values. | Unique session IDs help to reduce predictability of said identifiers. Unique session IDs address man-in-the-middle attacks, including session hijackin... |
| V-253708 | | MariaDB must fail to a secure state if system initialization fails, shutdown fails, or aborts fail. | Failure to a known state can address safety or security in accordance with the mission/business needs of the organization.
Failure to a known secure... |
| V-253709 | | 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. | Failure to a known state can address safety or security in accordance with the mission/business needs of the organization.
Failure to a known secure ... |
| V-253711 | | Database contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy. | Applications, including MariaDB, must prevent unauthorized and unintended information transfer via shared system resources.
Data used for the develo... |
| V-253712 | | MariaDB must prevent unauthorized and unintended information transfer via shared system resources. | The purpose of this control is to prevent information, including encrypted representations of information, produced by the actions of a prior user/rol... |
| V-253713 | | Access to database files must be limited to relevant processes and to authorized, administrative users. | Applications, including MariaDB, must prevent unauthorized and unintended information transfer via shared system resources. Permitting only MariaDB pr... |
| V-253714 | | MariaDB must check the validity of all data inputs except those specifically identified by the organization. | Invalid user input occurs when a user inserts data or characters into an application's data entry fields and the application is unprepared to process ... |
| V-253715 | | MariaDB and associated applications must reserve the use of dynamic code execution for situations that require it. | With respect to database management systems, one class of threat is known as SQL Injection, or more generally, code injection. It takes advantage of t... |
| V-253716 | | 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. | With respect to database management systems, one class of threat is known as SQL Injection, or more generally, code injection. It takes advantage of t... |
| V-253717 | | MariaDB must automatically terminate a user's session after organization-defined conditions or trigger events requiring session disconnect. | This addresses the termination of user-initiated logical sessions in contrast to the termination of network connections that are associated with commu... |
| V-253718 | | MariaDB must provide logout functionality to allow the user to manually terminate a session initiated by that user. | If a user cannot explicitly end a DBMS session, the session may remain open and be exploited by an attacker; this is referred to as a zombie session.
... |
| V-253719 | | MariaDB must associate organization-defined types of security labels having organization-defined security label values with information in storage. | Without the association of security labels to information, there is no basis for MariaDB to make security-related access-control decisions.
Security ... |
| V-253720 | | MariaDB must associate organization-defined types of security labels having organization-defined security label values with information in process. | Without the association of security labels to information, there is no basis for MariaDB to make security-related access-control decisions.
Security ... |
| V-253721 | | MariaDB must associate organization-defined types of security labels having organization-defined security label values with information in transmission. | Without the association of security labels to information, there is no basis for MariaDB to make security-related access-control decisions.
Security ... |
| V-253722 | | MariaDB must enforce discretionary access control policies, as defined by the data owner, over defined subjects, and objects. | Discretionary Access Control (DAC) is based on the notion that individual users are owners of objects and therefore have discretion over who should be... |
| V-253723 | | MariaDB must prevent nonprivileged users from executing privileged functions, to include disabling, circumventing, or altering implemented security safeguards/countermeasures. | Preventing nonprivileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary ... |
| V-253724 | | Execution of software modules (to include stored procedures, functions, and triggers) with elevated privileges must be restricted to necessary cases only. | In certain situations, to provide required functionality, MariaDB needs to execute internal logic (stored procedures, functions, triggers, etc.) and/o... |
| V-253727 | | MariaDB must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements. | To ensure sufficient storage capacity for the audit logs, MariaDB must be able to allocate audit record storage capacity. Although another requirement... |
| V-253728 | | MariaDB must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75 percent of maximum audit record storage capacity. | Organizations are required to use a central log management system, so, under normal conditions, the audit space allocated to the DBMS on its own serve... |
| V-253729 | | MariaDB must provide an immediate real-time alert to appropriate support staff of all audit failure events requiring real-time alerts. | It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without a real-time aler... |
| V-253730 | | MariaDB must record time stamps, in audit records and application data, that can be mapped to Coordinated Universal Time (UTC, formerly GMT). | If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis.
Time stamps generate... |
| V-253731 | | MariaDB must prohibit user installation of logic modules (stored procedures, functions, triggers, views, etc.) without explicit privileged status. | Allowing regular users to install software, without explicit privileges, creates the risk that untested or potentially malicious software will be inst... |
| V-253732 | | MariaDB must enforce access restrictions associated with changes to the configuration of MariaDB or database(s). | Failure to provide logical access restrictions associated with changes to configuration may have significant effects on the overall security of the sy... |
| V-253733 | | MariaDB must produce audit records of its enforcement of access restrictions associated with changes to the configuration of the DBMS or database(s). | Without auditing the enforcement of access restrictions against changes to configuration, it would be difficult to identify attempted attacks and an a... |
| V-253734 | | 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. | Use of nonsecure network functions, ports, protocols, and services exposes the system to avoidable threats.... |
| V-253735 | | MariaDB must require users to reauthenticate when organization-defined circumstances or situations require reauthentication. | The DOD standard for authentication of an interactive user is the presentation of a Common Access Card (CAC) or other physical token bearing a valid, ... |
| V-253736 | | MariaDB must prohibit the use of cached authenticators after an organization-defined time period. | If cached authentication information is out-of-date, the validity of the authentication information may be questionable.
Each connection to the Maria... |
| V-253738 | | 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. | Only DoD-approved external PKIs have been evaluated to ensure that they have security controls and identity vetting procedures in place that are suffi... |
| V-253741 | | MariaDB must maintain the confidentiality and integrity of information during preparation for transmission. | Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, including, for example, during agg... |
| V-253742 | | MariaDB must maintain the confidentiality and integrity of information during reception. | Information can be either unintentionally or maliciously disclosed or modified during reception, including, for example, during aggregation, at protoc... |
| V-253743 | | When invalid inputs are received, MariaDB must behave in a predictable and documented manner that reflects organizational and system objectives. | A common vulnerability is unplanned behavior when invalid inputs are received. This requirement guards against adverse or unintended system behavior c... |
| V-253744 | | When updates are applied to the MariaDB software, any software components that have been replaced or made unnecessary must be removed. | Previous versions of MariaDB components that are not removed from the information system after updates have been installed may be exploited by adversa... |
| V-253745 | | 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). | Security flaws with software applications, including database management systems, are discovered daily. Vendors are constantly updating and patching t... |
| V-253746 | | MariaDB must be able to generate audit records when security objects are accessed. | Changes to the security configuration must be tracked.
This requirement applies to situations where security data is retrieved or modified via data m... |
| V-253747 | | MariaDB must generate audit records when unsuccessful attempts to access security objects occur. | Changes to the security configuration must be tracked.
This requirement applies to situations where security data is retrieved or modified via data m... |
| V-253748 | | MariaDB must generate audit records when categories of information (e.g., classification levels/security levels) are accessed. | Changes in categories of information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected.
For detailed... |
| V-253749 | | MariaDB must generate audit records when unsuccessful attempts to access categories of information (e.g., classification levels/security levels) occur. | Changes in categories of information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected.
To aid in di... |
| V-253750 | | MariaDB must generate audit records when privileges/permissions are added. | Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized elevation or restri... |
| V-253751 | | MariaDB must generate audit records when unsuccessful attempts to add privileges/permissions occur. | Failed attempts to change the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized atte... |
| V-253752 | | MariaDB must generate audit records when privileges/permissions are modified. | Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized elevation or restri... |
| V-253753 | | MariaDB must generate audit records when unsuccessful attempts to modify privileges/permissions occur. | Failed attempts to change the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized atte... |
| V-253754 | | MariaDB must generate audit records when security objects are modified. | Changes in the database objects (tables, views, procedures, functions) that record and control permissions, privileges, and roles granted to users and... |
| V-253755 | | MariaDB must generate audit records when unsuccessful attempts to modify security objects occur. | Changes in the database objects (tables, views, procedures, functions) that record and control permissions, privileges, and roles granted to users and... |
| V-253756 | | MariaDB must generate audit records when categories of information (e.g., classification levels/security levels) are modified. | Changes in categories of information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected.
For detailed... |
| V-253757 | | MariaDB must generate audit records when unsuccessful attempts to modify categories of information (e.g., classification levels/security levels) occur. | Changes in categories of information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected.
To aid in di... |
| V-253758 | | MariaDB must generate audit records when privileges/permissions are deleted. | Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized elevation or restri... |
| V-253759 | | MariaDB must generate audit records when unsuccessful attempts to delete privileges/permissions occur. | Failed attempts to change the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized atte... |
| V-253760 | | MariaDB must generate audit records when security objects are deleted. | The removal of security objects from the database/DBMS would seriously degrade a system s information assurance posture. If such an event occurs, it m... |
| V-253761 | | MariaDB must generate audit records when unsuccessful attempts to delete security objects occur. | The removal of security objects from the database/DBMS would seriously degrade a system s information assurance posture. If such an action is attempte... |
| V-253762 | | MariaDB must generate audit records when categories of information (e.g., classification levels/security levels) are deleted. | Changes in categories of information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected.
For detailed... |
| V-253763 | | MariaDB must generate audit records when unsuccessful attempts to delete categories of information (e.g., classification levels/security levels) occur. | Changes in categories of information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected.
To aid in di... |
| V-253764 | | MariaDB must generate audit records when successful logons or connections occur. | For completeness of forensic analysis, it is necessary to track who/what (a user or other principal) logs on to the DBMS.... |
| V-253765 | | MariaDB must generate audit records when unsuccessful logons or connection attempts occur. | For completeness of forensic analysis, it is necessary to track failed attempts to log on to MariaDB. While positive identification may not be possibl... |
| V-253766 | | MariaDB must generate audit records for all privileged activities or other system-level access. | Without tracking privileged activity, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify th... |
| V-253767 | | MariaDB must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur. | Without tracking privileged activity, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify th... |
| V-253768 | | MariaDB must generate audit records showing starting and ending time for user access to the database(s). | For completeness of forensic analysis, it is necessary to know how long a user's (or other principal's) connection to MariaDB lasts. This can be achie... |
| V-253769 | | MariaDB must generate audit records when concurrent logons/connections by the same user from different workstations occur. | For completeness of forensic analysis, it is necessary to track who logs on to MariaDB.
Concurrent connections by the same user from multiple worksta... |
| V-253770 | | MariaDB must be able to generate audit records when successful accesses to objects occur. | Without tracking all or selected types of access to all or selected objects (tables, views, procedures, functions, etc.), it would be difficult to est... |
| V-253771 | | MariaDB must generate audit records when unsuccessful accesses to objects occur. | Without tracking all or selected types of access to all or selected objects (tables, views, procedures, functions, etc.), it would be difficult to est... |
| V-253772 | | MariaDB must generate audit records for all direct access to the database(s). | In this context, direct access is any query, command, or call to MariaDB that comes from any source other than the application(s) that it supports. Ex... |
| V-253773 | | MariaDB must implement NIST FIPS 140-2 validated cryptographic modules to provision digital signatures. | Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptogr... |
| V-253774 | | MariaDB must implement NIST FIPS 140-2 validated cryptographic modules to generate and validate cryptographic hashes. | Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptogr... |
| V-253775 | | 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. | Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptogr... |
| V-253776 | | 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. | Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Off-loading is a common process in information s... |
| V-253666 | | MariaDB must limit the number of concurrent sessions to an organization-defined number per user for all accounts and/or account types. | Database management includes the ability to control the number of users and user sessions utilizing MariaDB. Unlimited concurrent connections to Maria... |
| V-253667 | | MariaDB must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals. | Enterprise environments make account management for applications and databases challenging and complex. A manual process for account management functi... |
| V-253668 | | MariaDB must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. | Authentication with a DoD-approved PKI certificate does not necessarily imply authorization to access MariaDB. To mitigate the risk of unauthorized ac... |
| V-253686 | | The MariaDB software installation account must be restricted to authorized users. | When dealing with change control issues, it should be noted any changes to the hardware, software, and/or firmware components of the information syste... |
| V-253695 | | If MariaDB authentication, using passwords, is employed, then MariaDB must enforce the DOD standards for password complexity. | OS/enterprise authentication and identification must be used (SRG-APP-000023-DB-000001). Native MariaDB authentication may be used only when circumsta... |
| V-253697 | | If passwords are used for authentication, MariaDB must store only hashed, salted representations of passwords. | The DOD standard for authentication is DOD-approved PKI certificates.
Authentication based on User ID and Password may be used only when it is not po... |
| V-253698 | | If passwords are used for authentication, MariaDB must transmit only encrypted representations of passwords. | The DoD standard for authentication is DoD-approved PKI certificates.
Authentication based on User ID and Password may be used only when it is not po... |
| V-253700 | | MariaDB must enforce authorized access to all PKI private keys stored/used by the DBMS. | The DoD standard for authentication is DoD-approved PKI certificates. PKI certificate-based authentication is performed by requiring the certificate h... |
| V-253702 | | MariaDB must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals. | The DoD standard for authentication is DoD-approved PKI certificates.
Normally, with PKI authentication, the interaction with the user for authentica... |
| V-253703 | | MariaDB must use NIST FIPS 140-2 validated cryptographic modules for cryptographic operations. | Use of weak or not validated cryptographic algorithms undermines the purposes of utilizing encryption and digital signatures to protect data. Weak alg... |
| V-253710 | | MariaDB must protect the confidentiality and integrity of all information at rest. | This control is intended to address the confidentiality and integrity of information at rest in nonmobile devices and covers user information and syst... |
| V-253737 | | MariaDB must use NSA-approved cryptography to protect classified information in accordance with the data owner's requirements. | Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptogr... |
| V-253739 | | 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. | MariaDB’s handling of data requiring data at rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification... |
| V-253740 | | MariaDB must implement cryptographic mechanisms preventing the unauthorized disclosure of organization-defined information at rest on organization-defined information system components. | MariaDB’s handling of data requiring data at rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification... |
| V-265882 | | MariaDB products must be a version supported by the vendor. | Unsupported commercial and database systems should not be used because fixes to newly identified bugs will not be implemented by the vendor. The lack ... |
