# Cis Docker V160 1.1.4

> Ensure auditing is configured for Docker files and directories - /run/containerd

- Skill: `cyberstrikeus/cis-docker-v160-1-1-4` (Agent Skill)
- Install (CLI): `npx skillmds@latest add cyberstrikeus/cis-docker-v160-1-1-4`
- Raw SKILL.md: https://api.skillmd.com/api/skills/cyberstrikeus/cis-docker-v160-1-1-4/raw
- Safety review: PASS (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: cyberstrikeus (https://skillmd.com/u/cyberstrikeus)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/cyberstrikeus/cis-docker-v160-1-1-4

---


# CIS Docker Benchmark v1.6.0 - 1.1.4

## Profile Applicability

- Level 1 - Docker - Linux
- Level 2 - Docker - Linux

## Description

Audit `/run/containerd`.

## 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 behaviour depends on some key files and directories. `/run/containerd` is one such directory. As it holds all the information about containers 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 applied to the `/run/containerd` directory. For example, you could execute the command below:

```bash
auditctl -l | grep /run/containerd
```

This should list a rule for the `/run/containerd` directory.

## Remediation

You should add a rule for the `/run/containerd` directory.

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

```bash
-a exit,always -F path=/run/containerd -F perm=war -k docker
```

Then, restart the audit daemon using the following command

```bash
systemctl restart auditd
```

## Default Value

By default, Docker related files and directories are not audited.

## References

1. https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/system_design_guide/auditing-the-system_system-design-guide

## CIS Controls

| Controls Version | Control                                                                                                                                                                                                                                                                                 | IG 1 | IG 2 | IG 3 |
| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---- | ---- | ---- |
| v8               | 8.5 Collect Detailed Audit Logs<br>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. |      | ●    | ●    |
| v7               | 14.9 Enforce Detail Logging for Access or Changes to Sensitive Data<br>Enforce 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