Cis Docker V170 2.4
DevOps & Securitycis-docker-v170-2.4Cis Docker V170 2.4 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 Docker is allowed to make changes to iptables
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.7.0/cis-docker-v170-2.4/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cis-docker-v170-2-4, 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.7.0 - Control 2.4
Profile Applicability
- Level: 1 - Docker - Linux
Description
The iptables firewall is used to set up, maintain, and inspect the tables of IP packet filter rules within the Linux kernel. The Docker daemon should be allowed to make changes to the iptables ruleset.
Rationale
Docker will never make changes to your system iptables rules unless you allow it to do so. If you do allow this, Docker server can automatically make any required changes. We recommended letting Docker make changes to iptables automatically in order to avoid networking misconfigurations that could affect the communication between containers and with the outside world. Additionally, this reduces the administrative overhead of updating iptables every time you add containers or modify networking options.
Impact
The Docker daemon service requires iptables rules to be enabled before it starts. Any restarts of iptables during Docker daemon operation may result in losing Docker created rules. Adding iptables-persistent to your iptables install can assist with mitigation of this impact.
Audit Procedure
To confirm this setting you should review the dockerd start-up options and the settings in /etc/docker/daemon.json.
To review the dockerd startup options, use:
ps -ef | grep dockerd
Ensure that the --iptables parameter is either not present or not set to false.
The contents of /etc/docker/daemon.json should also be reviewed for this setting.
Remediation
Do not run the Docker daemon with --iptables=false parameter. For example, do not start the Docker daemon as below:
dockerd --iptables=false
Default Value
By default, iptables is set to true.
References
- https://docs.docker.com/engine/reference/commandline/dockerd/
- https://docs.docker.com/network/iptables/
CIS Controls
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 12.2 Establish and Maintain a Secure Network ArchitectureEstablish and maintain a secure network architecture. A secure network architecture must address segmentation, least privilege, and availability, at a minimum. | ● | ● | |
| v7 | 4 Controlled Use of Administrative PrivilegesControlled Use of Administrative Privileges |
Profile
Level 1 - Docker - Linux (Manual)