Details
Audit docker.socket,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. docker.socketis one such file. It holds various parameters for Docker daemon socket. It must be audited, if applicable.
Solution
If the file exists, add a rule for it.
For example,
Add the line as below in /etc/audit/audit.rules file:
-w /usr/lib/systemd/system/docker.socket -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 arenot audited.The file docker.socket may not be available on the system.
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.