cis-docker-v160-1-1-14

name	cis-docker-v160-1.1.14
description	Ensure auditing is configured for Docker files and directories - /usr/bin/containerd
category	cis-docker
version	1.6.0
author	cyberstrike-official
tags	["cis","docker","host-configuration","auditing","logging","containerd","binary","linux"]
cis_id	1.1.14
cis_benchmark	CIS Docker Benchmark v1.6.0
tech_stack	["docker","linux","auditd","containerd"]
cwe_ids	[]
chains_with	[]
prerequisites	[]
severity_boost	{}

CIS Docker Benchmark v1.6.0 - 1.1.14

Profile Applicability

• Level 2 - Docker - Linux

Description

Audit /usr/bin/containerd if applicable.

Rationale

As well as auditing the normal Linux file system and system calls, you should audit all Docker related files and directories. The Docker daemon runs with root privileges and its behavior depends on some key files and directories. /usr/bin/containerd is one such file and as such 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 corresponding to /usr/bin/containerd file.

For example, you could execute the command below:

auditctl -l | grep /usr/bin/containerd

This should display a rule for /usr/bin/containerd file.

Remediation

You should add a rule for the /usr/bin/containerd file.

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

-w /usr/bin/containerd -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 /usr/bin/containerd 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
2. https://containerd.io/

CIS Controls

Controls Version	Control	IG 1	IG 2	IG 3
v8	8.5 Collect Detailed Audit Logs Configure detailed audit logging for enterprise assets containing sensitive data. Include event source, date, username, timestamp, source addresses, destination addresses, and other useful elements that could assist in a forensic investigation.