Oracle MySQL 8.0 Security Technical Implementation Guide

Description

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

Details

Version / Release: V1R2

Published: 2021-12-10

Updated At: 2022-04-06 01:10:36

Compare/View Releases

Select any two versions of this STIG to compare the individual requirements

Select any old version/release of this STIG to view the previous requirements

Actions

Download

Filter

Findings
Severity Open Not Reviewed Not Applicable Not a Finding
Overall 0 0 0 0
Low 0 0 0 0
Medium 0 0 0 0
High 0 0 0 0
Drop CKL or SCAP (XCCDF) results here.

    Vuln Rule Version CCI Severity Title Description Status Finding Details Comments
    SV-235095r623407_rule MYS8-00-000100 CCI-000015 HIGH 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 functions adds the risk of a potential oversight or other error. Managing accounts for the same person in multi
    SV-235096r623410_rule MYS8-00-000200 CCI-000054 MEDIUM 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 concurrent connections to the DBMS could allow a successful Denial of Service (DoS) attack by exhausting con
    SV-235097r623413_rule MYS8-00-000300 CCI-000130 MEDIUM 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 difficult to establish, correlate, and investigate the events relating to an incident or identify those respon
    SV-235098r623416_rule MYS8-00-000800 CCI-000135 MEDIUM 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 possible if audit records do not contain enough information. To support analysis, some types of events will nee
    SV-235099r623419_rule MYS8-00-001200 CCI-000162 MEDIUM 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 is difficult, if not impossible, to achieve. In addition, access to audit records provides information an
    SV-235100r623422_rule MYS8-00-001300 CCI-000163 MEDIUM 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 is impossible to achieve. To ensure the veracity of audit data the information system and/or the applica
    SV-235101r623425_rule MYS8-00-001400 CCI-000164 MEDIUM 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 is impossible to achieve. To ensure the veracity of audit data, the information system and/or the applic
    SV-235102r623428_rule MYS8-00-001500 CCI-000166 MEDIUM 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 information, sending a message, approving information (e.g., indicating concurrence or signing a contract), and r
    SV-235103r623431_rule MYS8-00-001600 CCI-000169 MEDIUM 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 identify those responsible for one. Audit records can be generated from various components within the
    SV-235104r623434_rule MYS8-00-001700 CCI-000171 MEDIUM 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 interfere with the auditing of critical events. Suppression of auditing could permit an adversary to eva
    SV-235105r623437_rule MYS8-00-001800 CCI-000172 MEDIUM 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 configure auditing to do this. Database Management Systems (DBMSs) typically make such information available
    SV-235106r623440_rule MYS8-00-001900 CCI-000172 MEDIUM 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 configure auditing to do this. Database Management Systems (DBMSs) typically make such information available
    SV-235107r623443_rule MYS8-00-002000 CCI-000172 MEDIUM 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 manipulation operations, as opposed to via specialized security functionality. In SQL environment, types
    SV-235108r623446_rule MYS8-00-002100 CCI-000172 MEDIUM 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 manipulation operations, as opposed to via specialized security functionality. In a SQL environment, type
    SV-235109r623449_rule MYS8-00-002200 CCI-000172 MEDIUM 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 information on categorizing information, refer to FIPS Publication 199, Standards for Security Categoriz
    SV-235110r623452_rule MYS8-00-002300 CCI-000172 MEDIUM 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 diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones. For detail
    SV-235111r623455_rule MYS8-00-002400 CCI-000172 MEDIUM 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 restriction of individuals and groups privileges could go undetected. Elevated privileges give users access to
    SV-235112r623458_rule MYS8-00-002500 CCI-000172 MEDIUM 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 attempts to elevate or restrict individuals and groups privileges could go undetected. In a SQL environment,
    SV-235113r623461_rule MYS8-00-002600 CCI-000172 MEDIUM 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 restriction of individuals and groups privileges could go undetected. Elevated privileges give users access to
    SV-235114r623464_rule MYS8-00-002700 CCI-000172 MEDIUM 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 attempts to elevate or restrict individual and group privileges could go undetected. In an SQL environmen
    SV-235115r623467_rule MYS8-00-002800 CCI-000172 MEDIUM 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 roles must be tracked. Without an audit trail, unauthorized changes to the security subsystem could go u
    SV-235116r623470_rule MYS8-00-002900 CCI-000172 MEDIUM 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 roles must be tracked. Without an audit trail, unauthorized changes to the security subsystem could go u
    SV-235117r623473_rule MYS8-00-003000 CCI-000172 MEDIUM 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 information on categorizing information, refer to FIPS Publication 199, Standards for Security Categoriz
    SV-235118r623476_rule MYS8-00-003100 CCI-000172 MEDIUM 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 diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones. For detail
    SV-235119r623479_rule MYS8-00-003200 CCI-000172 MEDIUM 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 restriction of individual and group privileges could go undetected. Elevated privileges give users access to in
    SV-235120r623482_rule MYS8-00-003300 CCI-000172 MEDIUM 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 attempts to elevate or restrict individuals and groups privileges could go undetected. In a SQL environme
    SV-235121r623485_rule MYS8-00-003400 CCI-000172 MEDIUM 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. If such an event occurs, it must be logged.
    SV-235122r623488_rule MYS8-00-003500 CCI-000172 MEDIUM 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. If such an action is attempted, it must be logged. To aid in diagnosis, it is necessary to keep track of
    SV-235123r623491_rule MYS8-00-003600 CCI-000172 MEDIUM 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 information on categorizing information, refer to FIPS Publication 199, Standards for Security Categoriz
    SV-235124r623494_rule MYS8-00-003700 CCI-000172 MEDIUM 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 diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones. For detail
    SV-235125r623497_rule MYS8-00-003800 CCI-000172 MEDIUM 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).
    SV-235126r623500_rule MYS8-00-003900 CCI-000172 MEDIUM 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 identification may not be possible in a case of failed authentication, as much information as possible about
    SV-235127r623503_rule MYS8-00-004000 CCI-000172 MEDIUM 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 those responsible for one. System documentation should include a definition of the functionality consider
    SV-235128r623506_rule MYS8-00-004100 CCI-000172 MEDIUM 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 those responsible for one. System documentation should include a definition of the functionality consider
    SV-235129r623509_rule MYS8-00-004200 CCI-000172 MEDIUM 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 (DBMS) lasts. This can be achieved by recording disconnections, in addition to logons/connections, in the
    SV-235130r623512_rule MYS8-00-004300 CCI-000172 MEDIUM 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 same user from multiple workstations may be valid use of the system; or such connections may be due to imp
    SV-235131r623515_rule MYS8-00-004400 CCI-000172 MEDIUM 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 establish, correlate, and investigate the events relating to an incident, or identify those responsible for
    SV-235132r623518_rule MYS8-00-004500 CCI-000172 MEDIUM 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 establish, correlate, and investigate the events relating to an incident or identify those responsible for o
    SV-235133r623521_rule MYS8-00-004600 CCI-000172 MEDIUM 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 application(s) that it supports. Examples would be the command line or a database management utility program.
    SV-235134r623524_rule MYS8-00-004700 CCI-000185 MEDIUM 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 to a trusted root certification authority (CA). Certification path validation is necessary for a relyin
    SV-235135r623527_rule MYS8-00-004800 CCI-000186 HIGH 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 holder to cryptographically prove possession of the corresponding private key. If the private key is stol
    SV-235136r623530_rule MYS8-00-004900 CCI-000187 MEDIUM 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 Management System (DBMS) user account for the authenticated identity to be meaningful to the DBMS and useful f
    SV-235137r623533_rule MYS8-00-005000 CCI-000192 HIGH 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 circumstances make it unavoidable; and must be documented and Authorizing Official (AO)-approved. The DoD standard f
    SV-235138r623536_rule MYS8-00-005100 CCI-000196 MEDIUM 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 possible to employ a PKI certificate, and requires Authorizing Official (AO) approval. In such cases, data
    SV-235139r623539_rule MYS8-00-005200 CCI-000197 HIGH 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 possible to employ a PKI certificate, and requires Authorizing Official (AO) approval. In such cases, pass
    SV-235140r623542_rule MYS8-00-005300 CCI-000206 HIGH 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 authentication will be handled by a software component separate from the Database Management System (DBMS), such as
    SV-235141r623545_rule MYS8-00-005400 CCI-000213 HIGH 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 mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificate
    SV-235142r623548_rule MYS8-00-005500 CCI-000366 MEDIUM 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 compliance with federal standards and establishes a common security baseline across DoD that reflects the most
    SV-235143r623551_rule MYS8-00-005600 CCI-000381 MEDIUM 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 not be necessary to support essential organizational operations (e.g., key missions, functions). It is det
    SV-235144r623554_rule MYS8-00-005700 CCI-000381 MEDIUM 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 not be necessary to support essential organizational operations (e.g., key missions, functions). It is det
    SV-235145r623557_rule MYS8-00-005800 CCI-000381 MEDIUM 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 not be necessary to support essential organizational operations (e.g., key missions, functions). It is d
    SV-235146r623560_rule MYS8-00-006000 CCI-000382 MEDIUM 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 data types), organizations must disable or restrict unused or unnecessary physical and logical ports/proto
    SV-235147r623563_rule MYS8-00-006100 CCI-000764 MEDIUM 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 compromise of the system. Organizational users include organizational employees or individuals the org
    SV-235148r623566_rule MYS8-00-006200 CCI-000803 HIGH The MySQL Database Server 8.0 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 algorithms can be easily broken and not validated cryptographic modules may not implement algorithms correct
    SV-235149r623569_rule MYS8-00-006300 CCI-000804 MEDIUM 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 the organization deems to have equivalent status of employees (e.g., contractors, guest researchers, indiv
    SV-235150r623572_rule MYS8-00-006400 CCI-001082 MEDIUM 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 typically requires privileged user access. The separation of user functionality from information system m
    SV-235151r623575_rule MYS8-00-006500 CCI-001084 MEDIUM 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. Security functions are the hardware, software, and/or firmware of the information system responsible for en
    SV-235152r623578_rule MYS8-00-006600 CCI-001090 MEDIUM 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 development and testing of applications often involves copying data from production. It is important that specifi
    SV-235153r623581_rule MYS8-00-006800 CCI-001090 MEDIUM 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 processes and authorized, administrative users to have access to the files where the database resides helps ensu
    SV-235154r623584_rule MYS8-00-007000 CCI-001188 MEDIUM 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 identifiers already known. The preferred technique for thwarting guesses at Session IDs is the generation of un
    SV-235155r810831_rule MYS8-00-007200 CCI-001199 HIGH 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 system information. Information at rest refers to the state of information when it is located on a secondary
    SV-235156r623590_rule MYS8-00-007300 CCI-001310 MEDIUM 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 that data. This results in unanticipated application behavior, potentially leading to an application or i
    SV-235157r623593_rule MYS8-00-007400 CCI-001310 MEDIUM 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 the dynamic execution capabilities of various programming languages, including dialects of SQL. In such ca
    SV-235158r623596_rule MYS8-00-007500 CCI-001310 MEDIUM 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 the dynamic execution capabilities of various programming languages, including dialects of SQL. In such ca
    SV-235159r623599_rule MYS8-00-007800 CCI-001464 MEDIUM 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 auditing is in use, it needs to be in operation for the whole time the Database Management System (DBMS) i
    SV-235160r623602_rule MYS8-00-008000 CCI-001493 MEDIUM 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 application, system and application log tools may provide the only means to manipulate and manage applicatio
    SV-235161r623605_rule MYS8-00-008100 CCI-001494 MEDIUM 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 necessary to prevent unauthorized operation on audit data. Applications providing tools to interface with
    SV-235162r623608_rule MYS8-00-008200 CCI-001495 MEDIUM 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 necessary to prevent unauthorized operation on audit data. Applications providing tools to interface with
    SV-235163r623611_rule MYS8-00-008300 CCI-001499 MEDIUM 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 testing and approvals that are part of a robust change management process. Accordingly, only qualified
    SV-235164r623614_rule MYS8-00-008400 CCI-001499 MEDIUM 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 and/or application can have significant effects on the overall security of the system. If the system we
    SV-235165r623617_rule MYS8-00-008500 CCI-001499 MEDIUM 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 system and/or application can potentially have significant effects on the overall security of the system. Mu
    SV-235166r623709_rule MYS8-00-008700 CCI-001499 MEDIUM 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 appropriate testing and approvals that are part of a robust change management process. Accordingly, only qua
    SV-235167r623623_rule MYS8-00-009000 CCI-001762 MEDIUM 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.
    SV-235168r623626_rule MYS8-00-009100 CCI-001812 MEDIUM 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 installed on the system. Explicit privileges (escalated or administrative privileges) provide the regular use
    SV-235169r623629_rule MYS8-00-009200 CCI-001813 MEDIUM 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 system. When dealing with access restrictions pertaining to change control, it should be noted that any c
    SV-235170r623632_rule MYS8-00-009300 CCI-001814 MEDIUM 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 audit trail would not be available for forensic investigation for after-the-fact actions. Enforcement ac
    SV-235171r623635_rule MYS8-00-009400 CCI-001844 MEDIUM 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. The content captured in audit records must be managed from a central location (necessitating automation). Centralized management of audit records and logs provides for efficiency in maintenance and management of records, as well as the backup and archivin
    SV-235172r623638_rule MYS8-00-009500 CCI-001844 MEDIUM 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. If the configuration of the Database Management System's (DBMS's) auditing is spread across multiple locations in the database management software, or across multiple commands, only loosely related, it is harder to use and takes longer to reconfigure in r
    SV-235173r623641_rule MYS8-00-009600 CCI-001849 MEDIUM 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. Although another requirement (SRG-APP-000515-DB-000318) mandates that audit data be off-loaded to a cen
    SV-235174r623644_rule MYS8-00-009700 CCI-001851 MEDIUM 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 systems with limited audit storage capacity. The DBMS may write audit records to database tables, to fil
    SV-235175r623647_rule MYS8-00-009800 CCI-001855 MEDIUM 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 server will not be an issue. However, space will still be required on the Database Management System's (DBMS)
    SV-235176r623650_rule MYS8-00-009900 CCI-001858 MEDIUM 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 alert, security personnel may be unaware of an impending failure of the audit capability, and system operatio
    SV-235177r623653_rule MYS8-00-010300 CCI-002007 MEDIUM 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.
    SV-235178r623656_rule MYS8-00-010400 CCI-002038 MEDIUM 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, current, DoD-issued Public Key Infrastructure (PKI) certificate, coupled with a Personal Identification N
    SV-235179r623659_rule MYS8-00-010500 CCI-002165 MEDIUM 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 be authorized to access the object and in which mode (e.g., read or write). Ownership is usually acquired
    SV-235180r623662_rule MYS8-00-010600 CCI-002233 MEDIUM 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, functions, triggers, etc.) and/or external code modules with elevated privileges. However, if the privileges
    SV-235181r623665_rule MYS8-00-010700 CCI-002235 MEDIUM 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 access to information or privileges. System documentation should include a definition of the functiona
    SV-235182r623668_rule MYS8-00-010800 CCI-002262 MEDIUM 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 labels are abstractions representing the basic properties or characteristics of an entity (e.g., subject
    SV-235183r623671_rule MYS8-00-010900 CCI-002263 MEDIUM 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-control decisions. Security labels are abstractions representing the basic properties or characteristic
    SV-235184r623674_rule MYS8-00-011000 CCI-002264 MEDIUM 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 labels are abstractions representing the basic properties or characteristics of an entity (e.g., subject
    SV-235185r623677_rule MYS8-00-011100 CCI-002361 MEDIUM 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 sessions (i.e., network disconnect). A logical session (for local, network, and remote access) is initia
    SV-235186r623680_rule MYS8-00-011300 CCI-002420 MEDIUM 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 aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures
    SV-235187r810842_rule MYS8-00-011500 CCI-002450 MEDIUM 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 cryptographic modules adhering to the higher standards approved by the federal government since this provides ass
    SV-235188r623686_rule MYS8-00-011600 CCI-002450 MEDIUM The MySQL Database Server 8.0 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 cryptographic modules adhering to the higher standards approved by the federal government since this provides ass
    SV-235189r623689_rule MYS8-00-011700 CCI-002450 HIGH The MySQL Database Server 8.0 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 cryptographic modules adhering to the higher standards approved by the federal government since this provides ass
    SV-235190r623692_rule MYS8-00-011800 CCI-002450 MEDIUM 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. Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides ass
    SV-235191r623695_rule MYS8-00-011900 CCI-002470 MEDIUM 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 for DoD systems to rely on the identity asserted in the certificate. PKIs lacking sufficient security co
    SV-235192r623710_rule MYS8-00-012000 CCI-002475 MEDIUM 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 disclosure and modification of the information at rest. These cryptographic mechanisms may be native to the
    SV-235193r623701_rule MYS8-00-012100 CCI-002476 MEDIUM 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 disclosure and modification of the information at rest. These cryptographic mechanisms may be native to the D
    SV-235194r623704_rule MYS8-00-012300 CCI-002605 MEDIUM 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 their products to address newly discovered security vulnerabilities. Organizations (including any contract
    SV-235195r623707_rule MYS8-00-012500 CCI-002754 MEDIUM 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 caused by invalid inputs, where information system responses to the invalid input may be disruptive or cau