Features Added in MySQL 8.0 •MySQL now supports FIPS mode, if compiled using OpenSSL, and an OpenSSL library and FIPS Object Module are available at runtime. FIPS mode imposes conditions on cryptographic operations such as restrictions on acceptable encryption algorithms or requirements for longer key lengths. See Section 6.8, “FIPS Support” . •The TLS context the server uses for new connections now is reconfigurable at runtime. This capability may be useful, for example, to avoid restarting a MySQL server that has been running so long that its SSL certificate has expired. See Server-Side Runtime Configuration and Monitoring for Encrypted Connections. •OpenSSL 1.1.1 supports the TLS v1.3 protocol for encrypted connections, and MySQL 8.0.16 and higher supports TLS v1.3 as well, if both the server and client are compiled using OpenSSL 1.1.1 or higher. See Section 6.3.2, “Encrypted Connection TLS Protocols and Ciphers” . •MySQL now sets the access control granted to clients on the named pipe to the minimum necessary for successful communication on Windows. Newer MySQL client software can open named pipe connections without any additional configuration. If older client software cannot be upgraded immediately, the new  named_pipe_full_access_group  system variable can be used to give a Windows group the necessary permissions to open a named pipe connection. Membership in the full- access group should be restricted and temporary. • Resource management.   MySQL now supports creation and management of resource groups, and permits assigning threads running within the server to particular groups so that threads execute according to the resources available to the group. Group attributes enable control over its resources, to enable or restrict resource consumption by threads in the group. DBAs can modify these attributes as appropriate for different workloads. Currently, CPU time is a manageable resource, represented by the concept of “virtual CPU”  as a term that includes CPU cores, hyperthreads, hardware threads, and so forth. The server determines at startup how many virtual CPUs are available, and database administrators with appropriate privileges can associate these CPUs with resource groups and assign threads to groups. For more information, see Section 5.1.16, “Resource Groups” . • Table encryption management.   Table encryption can now be managed globally by defining and enforcing encryption defaults. The  default_table_encryption  variable defines an encryption default for newly created schemas and general tablespace. The encryption default for a schema can also be defined using the  DEFAULT ENCRYPTION  clause when creating a schema. By default, a table inherits the encryption of the schema or general tablespace it is created in. Encryption defaults are enforced by enabling the  table_encryption_privilege_check  variable. The privilege check occurs when creating or altering a schema or general tablespace with an encryption setting that differs from the  default_table_encryption  setting, or when creating or altering a table with an encryption setting that differs from the default schema encryption. The  TABLE_ENCRYPTION_ADMIN privilege permits overriding default encryption settings when  table_encryption_privilege_check is enabled. For more information, see Defining an Encryption Default for Schemas and General Tablespaces. 11