| Checked | Name | Title |
|---|
| ☐ | SV-235095r638812_rule | 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. |
| ☐ | SV-235096r638812_rule | 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. |
| ☐ | SV-235097r638812_rule | MySQL Database Server 8.0 must produce audit records containing sufficient information to establish what type of events occurred. |
| ☐ | SV-235098r638812_rule | 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. |
| ☐ | SV-235099r638812_rule | The audit information produced by the MySQL Database Server 8.0 must be protected from unauthorized read access. |
| ☐ | SV-235100r638812_rule | The audit information produced by the MySQL Database Server 8.0 must be protected from unauthorized modification. |
| ☐ | SV-235101r638812_rule | The audit information produced by the MySQL Database Server 8.0 must be protected from unauthorized deletion. |
| ☐ | SV-235102r638812_rule | The MySQL Database Server 8.0 must protect against a user falsely repudiating having performed organization-defined actions. |
| ☐ | SV-235103r638812_rule | The MySQL Database Server 8.0 must be configured to provide audit record generation capability for DoD-defined auditable events within all database components. |
| ☐ | SV-235104r638812_rule | 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. |
| ☐ | SV-235105r638812_rule | The MySQL Database Server 8.0 must be able to generate audit records when privileges/permissions are retrieved. |
| ☐ | SV-235106r638812_rule | The MySQL Database Server 8.0 must be able to generate audit records when unsuccessful attempts to retrieve privileges/permissions occur. |
| ☐ | SV-235107r638812_rule | The MySQL Database Server 8.0 must be able to generate audit records when security objects are accessed. |
| ☐ | SV-235108r638812_rule | The MySQL Database Server 8.0 must generate audit records when unsuccessful attempts to access security objects occur. |
| ☐ | SV-235109r638812_rule | The MySQL Database Server 8.0 must generate audit records when categories of information (e.g., classification levels/security levels) are accessed. |
| ☐ | SV-235110r638812_rule | 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. |
| ☐ | SV-235111r638812_rule | The MySQL Database Server 8.0 must generate audit records when privileges/permissions are added. |
| ☐ | SV-235112r638812_rule | The MySQL Database Server 8.0 must generate audit records when unsuccessful attempts to add privileges/permissions occur. |
| ☐ | SV-235113r638812_rule | The MySQL Database Server 8.0 must generate audit records when privileges/permissions are modified. |
| ☐ | SV-235114r638812_rule | The MySQL Database Server 8.0 must generate audit records when unsuccessful attempts to modify privileges/permissions occur. |
| ☐ | SV-235115r638812_rule | The MySQL Database Server 8.0 must generate audit records when security objects are modified. |
| ☐ | SV-235116r638812_rule | The MySQL Database Server 8.0 must generate audit records when unsuccessful attempts to modify security objects occur. |
| ☐ | SV-235117r638812_rule | The MySQL Database Server 8.0 must generate audit records when categories of information (e.g., classification levels/security levels) are modified. |
| ☐ | SV-235118r638812_rule | 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. |
| ☐ | SV-235119r638812_rule | The MySQL Database Server 8.0 must generate audit records when privileges/permissions are deleted. |
| ☐ | SV-235120r638812_rule | The MySQL Database Server 8.0 must generate audit records when unsuccessful attempts to delete privileges/permissions occur. |
| ☐ | SV-235121r638812_rule | The MySQL Database Server 8.0 must generate audit records when security objects are deleted. |
| ☐ | SV-235122r638812_rule | The MySQL Database Server 8.0 must generate audit records when unsuccessful attempts to delete security objects occur. |
| ☐ | SV-235123r638812_rule | The MySQL Database Server 8.0 must generate audit records when categories of information (e.g., classification levels/security levels) are deleted. |
| ☐ | SV-235124r638812_rule | 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. |
| ☐ | SV-235125r638812_rule | The MySQL Database Server 8.0 must generate audit records when successful logons or connections occur. |
| ☐ | SV-235126r638812_rule | The MySQL Database Server 8.0 must generate audit records when unsuccessful logons or connection attempts occur. |
| ☐ | SV-235127r638812_rule | The MySQL Database Server 8.0 must generate audit records for all privileged activities or other system-level access. |
| ☐ | SV-235128r638812_rule | The MySQL Database Server 8.0 must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur. |
| ☐ | SV-235129r638812_rule | The MySQL Database Server 8.0 must generate audit records showing starting and ending time for user access to the database(s). |
| ☐ | SV-235130r638812_rule | The MySQL Database Server 8.0 must generate audit records when concurrent logons/connections by the same user from different workstations. |
| ☐ | SV-235131r638812_rule | The MySQL Database Server 8.0 must be able to generate audit records when successful accesses to objects occur. |
| ☐ | SV-235132r638812_rule | The MySQL Database Server 8.0 must generate audit records when unsuccessful accesses to objects occur. |
| ☐ | SV-235133r638812_rule | The MySQL Database Server 8.0 must generate audit records for all direct access to the database(s). |
| ☐ | SV-235134r638812_rule | The MySQL Database Server 8.0, when utilizing PKI-based authentication, must validate certificates by performing RFC 5280-compliant certification path validation. |
| ☐ | SV-235135r638812_rule | The MySQL Database Server 8.0 must enforce authorized access to all PKI private keys stored/utilized by the MySQL Database Server 8.0. |
| ☐ | SV-235136r638812_rule | The MySQL Database Server 8.0 must map the PKI-authenticated identity to an associated user account. |
| ☐ | SV-235137r638812_rule | If Database Management System (DBMS) authentication using passwords is employed, the DBMS must enforce the DoD standards for password complexity and lifetime. |
| ☐ | SV-235138r638812_rule | If passwords are used for authentication, the MySQL Database Server 8.0 must store only hashed, salted representations of passwords. |
| ☐ | SV-235139r638812_rule | If passwords are used for authentication, the MySQL Database Server 8.0 must transmit only encrypted representations of passwords. |
| ☐ | SV-235140r638812_rule | 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. |
| ☐ | SV-235141r638812_rule | 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. |
| ☐ | SV-235142r638812_rule | 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. |
| ☐ | SV-235143r638812_rule | Default demonstration and sample databases, database objects, and applications must be removed. |
| ☐ | SV-235144r638812_rule | Unused database components, MySQL Database Server 8.0 software, and database objects must be removed. |
| ☐ | SV-235145r638812_rule | Unused database components which are integrated in the MySQL Database Server 8.0 and cannot be uninstalled must be disabled. |
| ☐ | SV-235146r638812_rule | 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. |
| ☐ | SV-235147r638812_rule | The MySQL Database Server 8.0 must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users). |
| ☐ | SV-235148r638812_rule | The MySQL Database Server 8.0 must use NIST FIPS 140-2 validated cryptographic modules for cryptographic operations. |
| ☐ | SV-235149r638812_rule | The MySQL Database Server 8.0 must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users). |
| ☐ | SV-235150r638812_rule | The MySQL Database Server 8.0 must separate user functionality (including user interface services) from database management functionality. |
| ☐ | SV-235151r638812_rule | The MySQL Database Server 8.0 must isolate security functions from non-security functions. |
| ☐ | SV-235152r638812_rule | Database contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy. |
| ☐ | SV-235153r638812_rule | Access to database files must be limited to relevant processes and to authorized, administrative users. |
| ☐ | SV-235154r638812_rule | 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. |
| ☐ | SV-235155r638812_rule | The MySQL Database Server 8.0 must protect the confidentiality and integrity of all information at rest. |
| ☐ | SV-235156r638812_rule | The MySQL Database Server 8.0 must check the validity of all data inputs except those specifically identified by the organization. |
| ☐ | SV-235157r638812_rule | The MySQL Database Server 8.0 and associated applications must reserve the use of dynamic code execution for situations that require it. |
| ☐ | SV-235158r638812_rule | 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. |
| ☐ | SV-235159r638812_rule | The MySQL Database Server 8.0 must initiate session auditing upon startup. |
| ☐ | SV-235160r638812_rule | The MySQL Database Server 8.0 must protect its audit features from unauthorized access. |
| ☐ | SV-235161r638812_rule | The MySQL Database Server 8.0 must protect its audit configuration from unauthorized modification. |
| ☐ | SV-235162r638812_rule | The MySQL Database Server 8.0 must protect its audit features from unauthorized removal. |
| ☐ | SV-235163r638812_rule | 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. |
| ☐ | SV-235164r638812_rule | The MySQL Database Server 8.0 software installation account must be restricted to authorized users. |
| ☐ | SV-235165r638812_rule | 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. |
| ☐ | SV-235166r638812_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 MySQL Database Server 8.0, etc.) must be restricted to authorized users. |
| ☐ | SV-235167r638812_rule | 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. |
| ☐ | SV-235168r638812_rule | The MySQL Database Server 8.0 must prohibit user installation of logic modules (stored procedures, functions, triggers, views, etc.) without explicit privileged status. |
| ☐ | SV-235169r638812_rule | 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). |
| ☐ | SV-235170r638812_rule | 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). |
| ☐ | SV-235171r638812_rule | The MySQL Database Server 8.0 must utilize centralized management of the content captured in audit records generated by all components of the MySQL Database Server 8.0. |
| ☐ | SV-235172r638812_rule | The MySQL Database Server 8.0 must provide centralized configuration of the content to be captured in audit records generated by all components of the MySQL Database Server 8.0. |
| ☐ | SV-235173r638812_rule | The MySQL Database Server 8.0 must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements. |
| ☐ | SV-235174r638812_rule | 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. |
| ☐ | SV-235175r638812_rule | 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. |
| ☐ | SV-235176r638812_rule | The MySQL Database Server 8.0 must provide an immediate real-time alert to appropriate support staff of all audit log failures. |
| ☐ | SV-235177r638812_rule | The MySQL Database Server 8.0 must prohibit the use of cached authenticators after an organization-defined time period. |
| ☐ | SV-235178r638812_rule | The MySQL Database Server 8.0 must require users to reauthenticate when organization-defined circumstances or situations require reauthentication. |
| ☐ | SV-235179r638812_rule | The MySQL Database Server 8.0 must enforce discretionary access control policies, as defined by the data owner, over defined subjects and objects. |
| ☐ | SV-235180r638812_rule | Execution of software modules (to include stored procedures, functions, and triggers) with elevated privileges must be restricted to necessary cases only. |
| ☐ | SV-235181r638812_rule | 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. |
| ☐ | SV-235182r638812_rule | The MySQL Database Server 8.0 must associate organization-defined types of security labels having organization-defined security label values with information in storage. |
| ☐ | SV-235183r638812_rule | The MySQL Database Server 8.0 must associate organization-defined types of security labels having organization-defined security label values with information in process. |
| ☐ | SV-235184r638812_rule | The MySQL Database Server 8.0 must associate organization-defined types of security labels having organization-defined security label values with information in transmission. |
| ☐ | SV-235185r638812_rule | The MySQL Database Server 8.0 must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect. |
| ☐ | SV-235186r638812_rule | The MySQL Database Server 8.0 must maintain the confidentiality and integrity of information during preparation for transmission. |
| ☐ | SV-235187r638812_rule | The MySQL Database Server 8.0 must use NSA-approved cryptography to protect classified information in accordance with the data owner's requirements. |
| ☐ | SV-235188r638812_rule | The MySQL Database Server 8.0 must implement NIST FIPS 140-2 validated cryptographic modules to provision digital signatures. |
| ☐ | SV-235189r638812_rule | The MySQL Database Server 8.0 must implement NIST FIPS 140-2 validated cryptographic modules to generate and validate cryptographic hashes. |
| ☐ | SV-235190r638812_rule | The MySQL Database Server 8.0 must implement NIST FIPS 140-2 validated cryptographic modules to protect unclassified information requiring confidentiality and cryptographic protection, in accordance with the data owner's requirements. |
| ☐ | SV-235191r638812_rule | 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. |
| ☐ | SV-235192r638812_rule | 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. |
| ☐ | SV-235193r638812_rule | 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. |
| ☐ | SV-235194r638812_rule | 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). |
| ☐ | SV-235195r638812_rule | 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. |
STIGQter: STIG Summary: