The MySQL Keyring •Plugin loading using  --plugin-load  or  --plugin-load-add  occurs after  InnoDB  initialization. •Plugins installed using  INSTALL PLUGIN  are registered in the  mysql.plugin  system table and loaded automatically for subsequent server restarts. However, because  mysql.plugin  is an  InnoDB  table, any plugins named in it can be loaded during startup only after  InnoDB  initialization. If no keyring component or plugin is available when a component tries to access the keyring service, the service cannot be used by that component. As a result, the component may fail to initialize or may initialize with limited functionality. For example, if  InnoDB  finds that there are encrypted tablespaces when it initializes, it attempts to access the keyring. If the keyring is unavailable,  InnoDB  can access only unencrypted tablespaces. To ensure that  InnoDB  can access encrypted tablespaces as well, use  -- early-plugin-load  to load the keyring 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  component_keyring_file  keyring component stores keyring data in a file local to the server host. 6.4.4.4 Using the component_keyring_file File-Based Keyring Component Warning To use  component_keyring_file  for keystore management, you must: 1. Write a manifest that tells the server to load  component_keyring_file , as described in Section 6.4.4.2, “Keyring Component Installation” . 2. Write a configuration file for  component_keyring_file , as described here. When it initializes,  component_keyring_file  reads either a global configuration file, or a global configuration file paired with a local configuration file: •The component attempts to read its global configuration file from the directory where the component library file is installed (that is, the server plugin directory). •If the global configuration file indicates use of a local configuration file, the component attempts to read its local configuration file from the data directory. •Although global and local configuration files are located in different directories, the file name is component_keyring_file.cnf  in both locations. •It is an error for no confguration file to exist.  component_keyring_file  cannot initialize without a valid configuration. Local configuration files permit setting up multiple server instances to use  component_keyring_file , such that component configuration for each server instance is specific to a given data directory instance. This enables the same keyring component to be used with a distinct data file for each instance. component_keyring_file  configuration files have these properties: •A configuration file must be in valid JSON format. •A configuration file permits these configuration items: 1404