cis-docker-v160-2-9

name	cis-docker-v160-2.9
description	Enable user namespace support
category	cis-docker
version	1.6.0
author	cyberstrike-official
tags	["cis","docker","daemon","user-namespace","privilege-isolation","security"]
cis_id	2.9
cis_benchmark	CIS Docker Benchmark v1.6.0
tech_stack	["docker"]
cwe_ids	[]
chains_with	[]
prerequisites	[]
severity_boost	{}

Enable user namespace support

Profile Applicability: Level 2 - Docker - Linux

Assessment Status: Manual

Description

You should enable user namespace support in Docker daemon to utilize container user to host user re-mapping. This recommendation is beneficial where the containers you are using do not have an explicit container user defined in the container image. If the container images that you are using have a pre-defined non-root user, this recommendation may be skipped as this feature is still in its infancy, and might result in unpredictable issues or difficulty in configuration.

Rationale

The Linux kernel "user namespace" support within the Docker daemon provides additional security for the Docker host system. It allows a container to have a unique range of user and group IDs which are outside the traditional user and group range utilized by the host system.

For example, the root user can have the expected administrative privileges inside the container but can effectively be mapped to an unprivileged UID on the host system.

Impact

User namespace remapping is incompatible with a number of Docker features and also currently breaks some of its functionalities. Reference the Docker documentation and included links for details.

Audit Procedure

docker inspect --format='{{ .State.Pid }}' $(docker ps -q) | while read -r line; do ps -h -p "$line" -o pid,user; done

The above command will find the PID of the container and then list the host user associated with the container process. If the container process is running as root, then this configuration may be non-compliant with your organization's security policy. Alternatively, you can run docker info to ensure that the userns is listed under Security Options:

docker info --format '{{ .SecurityOptions }}'

Remediation

Please consult the Docker documentation for various ways in which this can be configured depending upon your requirements. Your steps might also vary based on platform - For example, on Red Hat, sub-UIDs and sub-GIDs mapping creation do not work automatically. You might have to create your own mapping.

The high-level steps are as below: Step 1: Ensure that the files /etc/subuid and /etc/subgid exist.