| V-235095 | | MySQL Database Server 8.0 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-235135 | | The MySQL Database Server 8.0 must enforce authorized access to all PKI private keys stored/utilized by the MySQL Database Server 8.0. | The DoD standard for authentication is DoD-approved PKI certificates. PKI certificate-based authentication is performed by requiring the certificate h... |
| V-235137 | | If Database Management System (DBMS) authentication using passwords is employed, the DBMS must enforce the DOD standards for password complexity and lifetime. | OS/enterprise authentication and identification must be used (SRG-APP-000023-DB-000001). Native DBMS authentication may be used only when circumstance... |
| V-235139 | | If passwords are used for authentication, the MySQL Database Server 8.0 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-235140 | | The MySQL Database Server 8.0 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-235141 | | The MySQL Database Server 8.0 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 the Database Management System (DBMS). To mitiga... |
| V-235148 | | The MySQL Database Server 8.0 must use NIST FIPS 140-2 or 140-3 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-235155 | | The MySQL Database Server 8.0 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 non-mobile devices and covers user information and sys... |
| V-235189 | | The MySQL Database Server 8.0 must implement NIST FIPS 140-2 or 140-3 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-235192 | | The MySQL Database Server 8.0 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. | Database Management Systems (DBMSs) handling data requiring "data at rest" protections must employ cryptographic mechanisms to prevent unauthorized di... |
| V-235193 | | The MySQL Database Server 8.0 must implement cryptographic mechanisms preventing the unauthorized disclosure of organization-defined information at rest on organization-defined information system components. | Database Management Systems (DBMSs) handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disc... |
| V-265876 | | MySQL database 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 ... |
| V-235096 | | MySQL Database Server 8.0 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 a Database Management System (DBMS). Unlimited con... |
| V-235097 | | MySQL Database Server 8.0 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-235098 | | The MySQL Database Server 8.0 must include additional, more detailed, organizationally 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-235099 | | The audit information produced by the MySQL Database Server 8.0 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-235100 | | The audit information produced by the MySQL Database Server 8.0 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-235101 | | The audit information produced by the MySQL Database Server 8.0 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-235102 | | The MySQL Database Server 8.0 must protect against a user falsely repudiating having performed organization-defined actions. | Non-repudiation of actions taken is required to maintain data integrity. Examples of particular actions taken by individuals include creating informat... |
| V-235103 | | The MySQL Database Server 8.0 must be configured to provide audit record generation capability for DoD-defined auditable events within all 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-235104 | | The MySQL Database Server 8.0 must allow only the Information System Security Manager (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-235105 | | The MySQL Database Server 8.0 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-235106 | | The MySQL Database Server 8.0 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-235107 | | The MySQL Database Server 8.0 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-235108 | | The MySQL Database Server 8.0 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-235109 | | The MySQL Database Server 8.0 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-235110 | | The MySQL Database Server 8.0 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-235111 | | The MySQL Database Server 8.0 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-235112 | | The MySQL Database Server 8.0 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-235113 | | The MySQL Database Server 8.0 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-235114 | | The MySQL Database Server 8.0 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-235115 | | The MySQL Database Server 8.0 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-235116 | | The MySQL Database Server 8.0 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-235117 | | The MySQL Database Server 8.0 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-235118 | | The MySQL Database Server 8.0 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-235119 | | The MySQL Database Server 8.0 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-235120 | | The MySQL Database Server 8.0 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-235121 | | The MySQL Database Server 8.0 must generate audit records when security objects are deleted. | The removal of security objects from the database/Database Management System (DBMS) would seriously degrade a system's information assurance posture. ... |
| V-235122 | | The MySQL Database Server 8.0 must generate audit records when unsuccessful attempts to delete security objects occur. | The removal of security objects from the database/Database Management System (DBMS) would seriously degrade a system's information assurance posture. ... |
| V-235123 | | The MySQL Database Server 8.0 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-235124 | | The MySQL Database Server 8.0 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-235125 | | The MySQL Database Server 8.0 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 Database Management System (DBMS).... |
| V-235126 | | The MySQL Database Server 8.0 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 the Database Management System (DBMS). While positive ide... |
| V-235127 | | The MySQL Database Server 8.0 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-235128 | | The MySQL Database Server 8.0 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-235129 | | The MySQL Database Server 8.0 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 the Database Management System (... |
| V-235130 | | The MySQL Database Server 8.0 must generate audit records when concurrent logons/connections by the same user from different workstations. | For completeness of forensic analysis, it is necessary to track who logs on to the Database Management System (DBMS).
Concurrent connections by the s... |
| V-235131 | | The MySQL Database Server 8.0 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-235132 | | The MySQL Database Server 8.0 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-235133 | | The MySQL Database Server 8.0 must generate audit records for all direct access to the database(s). | In this context, direct access is any query, command, or call to the Database Management System (DBMS) that comes from any source other than the appli... |
| V-235134 | | The MySQL Database Server 8.0, 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-235136 | | The MySQL Database Server 8.0 must map the PKI-authenticated identity to an associated user account. | The DoD standard for authentication is DoD-approved PKI certificates. Once a PKI certificate has been validated, it must be mapped to a Database Manag... |
| V-235138 | | If passwords are used for authentication, the MySQL Database Server 8.0 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-235142 | | The MySQL Database Server 8.0 must be configured in accordance with the security configuration settings based on DoD security configuration and implementation guidance, including STIGs, NSA configuration guides, CTOs, DTMs, and IAVMs. | Configuring the Database Management System (DBMS) to implement organization-wide security implementation guides and security checklists ensures compli... |
| V-235143 | | 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-235144 | | Unused database components, MySQL Database Server 8.0 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-235145 | | Unused database components which are integrated in the MySQL Database Server 8.0 and cannot be uninstalled must be disabled. | 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-235146 | | The MySQL Database Server 8.0 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-235147 | | The MySQL Database Server 8.0 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-235149 | | The MySQL Database Server 8.0 must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users). | Non-organizational users include all information system users other than organizational users, which include organizational employees or individuals t... |
| V-235150 | | The MySQL Database Server 8.0 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 ty... |
| V-235151 | | The MySQL Database Server 8.0 must isolate security functions from non-security functions. | An isolation boundary provides access control and protects the integrity of the hardware, software, and firmware that perform security functions.
Se... |
| V-235152 | | Database contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy. | Applications, including DBMSs, must prevent unauthorized and unintended information transfer via shared system resources.
Data used for the developm... |
| V-235153 | | Access to database files must be limited to relevant processes and to authorized, administrative users. | Applications, including DBMSs, must prevent unauthorized and unintended information transfer via shared system resources. Permitting only DBMS process... |
| V-235154 | | The MySQL Database Server 8.0 must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values. | One class of man-in-the-middle, or session hijacking, attack involves the adversary guessing at valid session identifiers based on patterns in identif... |
| V-235156 | | The MySQL Database Server 8.0 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-235157 | | The MySQL Database Server 8.0 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-235158 | | The MySQL Database Server 8.0 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-235159 | | The MySQL Database Server 8.0 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-235160 | | The MySQL Database Server 8.0 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-235161 | | The MySQL Database Server 8.0 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-235162 | | The MySQL Database Server 8.0 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-235163 | | The MySQL Database Server 8.0 must limit privileges to change software modules, to include stored procedures, functions and triggers, and links to software external to the MySQL Database Server 8.0. | If the system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate... |
| V-235164 | | The MySQL Database Server 8.0 software installation account must be restricted to authorized users. | When dealing with change control issues, it must be noted any changes to the hardware, software, and/or firmware components of the information system ... |
| V-235165 | | Database software, including MySQL Database Server 8.0 configuration files, must be stored in dedicated directories, or DASD pools (remove), 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-235166 | | 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 MySQL Database Server 8.0, etc.) must be restricted to authorized users. | If the DBMS were to allow any user to make changes to database structure or logic, then those changes might be implemented without undergoing the appr... |
| V-235167 | | The MySQL Database Server 8.0 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-235168 | | The MySQL Database Server 8.0 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-235169 | | The MySQL Database Server 8.0 must enforce access restrictions associated with changes to the configuration of the MySQL Database Server 8.0 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-235170 | | The MySQL Database Server 8.0 must produce audit records of its enforcement of access restrictions associated with changes to the configuration of the MySQL Database Server 8.0 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-235173 | | The MySQL Database Server 8.0 must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements. | To ensure sufficient storage capacity for the audit logs, the Database Management System (DBMS) must be able to allocate audit record storage capacity... |
| V-235174 | | The MySQL Database Server 8.0 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-235175 | | The MySQL Database Server 8.0 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-235176 | | The MySQL Database Server 8.0 must provide an immediate real-time alert to appropriate support staff of all audit log failures. | 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-235177 | | The MySQL Database Server 8.0 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.... |
| V-235178 | | The MySQL Database Server 8.0 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-235179 | | The MySQL Database Server 8.0 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 ... |
| V-235180 | | 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, a Database Management System (DBMS) needs to execute internal logic (stored procedures, func... |
| V-235181 | | The MySQL Database Server 8.0 must prevent non-privileged users from executing privileged functions, to include disabling, circumventing, or altering implemented security safeguards/countermeasures. | Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary... |
| V-235182 | | The MySQL Database Server 8.0 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 the DBMS to make security-related access-control decisions.
Security... |
| V-235183 | | The MySQL Database Server 8.0 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 the Database Management System (DBMS) to make security-related access... |
| V-235184 | | The MySQL Database Server 8.0 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 the DBMS to make security-related access-control decisions.
Security... |
| V-235185 | | The MySQL Database Server 8.0 must automatically terminate a user 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 associated with communications... |
| V-235186 | | The MySQL Database Server 8.0 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-235187 | | The MySQL Database Server 8.0 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-235188 | | The MySQL Database Server 8.0 must implement NIST FIPS 140-2 or 140-3 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-235190 | | The MySQL Database Server 8.0 must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to protect unclassified information requiring confidentiality and cryptographic protection, 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-235191 | | The MySQL Database Server 8.0 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 they have security controls and identity vetting procedures in place that are sufficient... |
| V-235194 | | Security-relevant software updates to the MySQL Database Server 8.0 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-235195 | | When invalid inputs are received, the MySQL Database Server 8.0 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... |
