Cis Docker 2.19

Ensure that experimental features are not implemented in production

cyberstrikeus ef6573e 1.3 KB Updated

File contents

Ensure that experimental features are not implemented in production (Manual)

Profile Applicability

• Level 1 - Docker - Linux

Description

Experimental features should not be enabled in production.

Rationale

"Experimental" is currently a runtime Docker daemon flag rather than being a feature of a separate build. Passing --experimental as a runtime flag to the docker daemon activates experimental features. Whilst "Experimental" is considered a stable release, it has a number of features which may not have been fully tested and do not guarantee API stability.

Impact

None

Audit Procedure

You should run the command below and ensure that the Experimental property is set to false in the Server section.

docker version --format '{{ .Server.Experimental }}'

Remediation

You should not pass --experimental as a runtime parameter to the Docker daemon on production systems.

Default Value

By default, experimental features are not activated in the Docker daemon.

References

  1. https://docs.docker.com/engine/reference/commandline/dockerd/

CIS Controls

No CIS Controls mapping provided in the benchmark for this control.

cyberstrikeus/cyberstrike/tree/main/.cyberstrike/skill/CIS_benchmarks/Server_Software/Docker/CIS_Docker_Benchmark_v1.8.0/cis-docker-2.19 commit ef6573e9a0

Frequently asked questions

npx skillmds@latest add cyberstrikeus/cis-docker-2-19