Cis Docker V170 1.1.12

CIS Docker Benchmark v1.7.0 - Control 1.1.12

Profile

• Level: 2 - Docker - Linux
• Assessment Status: Automated

Description

Audit /etc/containerd/config.toml if applicable

Rationale

As well as auditing the normal Linux file system and system calls, you should also audit the Docker daemon. Because this daemon runs with root privileges it is very important to audit its activities and usage. Its behavior depends on some key files and directories and /etc/containerd/config.toml is one such file as it contains various parameters. If present, it is important that it is audited.

Impact

Auditing can generate large log files. You should ensure that these are rotated and archived periodically. A separate partition should also be created for audit logs to avoid filling up any other critical partition.

Audit Procedure

You should verify that there is an audit rule present relating to the /etc/containerd/config.toml file. For example, you could execute the command below:

auditctl -l | grep /etc/containerd/config.toml

This should display a rule for /etc/containerd/config.toml file.

Remediation

You should add a rule for /etc/containerd/config.toml file. For example: Add the line below to the /etc/audit/audit.rules file:

-w /etc/containerd/config.toml -k docker

Then restart the audit daemon. For example:

systemctl restart auditd

Default Value

By default, Docker related files and directories are not audited. The file /etc/containerd/config.toml may not be present on the system and in that case, this recommendation is not applicable.

References

1. https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/system_design_guide/auditing-the-system_system-design-guide

CIS Controls