# Cis Docker 4.8

> Ensure setuid and setgid permissions are removed

- Skill: `cyberstrikeus/cis-docker-4-8` (Agent Skill)
- Install (CLI): `npx skillmds@latest add cyberstrikeus/cis-docker-4-8`
- Raw SKILL.md: https://api.skillmd.com/api/skills/cyberstrikeus/cis-docker-4-8/raw
- Safety review: PASS (external: skill-scanner WARNING, 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-4-8

---


# 4.8 Ensure setuid and setgid permissions are removed (Manual)

## 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:

```bash
docker export <IMAGE_ID> | tar -tv 2>/dev/null | grep -E '^[-rwx]*.*(s|S).*\s[0-9]'
```

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:

```dockerfile
RUN find / -perm /6000 -type f -exec chmod a-s {} \; || true
```

## Default Value

Not Applicable

## References

1. https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
2. http://man7.org/linux/man-pages/man2/setuid.2.html
3. 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