Cis Docker V160 1.1.8
DevOps & Securitycis-docker-v160-1.1.8Cis Docker V160 1.1.8 is an Agent Skill for devops & security published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Ensure auditing is configured for Docker files and directories - containerd.sock
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/CIS_benchmarks/Server_Software/Docker/CIS_Docker_Benchmark_v1.6.0/cis-docker-v160-1.1.8/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cis-docker-v160-1-1-8, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
CIS Docker Benchmark v1.6.0 - 1.1.8
Profile Applicability
- Level 2 - Docker - Linux
Description
Audit containerd.sock, 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 with containerd.sock being one such file, and as this holds various parameters for the Docker daemon, 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
Step 1: Find out the file location:
grep 'containerd.sock' /etc/containerd/config.toml
or by checking the Docker --containerd option.
Step 2: If the file does not exist, this recommendation is not applicable. If the file exists, you should verify that there is an audit rule corresponding to the file:
For example, you could execute the command below:
auditctl -l | grep containerd.sock
This should display a rule for containerd.sock.
Remediation
If the file exists, you should add a rule for it.
For example:
Add the line below to the /etc/audit/audit.rules file:
-w /run/containerd/containerd.sock -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 containerd.sock may not be present, but if it is, it should be audited.
References
- https://github.com/containerd/containerd/blob/master/docs/ops.md
- https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/system_design_guide/auditing-the-system_system-design-guide
- https://docs.docker.com/engine/reference/commandline/dockerd/#docker-runtime-execution-options
CIS Controls
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 8.5 Collect Detailed Audit LogsConfigure 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. | ● | ● | |
| v7 | 14.9 Enforce Detail Logging for Access or Changes to Sensitive DataEnforce detailed audit logging for access to sensitive data or changes to sensitive data (utilizing tools such as File Integrity Monitoring or Security Information and Event Monitoring). | ● |
Assessment Status
Automated
Additional Information
N/A