Cis Docker V160 1.1.11

CIS Docker Benchmark v1.6.0 - 1.1.11

Profile Applicability

• Level 2 - Docker - Linux

Description

Audit /etc/docker/daemon.json, if applicable.

Rationale

As well as auditing the normal Linux file system and system calls, you should also audit all Docker related files and directories. The Docker daemon runs with root privileges and its behavior depends on some key files and directories. /etc/docker/daemon.json is one such file. This holds various parameters for the Docker daemon, and as such it should be 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 associated with the /etc/docker/daemon.json file.

For example, you could execute the command below:

auditctl -l | grep /etc/docker/daemon.json

This should display a rule for the /etc/docker/daemon.json file.

Remediation

You should add a rule for the /etc/docker/daemon.json file.

For example: Add the line below to the /etc/audit/audit.rules file:

-w /etc/docker/daemon.json -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/docker/daemon.json may not exist 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
2. https://docs.docker.com/engine/reference/commandline/dockerd/#daemon-configuration-file

CIS Controls

Assessment Status

Automated

Additional Information

N/A