1. Home
  2. Security Hardening
  3. CIS Docker Community Edition V1.1.0 L1 Linux Host OS
  4. Ensure auditing is configured for Docker files and directories – /usr/bin/docker-runc

Ensure auditing is configured for Docker files and directories – /usr/bin/docker-runc

Details

Audit /usr/bin/docker-runc, if applicable.

Rationale:

Apart from auditing your regular Linux file system and system calls, audit all Docker related files and directories. Docker daemon runs with root privileges. Its behavior depends on some key files and directories. /usr/bin/docker-runc is one such file. Docker now relies on containerd and runC to spawn containers. It must be audited, if applicable.

Solution

Add a rule for /usr/bin/docker-runc file.
For example,
Add the line as below in /etc/audit/audit.rules file:
-w /usr/bin/docker-runc -k docker
Then, restart the audit daemon. For example,
service auditd restart
Impact:
Auditing generates quite big log files. Ensure to rotate and archive them periodically. Also, create a separate partition of audit to avoid filling root file system.
Default Value:
By default, Docker related files and directories are not audited. The file/usr/bin/docker-runc may not be available on the system. In that case, this recommendation is not applicable.

Supportive Information

The following resource is also helpful.

This security hardening control applies to the following category of controls within NIST 800-53: Audit and Accountability.This control applies to the following type of system Unix.

References

Source

Updated on July 16, 2022
Was this article helpful?

Related Articles