How do I install the Cis Docker 1.1.12 skill?

Run npx skillmds@latest add cyberstrikeus/cis-docker-1-1-12 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Cis Docker 1.1.12 safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cis Docker 1.1.12?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cis Docker 1.1.12 free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cis Docker 1.1.12?

cyberstrikeus (@cyberstrikeus) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cis Docker 1.1.12 by cyberstrikeus — Agent Skill

Name: Cis Docker 1.1.12
Author: cyberstrikeus

File contents

Ensure auditing is configured for Docker files and directories - /etc/containerd/config.toml (Automated)

Description

Audit /etc/containerd/config.toml 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 and /etc/containerd/config.toml is one such file as it contains various parameters. If present, it is important that it is 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

You should verify that there is an audit rule present relating to the /etc/containerd/config.toml file.

For example, you could execute the command below:

auditctl -l | grep /etc/containerd/config.toml

This should display a rule for /etc/containerd/config.toml file.

Remediation

You should add a rule for /etc/containerd/config.toml file.

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

-w /etc/containerd/config.toml -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 /etc/containerd/config.toml may not be present on the system and in that case, this recommendation is not applicable.

References

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 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 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). | | | ●

Profile

• Level 2 - Docker - Linux

---name: cis-docker-1-1-12description: Ensure auditing is configured for Docker files and directories - /etc/containerd/config.toml---# Ensure auditing is configured for Docker files and directories - /etc/containerd/config.toml (Automated)## DescriptionAudit `/etc/containerd/config.toml` if applicable## RationaleAs 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 and `/etc/containerd/config.toml` is one such file as it contains various parameters. If present, it is important that it is audited.## ImpactAuditing 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.## AuditYou should verify that there is an audit rule present relating to the `/etc/containerd/config.toml` file.For example, you could execute the command below:```bashauditctl -l | grep /etc/containerd/config.toml```This should display a rule for `/etc/containerd/config.toml` file.## RemediationYou should add a rule for `/etc/containerd/config.toml` file.For example:Add the line below to the `/etc/audit/audit.rules` file:```bash-w /etc/containerd/config.toml -k docker```Then restart the audit daemon.For example:```bashsystemctl restart auditd```## Default ValueBy default, Docker related files and directories are not audited. The file `/etc/containerd/config.toml` may not be present on the system and in that case, this recommendation is not applicable.## References1. 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 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). | | | ●## Profile• Level 2 - Docker - Linux

Frequently asked questions

Cis Docker 1.1.12