The MySQL Keyring • keyring_oci : Communicates with Oracle Cloud Infrastructure Vault for back end storage. Available in MySQL Enterprise Edition distributions as of MySQL 8.0.22. See Section 6.4.4.11, “Using the Oracle Cloud Infrastructure Vault Keyring Plugin” . •A keyring service interface for keyring key management. This service is accessible at two levels: •SQL interface: In SQL statements, call the functions described in Section 6.4.4.14, “General-Purpose Keyring Key-Management Functions” . •C interface: In C-language code, call the keyring service functions described in Section 5.6.9.2, “The Keyring Service” . •Key metadata access: •The Performance Schema  keyring_keys  table exposes metadata for keys in the keyring. Key metadata includes key IDs, key owners, and backend key IDs. The  keyring_keys  table does not expose any sensitive keyring data such as key contents. Available as of MySQL 8.0.16. See Section 27.12.18.2, “The keyring_keys table” . •The Performance Schema  keyring_component_status  table provides status information about the keyring component in use, if one is installed. Available as of MySQL 8.0.24. See Section 27.12.18.1, “The keyring_component_status Table” . •A key migration capability. MySQL supports migration of keys between keystores, enabling DBAs to switch a MySQL installation from one keystore to another. See Section 6.4.4.13, “Migrating Keys Between Keyring Keystores” . •The implementation of keyring plugins is revised as of MySQL 8.0.24 to use the component infrastructure. This is facilitated using the built-in plugin named  daemon_keyring_proxy_plugin  that acts as a bridge between the plugin and component service APIs. See Section 5.6.8, “The Keyring Proxy Bridge Plugin” . For encryption key management, the  component_keyring_file  and component_keyring_encrypted_file  components, and the  keyring_file and  keyring_encrypted_file  plugins are not intended as a regulatory compliance solution. Security standards such as PCI, FIPS, and others require use of key management systems to secure, manage, and protect encryption keys in key vaults or hardware security modules (HSMs). •The  InnoDB  storage engine uses the keyring to store its key for tablespace encryption. See Section 15.13, “InnoDB Data-at-Rest Encryption” . •MySQL Enterprise Audit uses the keyring to store the audit log file encryption password. See Encrypting Audit Log Files. •Binary log and relay log management supports keyring-based encryption of log files. With log file encryption activated, the keyring stores the keys used to encrypt passwords for the binary log files and relay log files. See Section 17.3.2, “Encrypting Binary Log Files and Relay Log Files” . For general keyring installation instructions, see Section 6.4.4.2, “Keyring Component Installation” , and Section 6.4.4.3, “Keyring Plugin Installation” . For installation and configuration information specific to a given keyring component or plugin, see the section describing it. Within MySQL, keyring service consumers include: Warning 1398