content_image/834564.jpg content_image/834579.jpg
<img src='content_image/834564.jpg'>

Whether keyring operations are enabled. This variable is used during key migration operations. See Section 6.4.4.13, “Migrating Keys Between Keyring Keystores” . The privileges required to modify this variable are ENCRYPTION_KEY_ADMIN  in addition to either SYSTEM_VARIABLES_ADMIN  or the deprecated SUPER  privilege. 

## 6.4.5 MySQL Enterprise Audit 

<img src='content_image/834579.jpg'>

## Note 

MySQL Enterprise Audit is an extension included in MySQL Enterprise Edition, a commercial product. To learn more about commercial products, see https:// www.mysql.com/products/. 

MySQL Enterprise Edition includes MySQL Enterprise Audit, implemented using a server plugin named audit_log . MySQL Enterprise Audit uses the open MySQL Audit API to enable standard, policy-based monitoring, logging, and blocking of connection and query activity executed on specific MySQL servers. Designed to meet the Oracle audit specification, MySQL Enterprise Audit provides an out of box, easy to use auditing and compliance solution for applications that are governed by both internal and external regulatory guidelines. 

When installed, the audit plugin enables MySQL Server to produce a log file containing an audit record of server activity. The log contents include when clients connect and disconnect, and what actions they perform while connected, such as which databases and tables they access. 

After you install the audit plugin (see Section 6.4.5.2, “Installing or Uninstalling MySQL Enterprise Audit” ), it writes an audit log file. By default, the file is named audit.log  in the server data directory. To change the name of the file, set the audit_log_file  system variable at server startup. 

By default, audit log file contents are written in new-style XML format, without compression or encryption. To select the file format, set the audit_log_format  system variable at server startup. For details on file format and contents, see Section 6.4.5.4, “Audit Log File Formats” . 

For more information about controlling how logging occurs, including audit log file naming and format selection, see Section 6.4.5.5, “Configuring Audit Logging Characteristics” . To perform filtering of audited events, see Section 6.4.5.7, “Audit Log Filtering” . For descriptions of the parameters used to configure the audit log plugin, see Audit Log Options and Variables. 

If the audit log plugin is enabled, the Performance Schema (see Chapter 27, MySQL Performance Schema ) has instrumentation for it. To identify the relevant instruments, use this query: 

## 6.4.5.1 Elements of MySQL Enterprise Audit 

SELECT NAME FROM performance_schema.setup_instruments WHERE NAME LIKE ’%/alog/%’; 

MySQL Enterprise Audit is based on the audit log plugin and related elements: 

•A server-side plugin named audit_log  examines auditable events and determines whether to write them to the audit log. 

