Cis Docker V170 4.8
DevOps & Securitycis-docker-v170-4.8Cis Docker V170 4.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 setuid and setgid permissions are removed
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-4.8/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cis-docker-v170-4-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.7.0 - Control 4.8
Profile Applicability
- Level 2 - Docker - Linux
Description
Removing setuid and setgid permissions in the images can prevent privilege escalation attacks within containers.
Rationale
setuid and setgid permissions can be used for privilege escalation. Whilst these permissions can on occasion be legitimately needed, you should consider removing them from packages which do not need them. This should be reviewed for each image.
Impact
The above command would break all executables that depend on setuid or setgid permissions including legitimate ones. You should therefore be careful to modify the command to suit your requirements so that it does not reduce the permissions of legitimate programs excessively. Because of this, you should exercise a degree of caution and examine all processes carefully before making this type of modification in order to avoid outages.
Audit Procedure
You should run the command below against each image to list the executables which have either setuid or setgid permissions:
docker export <IMAGE_ID> | tar -tv 2>/dev/null | grep -E '^[^ rwx]*[rwx]*[s|S]*[s|S]*[rwx]*'
You should then review the list and ensure that all executables configured with these permissions actually require them.
Remediation
You should allow setuid and setgid permissions only on executables which require them. You could remove these permissions at build time by adding the following command in your Dockerfile, preferably towards the end of the Dockerfile:
RUN find / -perm /6000 -type f -exec chmod a-s {} \; || true
Default Value
Not Applicable
References
- https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
- http://man7.org/linux/man-pages/man2/setuid.2.html
- http://man7.org/linux/man-pages/man2/setgid.2.html
CIS Controls
v8:
- 5.4 Restrict Administrator Privileges to Dedicated Administrator Accounts - Restrict administrator privileges to dedicated administrator accounts on enterprise assets. Conduct general computing activities, such as internet browsing, email, and productivity suite use, from the user's primary, non-privileged account.
v7:
- 4 Controlled Use of Administrative Privileges - Controlled Use of Administrative Privileges
Assessment Status
Manual