TMAegis
More rules for mysql

TMA-MYSQL-1.7

Ensure MySQL is Run Under a Sandbox Environment

LowLevel 2Manual reviewmysql

Description

Use of the chroot() system call at startup, Systemd with settings to achieve isolation, or docker will put MySQL in a Sandbox environment.

How it is checked

Audit method: Manual review

This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --include-manual.

Check whether MySQL is confined: chroot option (grep -r '^chroot' /etc/mysql /etc/my.cnf*; must differ from datadir), systemd unit runs as a non-root user (systemctl status mysqld: Main PID not owned by root), or it runs in a container (docker ps / podman ps). None of these is a fail.

How it is fixed

Fix method: Guidance or infrastructure patch

Run MySQL under systemd as the mysql user, in a container, or with chroot=<path> under [mysqld], and keep SELinux/AppArmor confinement enabled.

Properties

Operating systems
Any
Tags
mysqldatabaseosisolationmanual
Reference
CIS Oracle MySQL Community Server 8.4 Benchmark v1.1.0 - 1.7 Ensure MySQL is Run Under a Sandbox Environment