STIGQter: STIG Summary: Oracle MySQL 8.0 Security Technical Implementation Guide Version: 1 Release: 1 Benchmark Date: 28 Jan 2021:

MySQL Database Server 8.0 must produce audit records containing sufficient information to establish what type of events occurred.

DISA Rule

SV-235097r638812_rule

Vulnerability Number

V-235097

Group Title

SRG-APP-000095-DB-000039

Rule Version

MYS8-00-000300

Severity

CAT II

CCI(s)

• CCI-000130 - The information system generates audit records containing information that establishes what type of event occurred.

Weight

10

Fix Recommendation

Configure DBMS auditing to audit standard and organization-defined auditable events, with the audit record to include what type of event occurred.

Use this process to ensure auditable events are captured:

Configure MySQL database server 8.0 for auditing and configure audit settings to include required events as part of the audit record.

To install MySQL Enterprise Audit:
Run the audit_log_filter_linux_install.sql script located in the sharedirectory of your MySQL installation. This can be determined by running – select @@basedir;
For example if the basedir is /usr/local/mysql
shell> bin/mysql -u root -p < /usr/local/mysql/share/audit_log_filter_linux_install.sql

Verify the plugin installation by running:
SELECT PLUGIN_NAME, PLUGIN_STATUS
FROM INFORMATION_SCHEMA.PLUGINS
WHERE PLUGIN_NAME LIKE 'audit%';
The value for audit_log should return ACTIVE.

To prevent the plugin from being removed at runtime, add the --audit-log option under the [mysqld] option group in the MySQL configuration file (/etc/my.cnf) with a setting of FORCE_PLUS_PERMANENT.

audit-log=FORCE_PLUS_PERMANENT

Restart the server to apply the configuration change.

By default, rule-based audit log filtering logs no auditable events for any users. To produce log-everything behavior with rule-based filtering, create a filter to enable logging of all events and assign it to the audit all accounts.

Run the following statements to filter all activity for all users:
SELECT audit_log_filter_set_filter('log_all', '{ "filter": { "log": true } }');
SELECT audit_log_filter_set_user('%', 'log_all');
SELECT audit_log_filter_set_user('%', 'log_all');

Check Contents

Verify, using vendor and system documentation if necessary, that the Database Management System (DBMS) is configured to use MySQL auditing features, or that a third-party product or custom code is deployed and configured to satisfy this requirement.

Check MySQL auditing to determine whether organization-defined auditable events are being audited by the system.

SELECT PLUGIN_NAME, plugin_status FROM INFORMATION_SCHEMA.PLUGINS
WHERE PLUGIN_NAME LIKE 'audit_log' ;

If the results are not 'audit_log' and plugin_status='ACTIVE' , this is a finding.

Next, determine if the audit log is encrypted:
SELECT VARIABLE_NAME, VARIABLE_VALUE
FROM performance_schema.global_variables
WHERE VARIABLE_NAME LIKE 'audit_log_encryption' ;

If nothing is returned or the value for audit_log_encryption is not AES, this is a finding.

Review the audit files in the file systems.

Run the following command using the audit log location from above and review its output:
ls -l <directory where audit log files are located>/audit*log*

For example, if the values returned by - "select @@datadir, @@audit_log_file; " are /usr/local/mysql/data/, audit.log
ls -l /usr/local/mysql/data/audit.log
Example output:
-rw-r----- 1 _mysql _mysql 3935888 Apr 25 12:34 audit.20190425T173437.log.enc
-rw-r----- 1 _mysql _mysql 2336 Apr 25 12:35 audit.20190425T173527.log.enc
-rw-r----- 1 _mysql _mysql 13763984 Apr 30 14:04 audit.log.enc

Next, verify the log files have set permissions the log_destination:
If the user owner is not "mysql", this is a finding.
If the group owner is not "mysql", this is a finding.
If the file is more permissive than "640", this is a finding.
Check that the files end with the ".enc" file extension. If they do not, this means they are in plaintext, and this is a finding.

Run following command to verify the directory permissions and review its output:
ls -l /usr/local/mysql/data

Example output:
drwxr-x--- _mysql _mysql 1760 Apr 26 09:55 data

Next, verify the log files have set permissions for the log_destination:
If the user owner is not "mysql", this is a finding.
If the group owner is not "mysql", this is a finding.
If more permissive than "750", this is a finding.

If there are no audit log files, then organizational auditable events are not being audited, and this is a finding.

To confirm that MySQL audit is capturing sufficient information to establish the identity of the user/subject or process, perform a successful auditable action and an auditable action that results in an SQL error, and then view the results in the audit file, whichever is in use.

If no audit event is returned for the auditable actions just performed, this is a finding.

Vulnerability Number

V-235097

Documentable

False

Rule Version

MYS8-00-000300

Severity Override Guidance

Verify, using vendor and system documentation if necessary, that the Database Management System (DBMS) is configured to use MySQL auditing features, or that a third-party product or custom code is deployed and configured to satisfy this requirement.

Check MySQL auditing to determine whether organization-defined auditable events are being audited by the system.

SELECT PLUGIN_NAME, plugin_status FROM INFORMATION_SCHEMA.PLUGINS
WHERE PLUGIN_NAME LIKE 'audit_log' ;

If the results are not 'audit_log' and plugin_status='ACTIVE' , this is a finding.

Next, determine if the audit log is encrypted:
SELECT VARIABLE_NAME, VARIABLE_VALUE
FROM performance_schema.global_variables
WHERE VARIABLE_NAME LIKE 'audit_log_encryption' ;

If nothing is returned or the value for audit_log_encryption is not AES, this is a finding.

Review the audit files in the file systems.

Run the following command using the audit log location from above and review its output:
ls -l <directory where audit log files are located>/audit*log*

For example, if the values returned by - "select @@datadir, @@audit_log_file; " are /usr/local/mysql/data/, audit.log
ls -l /usr/local/mysql/data/audit.log
Example output:
-rw-r----- 1 _mysql _mysql 3935888 Apr 25 12:34 audit.20190425T173437.log.enc
-rw-r----- 1 _mysql _mysql 2336 Apr 25 12:35 audit.20190425T173527.log.enc
-rw-r----- 1 _mysql _mysql 13763984 Apr 30 14:04 audit.log.enc

Next, verify the log files have set permissions the log_destination:
If the user owner is not "mysql", this is a finding.
If the group owner is not "mysql", this is a finding.
If the file is more permissive than "640", this is a finding.
Check that the files end with the ".enc" file extension. If they do not, this means they are in plaintext, and this is a finding.

Run following command to verify the directory permissions and review its output:
ls -l /usr/local/mysql/data

Example output:
drwxr-x--- _mysql _mysql 1760 Apr 26 09:55 data

Next, verify the log files have set permissions for the log_destination:
If the user owner is not "mysql", this is a finding.
If the group owner is not "mysql", this is a finding.
If more permissive than "750", this is a finding.

If there are no audit log files, then organizational auditable events are not being audited, and this is a finding.

To confirm that MySQL audit is capturing sufficient information to establish the identity of the user/subject or process, perform a successful auditable action and an auditable action that results in an SQL error, and then view the results in the audit file, whichever is in use.

If no audit event is returned for the auditable actions just performed, this is a finding.

Check Content Reference

M

Target Key

5277

Comments