Cis Docker 2.13
DevOps & Securitycis-docker-2.13Cis Docker 2.13 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 that authorization for Docker client commands is enabled
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.8.0/cis-docker-2.13/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cis-docker-2-13, 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.
Ensure that authorization for Docker client commands is enabled (Manual)
Profile Applicability
• Level 2 - Docker - Linux
Description
You should use native Docker authorization plugins or a third party authorization mechanism with the Docker daemon to manage access to Docker client commands.
Rationale
Docker's out-of-the-box authorization model is currently "all or nothing". This means that any user with permission to access the Docker daemon can run any Docker client command. The same is true for remote users accessing Docker's API to contact the daemon. If you require greater access control, you can create authorization plugins and add them to your Docker daemon configuration. Using an authorization plugin, a Docker administrator can configure granular access policies for managing access to the Docker daemon.
Third party integrations of Docker may implement their own authorization models to require authorization with the Docker daemon outside of docker's native authorization plugin (i.e. Kubernetes, Cloud Foundry, Openshift).
Impact
Each Docker command needs to pass through the authorization plugin mechanism. This may have a performance impact.
It may be possible to use alternative mechanisms that do not have this performance hit.
Audit Procedure
To confirm this setting the dockerd start-up options and any settings in /etc/docker/daemon.json should be reviewed.
To review the dockerd startup options, use:
ps -ef | grep dockerd
You should ensure that the --authorization-plugin parameter is set as appropriate if you are using docker native authorization.
The contents of /etc/docker/daemon.json should also be reviewed.
Remediation
Step 1: Install/Create an authorization plugin.
Step 2: Configure the authorization policy as desired.
Step 3: Start the docker daemon as below:
dockerd --authorization-plugin=<PLUGIN_ID>
Default Value
By default, authorization plugins are not set up.
References
- https://docs.docker.com/engine/reference/commandline/dockerd/#access-authorization
- https://docs.docker.com/engine/extend/plugins_authorization/
Additional Information
It should be noted that the native Docker authentication plugin is only one method of enforcing this control so other methods which could potentially be in use should be reviewed before assessing this as a pass or fail in an audit.
CIS Controls
Controls Version: v8
Control: 6 Access Control Management
Use processes and tools to create, assign, manage, and revoke access credentials and privileges for user, administrator, and service accounts for enterprise assets and software.
IG 1: IG 2: IG 3:
Controls Version: v7
Control: 16 Account Monitoring and Control
Account Monitoring and Control