| 1.1.4 Ensure auditing is configured for Docker files and directories - /run/containerd | CIS Docker v1.6.0 L2 Docker Linux | Unix | AUDIT AND ACCOUNTABILITY |
| 1.1.16 Ensure auditing is configured for Docker files and directories - /usr/bin/containerd-shim-runc-v1 | CIS Docker v1.6.0 L2 Docker Linux | Unix | AUDIT AND ACCOUNTABILITY |
| 1.1.18 Ensure auditing is configured for Docker files and directories - /usr/bin/runc | CIS Docker v1.6.0 L2 Docker Linux | Unix | AUDIT AND ACCOUNTABILITY |
| 1.2.1 Ensure the container host has been Hardened | CIS Docker v1.6.0 L1 Docker Linux | Unix | CONFIGURATION MANAGEMENT |
| 2.1 Restrict network traffic between containers | CIS Docker 1.13.0 v1.0.0 L1 Docker | Unix | SYSTEM AND COMMUNICATIONS PROTECTION |
| 2.8 Ensure the default ulimit is configured appropriately - daemon.json nproc hard | CIS Docker v1.6.0 L1 Docker Linux | Unix | CONFIGURATION MANAGEMENT |
| 2.8 Ensure the default ulimit is configured appropriately - daemon.json nproc soft | CIS Docker v1.6.0 L1 Docker Linux | Unix | CONFIGURATION MANAGEMENT |
| 2.10 Do not change base device size until needed | CIS Docker 1.11.0 v1.0.0 L2 Docker | Unix | |
| 2.10 Do not change base device size until needed | CIS Docker 1.12.0 v1.0.0 L2 Docker | Unix | |
| 2.11 Ensure base device size is not changed until needed - dockerd | CIS Docker v1.6.0 L2 Docker Linux | Unix | CONFIGURATION MANAGEMENT |
| 2.14 Ensure containers are restricted from acquiring new privileges - daemon.json | CIS Docker v1.6.0 L1 Docker Linux | Unix | |
| 2.17 Bind swarm services to a specific host interface | CIS Docker 1.13.0 v1.0.0 L1 Docker | Unix | SYSTEM AND COMMUNICATIONS PROTECTION |
| 3.2 Verify that docker.service file permissions are set to 644 or more restrictive | CIS Docker 1.11.0 v1.0.0 L1 Docker | Unix | CONFIGURATION MANAGEMENT |
| 3.2 Verify that docker.service file permissions are set to 644 or more restrictive | CIS Docker 1.6 v1.0.0 L1 Docker | Unix | CONFIGURATION MANAGEMENT |
| 3.4 Ensure that docker.socket file permissions are set to 644 or more restrictive | CIS Docker v1.6.0 L2 Docker Linux | Unix | ACCESS CONTROL, MEDIA PROTECTION |
| 3.4 Ensure that docker.socket file permissions are set to 644 or more restrictive | CIS Docker v1.6.0 L1 Docker Linux | Unix | ACCESS CONTROL, MEDIA PROTECTION |
| 3.10 Verify that TLS CA certificate file permissions are set to 444 or more restrictive | CIS Docker 1.11.0 v1.0.0 L1 Docker | Unix | CONFIGURATION MANAGEMENT |
| 3.24 Ensure that the Containerd socket file permissions are set to 660 or more restrictively | CIS Docker v1.6.0 L1 Docker Linux | Unix | ACCESS CONTROL, MEDIA PROTECTION |
| 4.3 Do not install unnecessary packages in the container | CIS Docker 1.13.0 v1.0.0 L1 Docker | Unix | CONFIGURATION MANAGEMENT |
| 4.4 Rebuild the images to include security patches | CIS Docker 1.11.0 v1.0.0 L1 Docker | Unix | CONFIGURATION MANAGEMENT |
| 4.5 Ensure Content trust for Docker is Enabled | CIS Docker v1.6.0 L2 Docker Linux | Unix | SYSTEM AND COMMUNICATIONS PROTECTION |
| 4.11 Ensure only verified packages are installed | CIS Docker v1.6.0 L2 Docker Linux | Unix | SYSTEM AND SERVICES ACQUISITION |
| 4.11 Install verified packages only | CIS Docker 1.13.0 v1.0.0 L2 Docker | Unix | CONFIGURATION MANAGEMENT |
| 5.4 Do not use privileged containers | CIS Docker 1.12.0 v1.0.0 L1 Docker | Unix | ACCESS CONTROL |
| 5.6 Do not mount sensitive host system directories on containers | CIS Docker 1.6 v1.0.0 L1 Docker | Unix | CONFIGURATION MANAGEMENT |
| 5.7 Do not run ssh within containers | CIS Docker 1.6 v1.0.0 L1 Docker | Unix | CONFIGURATION MANAGEMENT |
| 5.10 Limit memory usage for container | CIS Docker 1.12.0 v1.0.0 L1 Docker | Unix | SYSTEM AND COMMUNICATIONS PROTECTION |
| 5.11 Set container CPU priority appropriately | CIS Docker 1.11.0 v1.0.0 L1 Docker | Unix | SYSTEM AND COMMUNICATIONS PROTECTION |
| 5.12 Set container CPU priority appropriately | CIS Docker 1.6 v1.0.0 L1 Docker | Unix | SYSTEM AND COMMUNICATIONS PROTECTION |
| 5.14 Ensure that incoming container traffic is bound to a specific host interface | CIS Docker v1.6.0 L1 Docker Linux | Unix | SECURITY ASSESSMENT AND AUTHORIZATION, SYSTEM AND COMMUNICATIONS PROTECTION |
| 5.14 Set the 'on-failure' container restart policy to 5 - RestartPolicyName=always | CIS Docker 1.12.0 v1.0.0 L1 Docker | Unix | SYSTEM AND COMMUNICATIONS PROTECTION |
| 5.14 Set the 'on-failure' container restart policy to 5 - RestartPolicyName=on-failure | CIS Docker 1.11.0 v1.0.0 L1 Docker | Unix | SYSTEM AND COMMUNICATIONS PROTECTION |
| 5.15 Set the 'on-failure' container restart policy to 5 - RestartPolicyName=on-failure | CIS Docker 1.6 v1.0.0 L1 Docker | Unix | SYSTEM AND COMMUNICATIONS PROTECTION |
| 5.17 Do not directly expose host devices to containers | CIS Docker 1.11.0 v1.0.0 L1 Docker | Unix | SYSTEM AND COMMUNICATIONS PROTECTION |
| 5.20 Ensure mount propagation mode is not set to shared | CIS Docker v1.6.0 L1 Docker Linux | Unix | SYSTEM AND COMMUNICATIONS PROTECTION |
| 5.25 Restrict container from acquiring additional privileges | CIS Docker 1.11.0 v1.0.0 L1 Docker | Unix | SYSTEM AND COMMUNICATIONS PROTECTION |
| 5.25 Restrict container from acquiring additional privileges | CIS Docker 1.13.0 v1.0.0 L1 Docker | Unix | SYSTEM AND COMMUNICATIONS PROTECTION |
| 5.26 Ensure that the container is restricted from acquiring additional privileges | CIS Docker v1.6.0 L1 Docker Linux | Unix | ACCESS CONTROL |
| 5.27 Ensure that container health is checked at runtime | CIS Docker v1.6.0 L1 Docker Linux | Unix | SYSTEM AND INFORMATION INTEGRITY |
| 5.31 Ensure that the host's user namespaces are not shared | CIS Docker v1.6.0 L1 Docker Linux | Unix | SYSTEM AND COMMUNICATIONS PROTECTION |
| 6.1 Ensure that image sprawl is avoided | CIS Docker v1.6.0 L1 Docker Linux | Unix | PLANNING, SYSTEM AND SERVICES ACQUISITION |
| 6.2 Monitor Docker containers usage, performance and metering | CIS Docker 1.12.0 v1.0.0 L1 Docker | Unix | |
| 7.1 Ensure that the minimum number of manager nodes have been created in a swarm | CIS Docker v1.6.0 L1 Docker Swarm | Unix | CONFIGURATION MANAGEMENT |
| 7.5 Ensure that swarm manager is run in auto-lock mode | CIS Docker v1.6.0 L1 Docker Swarm | Unix | IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION |
| Check if this is a Docker Vessel/Host | CIS Docker 1.13.0 v1.0.0 L2 Docker | Unix | |
| CIS_Docker_1.11.0_v1.0.0_L1.audit Level 1 | CIS Docker 1.11.0 v1.0.0 L1 Docker | Unix | |
| DKER-EE-002060 - The Docker Enterprise hosts UTS namespace must not be shared. | DISA STIG Docker Enterprise 2.x Linux/Unix v2r2 | Unix | CONFIGURATION MANAGEMENT |
| DKER-EE-002120 - The Docker Enterprise hosts user namespace must not be shared. | DISA STIG Docker Enterprise 2.x Linux/Unix v2r2 | Unix | CONFIGURATION MANAGEMENT |
| DKER-EE-002780 - PIDs cgroup limits must be used in Docker Enterprise. | DISA STIG Docker Enterprise 2.x Linux/Unix v2r2 | Unix | SYSTEM AND COMMUNICATIONS PROTECTION |
| DKER-EE-003330 - Log aggregation/SIEM systems must be configured to alarm when audit storage space for Docker Engine - Enterprise nodes exceed 75% usage. | DISA STIG Docker Enterprise 2.x Linux/Unix v2r2 | Unix | AUDIT AND ACCOUNTABILITY |
