| V-235861 | High | Docker Enterprise server certificate file ownership must be set to root:root. | Verify that the Docker server certificate file (the file that is passed along with --TLScert parameter) is owned and group-owned by root.
The Docker server certificate file should be protected... |
| V-235867 | High | Docker Enterprise daemon.json file ownership must be set to root:root. | Verify that the daemon.json file ownership and group-ownership is correctly set to root.
daemon.json file contains sensitive parameters that may alter the behavior of docker daemon. Hence, it... |
| V-235866 | High | Docker Enterprise socket file permissions must be set to 660 or more restrictive. | Verify that the Docker socket file has permissions of 660 or more restrictive.
Only root and members of docker group should be allowed to read and write to default Docker UNIX socket. Hence, the... |
| V-235865 | High | Docker Enterprise socket file ownership must be set to root:docker. | Verify that the Docker socket file is owned by root and group-owned by docker.
Docker daemon runs as root. The default UNIX socket hence must be owned by root. If any other user or process owns... |
| V-235864 | High | Docker Enterprise server certificate key file permissions must be set to 400. | Verify that the Docker server certificate key file (the file that is passed along with --TLSkey parameter) has permissions of 400.
The Docker server certificate key file should be protected from... |
| V-235869 | High | Docker Enterprise /etc/default/docker file ownership must be set to root:root. | Verify that the /etc/default/docker file ownership and group-ownership is correctly set to root.
/etc/default/docker file contains sensitive parameters that may alter the behavior of docker... |
| V-235868 | High | Docker Enterprise daemon.json file permissions must be set to 644 or more restrictive. | Verify that the daemon.json file permissions are correctly set to 644 or more restrictive.
daemon.json file contains sensitive parameters that may alter the behavior of docker daemon. Hence, it... |
| V-235857 | High | Docker Enterprise registry certificate file ownership must be set to root:root. | Verify that all the registry certificate files (usually found under /etc/docker/certs.d/<registry-name> directory) are owned and group-owned by root.
/etc/docker/certs.d/<registry-name> directory... |
| V-235855 | High | Docker Enterprise /etc/docker directory ownership must be set to root:root. | Verify that the /etc/docker directory ownership and group-ownership is correctly set to root.
/etc/docker directory contains certificates and keys in addition to various sensitive files. Hence,... |
| V-235853 | High | Docker Enterprise docker.socket file ownership must be set to root:root. | Verify that the docker.socket file ownership and group ownership is correctly set to root.
docker.socket file contains sensitive parameters that may alter the behavior of Docker remote API.... |
| V-235851 | High | Docker Enterprise docker.service file ownership must be set to root:root. | Verify that the docker.service file ownership and group-ownership are correctly set to root.
docker.service file contains sensitive parameters that may alter the behavior of Docker daemon. Hence,... |
| V-235859 | High | Docker Enterprise TLS certificate authority (CA) certificate file ownership must be set to root:root. | Verify that the TLS CA certificate file (the file that is passed along with --TLScacert parameter) is owned and group-owned by root.
The TLS CA certificate file should be protected from any... |
| V-235812 | High | The Docker Enterprise default seccomp profile must not be disabled. | Seccomp filtering provides a means for a process to specify a filter for incoming system calls. The default Docker seccomp profile works on whitelist basis and allows 311 system calls blocking all... |
| V-235813 | High | Docker Enterprise exec commands must not be used with privileged option. | Do not use docker exec with --privileged option.
Using --privileged option in docker exec gives extended Linux capabilities to the command. Do not run docker exec with the --privileged option,... |
| V-235816 | High | All Docker Enterprise containers must be restricted from acquiring additional privileges. | Restrict the container from acquiring additional privileges via suid or sgid bits.
A process can set the no_new_priv bit in the kernel. It persists across fork, clone, and execve. The no_new_priv... |
| V-235817 | High | The Docker Enterprise hosts user namespace must not be shared. | Do not share the host's user namespaces with the containers.
User namespaces ensure that a root process inside the container will be mapped to a non-root process outside the container. Sharing... |
| V-235818 | High | The Docker Enterprise socket must not be mounted inside any containers. | The docker socket docker.sock (Linux) and \\.\pipe\docker_engine (Windows) should not be mounted inside a container, with the exception case being during the installation of Universal Control... |
| V-235819 | High | Docker Enterprise privileged ports must not be mapped within containers. | The TCP/IP port numbers below 1024 are considered privileged ports. Normal users and processes are not allowed to use them for various security reasons. Docker allows a container port to be mapped... |
| V-235805 | High | Docker Enterprise hosts network namespace must not be shared. | The networking mode on a container when set to --net=host, skips placing the container inside separate network stack. In essence, this choice tells Docker to not containerize the container's... |
| V-235777 | High | FIPS mode must be enabled on all Docker Engine - Enterprise nodes. | When FIPS mode is enabled on a Docker Engine - Enterprise node, it uses FIPS-validated cryptography to protect the confidentiality of remote access sessions to any bound TCP sockets with TLS... |
| V-235809 | High | Docker Enterprise host devices must not be directly exposed to containers. | Host devices can be directly exposed to containers at runtime. Do not directly expose host devices to containers especially for containers that are not trusted.
The --device option exposes the... |
| V-235808 | High | All Docker Enterprise containers root filesystem must be mounted as read only. | The container's root filesystem should be treated as a 'golden image' by using Docker run's --read-only option. This prevents any writes to the container's root filesystem at container runtime and... |
| V-235870 | High | Docker Enterprise /etc/default/docker file permissions must be set to 644 or more restrictive. | Verify that the /etc/default/docker file permissions are correctly set to 644 or more restrictive.
/etc/default/docker file contains sensitive parameters that may alter the behavior of docker... |
| V-235863 | Medium | Docker Enterprise server certificate key file ownership must be set to root:root. | Verify that the Docker server certificate key file (the file that is passed along with --TLSkey parameter) is owned and group-owned by root.
The Docker server certificate key file should be... |
| V-235862 | Medium | Docker Enterprise server certificate file permissions must be set to 444 or more restrictive. | Verify that the Docker server certificate file (the file that is passed along with --TLScert parameter) has permissions of 444 or more restrictive.
The Docker server certificate file should be... |
| V-235860 | Medium | Docker Enterprise TLS certificate authority (CA) certificate file permissions must be set to 444 or more restrictive. | Verify that the TLS CA certificate file (the file that is passed along with --TLScacert parameter) has permissions of 444 or more restrictive.
The TLS CA certificate file should be protected from... |
| V-235856 | Medium | Docker Enterprise /etc/docker directory permissions must be set to 755 or more restrictive. | Verify that the /etc/docker directory permissions are correctly set to 755 or more restrictive.
/etc/docker directory contains certificates and keys in addition to various sensitive files. Hence,... |
| V-235854 | Medium | Docker Enterprise docker.socket file permissions must be set to 644 or more restrictive. | Verify that the docker.socket file permissions are correctly set to 644 or more restrictive.
docker.socket file contains sensitive parameters that may alter the behavior of Docker remote API.... |
| V-235852 | Medium | Docker Enterprise docker.service file permissions must be set to 644 or more restrictive. | Verify that the docker.service file permissions are correctly set to 644 or more restrictive.
docker.service file contains sensitive parameters that may alter the behavior of Docker daemon.... |
| V-235850 | Medium | Docker Enterprise node certificates must be rotated as defined in the System Security Plan (SSP). | Rotate swarm node certificates as appropriate.
Docker Swarm uses mutual TLS for clustering operations amongst its nodes. Certificate rotation ensures that in an event such as compromised node or... |
| V-235858 | Medium | Docker Enterprise registry certificate file permissions must be set to 444 or more restrictive. | Verify that all the registry certificate files (usually found under /etc/docker/certs.d/<registry-name> directory) have permissions of 444 or more restrictive.
/etc/docker/certs.d/<registry-name>... |
| V-235849 | Medium | Docker Enterprise Swarm manager auto-lock key must be rotated periodically. | Rotate swarm manager auto-lock key periodically.
Swarm manager auto-lock key is not automatically rotated. Rotate them periodically as a best practice.
By default, keys are not rotated automatically. |
| V-235848 | Medium | Docker Swarm must have the minimum number of manager nodes. | Ensure that the minimum number of required manager nodes is created in a swarm.
Manager nodes within a swarm have control over the swarm and change its configuration modifying security... |
| V-235841 | Medium | Universal Control Plane (UCP) must be integrated with a trusted certificate authority (CA) in Docker Enterprise. | Both the UCP and Docker Trusted Registry (DTR) components of Docker Enterprise leverage the same authentication and authorization backplane known as eNZi. The eNZi backplane includes its own... |
| V-235840 | Medium | Vulnerability scanning must be enabled for all repositories in the Docker Trusted Registry (DTR) component of Docker Enterprise. | DTR can scan Docker images for vulnerabilities and this capability should be enabled to meet the requirements of this control.
When enabled, for every Docker image that is pushed to DTR, a scan... |
| V-235843 | Medium | The on-failure container restart policy must be is set to 5 in Docker Enterprise. | Using the --restart flag in docker run command, specify a restart policy for how a container should or should not be restarted on exit. Choose the on-failure restart policy and limit the restart... |
| V-235842 | Medium | Docker Trusted Registry (DTR) must be integrated with a trusted certificate authority (CA) in Docker Enterprise. | Both the Universal Control Plane (UCP) and DTR components of Docker Enterprise leverage the same authentication and authorization backplane known as eNZi. The eNZi backplane includes its own... |
| V-235845 | Medium | Docker Enterprise older Universal Control Plane (UCP) and Docker Trusted Registry (DTR) images must be removed from all cluster nodes upon upgrading. | When upgrading either the UCP or DTR components of Docker Enterprise, the newer images are pulled (or unpacked if offline) onto Engine nodes in a cluster. Once the upgrade is complete, one must... |
| V-235844 | Medium | The Docker Enterprise default ulimit must not be overwritten at runtime unless approved in the System Security Plan (SSP). | The default ulimit is set at the Docker daemon level. However, override the default ulimit setting, if needed, during container runtime.
ulimit provides control over the resources available to... |
| V-235847 | Medium | Docker Content Trust enforcement must be enabled in Universal Control Plane (UCP). | The UCP and Docker Trusted Registry (DTR) components of Docker Enterprise can be used in concert with built-in audit logging capabilities to audit detected potential integrity violations per the... |
| V-235846 | Medium | Only trusted, signed images must be stored in Docker Trusted Registry (DTR) in Docker Enterprise. | The Universal Control Plane (UCP) and DTR components of Docker Enterprise can be used in concert to perform an integrity check of organization-defined software at startup. In the context of Docker... |
| V-235789 | Medium | The insecure registry capability in the Docker Engine - Enterprise component of Docker Enterprise must be disabled. | Docker considers a private registry either secure or insecure. By default, registries are considered secure.
Docker Enterprise includes the following capabilities that are considered... |
| V-235838 | Medium | Content Trust enforcement must be enabled in Universal Control Plane (UCP) in Docker Enterprise. | The UCP and Docker Trusted Registry (DTR) components of Docker Enterprise can be used in concert to perform an integrity check of organization-defined software at startup. In the context of Docker... |
| V-235839 | Medium | Only trusted, signed images must be on Universal Control Plane (UCP) in Docker Enterprise. | The UCP and Docker Trusted Registry (DTR) components of Docker Enterprise can be used in concert to perform an integrity check of organization-defined software at startup. In the context of Docker... |
| V-235782 | Medium | A policy set using the built-in role-based access control (RBAC) capabilities in the Docker Trusted Registry (DTR) component of Docker Enterprise must be set. | Both the Universal Control Plane (UCP) and DTR components of Docker Enterprise leverage the same authentication and authorization backplane known as eNZi. eNZi provides UCP and DTR with role-based... |
| V-235783 | Medium | Docker Enterprise sensitive host system directories must not be mounted on containers. | Sensitive host system directories such as below should not be allowed to be mounted as container volumes especially in read-write... |
| V-235780 | Medium | LDAP integration in Docker Enterprise must be configured. | Both the Universal Control Plane (UCP) and Docker Trusted Registry (DTR) components of Docker Enterprise leverage the same authentication and authorization backplane known as eNZi. The eNZi... |
| V-235781 | Medium | A policy set using the built-in role-based access control (RBAC) capabilities in the Universal Control Plane (UCP) component of Docker Enterprise must be configured. | Both the UCP and Docker Trusted Registry (DTR) components of Docker Enterprise leverage the same authentication and authorization backplane known as eNZi. eNZi provides UCP and DTR with role-based... |
| V-235786 | Medium | log-opts on all Docker Engine - Enterprise nodes must be configured. | The Universal Control Plane (UCP) and Docker Trusted Registry (DTR) components of Docker Enterprise provide audit record generation capabilities. Audit logs capture all HTTP actions for the... |
| V-235784 | Medium | The Docker Enterprise hosts process namespace must not be shared. | Process ID (PID) namespaces isolate the PID number space, meaning that processes in different PID namespaces can have the same PID. This is process level isolation between containers and the... |
| V-235785 | Medium | The Docker Enterprise hosts IPC namespace must not be shared. | IPC (POSIX/SysV IPC) namespace provides separation of named shared memory segments, semaphores, and message queues. IPC namespace on the host thus should not be shared with the containers and... |
| V-235827 | Medium | Docker Enterprise container health must be checked at runtime. | If the container image does not have an HEALTHCHECK instruction defined, use --health-cmd parameter at container runtime for checking container health.
One of the important security triads is... |
| V-235826 | Medium | Docker Secrets must be used to store configuration files and small amounts of user-generated data (up to 500 kb in size) in Docker Enterprise. | By leveraging Docker Secrets or Kubernetes secrets to store configuration files and small amounts of user-generated data (up to 500 kb in size), the data is encrypted at rest by the Engine's... |
| V-235797 | Medium | Periodic data usage and analytics reporting in Universal Control Plane (UCP) must be disabled in Docker Enterprise. | Docker Enterprise includes the following capabilities that are considered non-essential:
*NOTE: disabling these capabilities negatively affects the operation of UCP and Docker Trusted Registry... |
| V-235796 | Medium | The Create repository on push option in Docker Trusted Registry (DTR) must be disabled in Docker Enterprise. | Docker Enterprise includes the following capabilities that are considered non-essential:
*NOTE: disabling these capabilities negatively affects the operation of Universal Control Plane (UCP) and... |
| V-235791 | Medium | The userland proxy capability in the Docker Engine - Enterprise component of Docker Enterprise must be disabled. | The docker daemon starts a userland proxy service for port forwarding whenever a port is exposed. Where hairpin NAT is available, this service is generally superfluous to requirements and can be... |
| V-235790 | Medium | On Linux, a non-AUFS storage driver in the Docker Engine - Enterprise component of Docker Enterprise must be used. | The aufs storage driver is the oldest storage driver. It is based on a Linux kernel patch-set that is unlikely to be merged into the main Linux kernel. aufs driver is also known to cause some... |
| V-235821 | Medium | SAML integration must be enabled in Docker Enterprise. | Both the Universal Control Plane (UCP) and Docker Trusted Registry (DTR) components of Docker Enterprise leverage the same authentication and authorization backplane known as eNZi. The eNZi... |
| V-235820 | Medium | Docker Enterprise incoming container traffic must be bound to a specific host interface. | By default, Docker containers can make connections to the outside world, but the outside world cannot connect to containers. Each outgoing connection will appear to originate from one of the host... |
| V-235799 | Medium | An appropriate AppArmor profile must be enabled on Ubuntu systems for Docker Enterprise. | AppArmor protects the Ubuntu OS and applications from various threats by enforcing security policy which is also known as AppArmor profile. The user can create their own AppArmor profile for... |
| V-235798 | Medium | Periodic data usage and analytics reporting in Docker Trusted Registry (DTR) must be disabled in Docker Enterprise. | Docker Enterprise includes the following capabilities that are considered non-essential:
*NOTE: disabling these capabilities negatively affects the operation of Universal Control Plane (UCP) and... |
| V-235828 | Medium | PIDs cgroup limits must be used in Docker Enterprise. | Use --pids-limit flag at container runtime.
Attackers could launch a fork bomb with a single command inside the container. This fork bomb can crash the entire system and requires a restart of the... |
| V-235795 | Medium | The option in Universal Control Plane (UCP) allowing users and administrators to schedule containers on all nodes, including UCP managers and Docker Trusted Registry (DTR) nodes must be disabled in Docker Enterprise. | Docker Enterprise includes the following capabilities that are considered non-essential:
*NOTE: disabling these capabilities negatively affects the operation of UCP and DTR and should be... |
| V-235794 | Medium | The Docker Enterprise self-signed certificates in Docker Trusted Registry (DTR) must be replaced with DoD trusted, signed certificates. | Docker Enterprise includes the following capabilities that are considered non-essential:
*NOTE: disabling these capabilities negatively affects the operation of Universal Control Plane (UCP) and... |
| V-235825 | Medium | The Lifetime Minutes and Renewal Threshold Minutes Login Session Controls must be set to 10 and 0 respectively in Docker Enterprise. | The Universal Control Plane (UCP) component of Docker Enterprise includes a built-in access authorization mechanism called eNZi which can be integrated with an LDAP server and subsequently... |
| V-235824 | Medium | Docker Enterprise secret management commands must be used for managing secrets in a Swarm cluster. | Use Docker's in-built secret management commands for managing sensitive data that which can be stored in key/value pairs. Examples include API tokens, database connection strings and credentials,... |
| V-235823 | Medium | Docker Enterprise Swarm manager must be run in auto-lock mode. | Run Docker swarm manager in auto-lock mode.
When Docker restarts, both the TLS key used to encrypt communication among swarm nodes, and the key used to encrypt and decrypt Raft logs on disk, are... |
| V-235822 | Medium | The certificate chain used by Universal Control Plane (UCP) client bundles must match what is defined in the System Security Plan (SSP) in Docker Enterprise. | Both the UCP and Docker Trusted Registry (DTR) components of Docker Enterprise leverage the same authentication and authorization backplane known as eNZi. UCP has the ability to use external... |
| V-235793 | Medium | The Docker Enterprise self-signed certificates in Universal Control Plane (UCP) must be replaced with DoD trusted, signed certificates. | Docker Enterprise includes the following capabilities that are considered non-essential:
*NOTE: disabling these capabilities negatively affects the operation of Docker Trusted Registry (DTR) and... |
| V-235792 | Medium | Experimental features in the Docker Engine - Enterprise component of Docker Enterprise must be disabled. | Avoid experimental features in production.
Docker Enterprise includes the following capabilities that are considered non-essential:
*NOTE: disabling these capabilities negatively affects the... |
| V-235810 | Medium | Mount propagation mode must not set to shared in Docker Enterprise. | Mount propagation mode allows mounting volumes in shared, slave or private mode on a container. Do not use shared mount propagation mode until needed.
A shared mount is replicated at all mounts... |
| V-235811 | Medium | The Docker Enterprise hosts UTS namespace must not be shared. | UTS namespaces provide isolation of two system identifiers: the hostname and the NIS domain name. It is used for setting the hostname and the domain that is visible to running processes in that... |
| V-235814 | Medium | Docker Enterprise exec commands must not be used with the user option. | Do not docker exec with --user option.
Using --user option in docker exec executes the command within the container as that user. Do not run docker exec with the --user option , especially when... |
| V-235815 | Medium | cgroup usage must be confirmed in Docker Enterprise. | It is possible to attach to a particular cgroup on container run. Confirming cgroup usage would ensure that containers are running under defined cgroups.
System administrators typically define... |
| V-235834 | Medium | Log aggregation/SIEM systems must be configured to alarm when audit storage space for Docker Engine - Enterprise nodes exceed 75% usage. | The Universal Control Plane (UCP) and Docker Trusted Registry (DTR) components of Docker Enterprise provide audit record generation capabilities. Audit logs capture all HTTP actions for the... |
| V-235835 | Medium | Log aggregation/SIEM systems must be configured to notify SA and ISSO on Docker Engine - Enterprise audit failure events. | The Universal Control Plane (UCP) and Docker Trusted Registry (DTR) components of Docker Enterprise provide audit record generation capabilities. Audit logs capture all HTTP actions for the... |
| V-235836 | Medium | The Docker Enterprise log aggregation/SIEM systems must be configured to send an alert the ISSO/ISSM when unauthorized software is installed. | A Docker image is analogous to software in the context of this control.
All components of Docker Enterprise can be configured to send logs to a remote syslog server in order to meet the... |
| V-235837 | Medium | Docker Enterprise network ports on all running containers must be limited to what is needed. | By itself, Docker Engine - Enterprise is configured by default to listen for API requests via a UNIX domain socket (or IPC socket) created at /var/run/docker.sock on supported Linux distributions... |
| V-235830 | Medium | Docker Enterprise images must be built with the USER instruction to prevent containers from running as root. | Both the Universal Control Plane (UCP) and Docker Trusted Registry (DTR) components of Docker Enterprise leverage the same authentication and authorization backplane known as eNZi. The eNZi... |
| V-235831 | Medium | An appropriate Docker Engine - Enterprise log driver plugin must be configured to collect audit events from Universal Control Plane (UCP) and Docker Trusted Registry (DTR). | The UCP and DTR components of Docker Enterprise provide audit record generation capabilities. Audit logs capture all HTTP actions for the following endpoints: Kubernetes API, Swarm API and UCP... |
| V-235832 | Medium | The Docker Enterprise max-size and max-file json-file drivers logging options in the daemon.json configuration file must be configured to allocate audit record storage capacity for Universal Control Plane (UCP) and Docker Trusted Registry (DTR) per the requirements set forth by the System Security Plan (SSP). | By default, the UCP and DTR components of Docker Enterprise leverage the "json-file" Engine logging driver. This driver has configurable "max-size" and "max-file" options which are applicable in... |
| V-235833 | Medium | All Docker Engine - Enterprise nodes must be configured with a log driver plugin that sends logs to a remote log aggregation system (SIEM). | The Universal Control Plane (UCP) and Docker Trusted Registry (DTR) components of Docker Enterprise provide audit record generation capabilities. Audit logs capture all HTTP actions for the... |
| V-235804 | Medium | Only required ports must be open on the containers in Docker Enterprise. | Dockerfile for a container image defines the ports to be opened by default on a container instance. The list of ports may or may not be relevant to the application running within the container.
A... |
| V-235806 | Medium | Memory usage for all containers must be limited in Docker Enterprise. | By default, all containers on a Docker host share the resources equally. By using the resource management capabilities of Docker host, such as memory limit, the amount of memory that a container... |
| V-235776 | Medium | TCP socket binding for all Docker Engine - Enterprise nodes in a Universal Control Plane (UCP) cluster must be disabled. | The UCP component of Docker Enterprise configures and leverages Swarm Mode for node-to-node cluster communication. Swarm Mode is built in to Docker Engine - Enterprise and uses TLS 1.2 at a... |
| V-235802 | Medium | Privileged Linux containers must not be used for Docker Enterprise. | Using the --privileged flag gives all Linux Kernel Capabilities to the container thus overwriting the --cap-add and --cap-drop flags. Ensure that it is not used. The --privileged flag gives all... |
| V-235779 | Medium | The host operating systems auditing policies for the Docker Engine - Enterprise component of Docker Enterprise must be set. | The Universal Control Plane (UCP) and Docker Trusted Registry (DTR) components of Docker Enterprise provide audit record generation capabilities. Audit logs capture all HTTP actions for the... |
| V-235778 | Medium | The audit log configuration level must be set to request in the Universal Control Plane (UCP) component of Docker Enterprise. | The UCP and Docker Trusted Registry (DTR) components of Docker Enterprise provide audit record generation capabilities. Audit logs capture all HTTP actions for the following endpoints: Kubernetes... |
| V-235801 | Medium | Linux Kernel capabilities must be restricted within containers as defined in the System Security Plan (SSP) for Docker Enterprise. | By default, Docker starts containers with a restricted set of Linux Kernel Capabilities. It means that any process may be granted the required capabilities instead of root access. Using Linux... |
| V-235800 | Medium | SELinux security options must be set on Red Hat or CentOS systems for Docker Enterprise. | SELinux provides a Mandatory Access Control (MAC) system on RHEL and CentOS that greatly augments the default Discretionary Access Control (DAC) model. The user can thus add an extra layer of... |
| V-235803 | Medium | SSH must not run within Linux containers for Docker Enterprise. | SSH server should not be running within the container. The user should instead use Universal Control Plane (UCP) to console in to running containers.
Running SSH within the container increases... |
| V-235871 | Medium | Docker Enterprise Universal Control Plane (UCP) must be integrated with a trusted certificate authority (CA). | When integrating the UCP and Docker Trusted Registry (DTR) management consoles with an external, trusted certificate authority (CA), both UCP and DTR will validate these certificate chains per the... |
| V-235872 | Medium | Docker Enterprise data exchanged between Linux containers on different nodes must be encrypted on the overlay network. | Encrypt data exchanged between containers on different nodes on the overlay network.
By default, data exchanged between containers on different nodes on the overlay network is not encrypted. This... |
| V-235873 | Medium | Docker Enterprise Swarm services must be bound to a specific host interface. | By default, the docker swarm services will listen to all interfaces on the host, which may not be necessary for the operation of the swarm where the host has multiple network interfaces.
When a... |
| V-235874 | Medium | Docker Enterprise Universal Control Plane (UCP) must be configured to use TLS 1.2. | By default docker UCP is configured to use TLS v1.2, if this setting is misconfigured, older protocols containing security weaknesses could be utilized. TLS requires a handshake between client and... |
| V-235788 | Low | Docker Incs official GPG key must be added to the host using the users operating systems respective package repository management tooling. | All packaged components of Docker Enterprise are digitally signed using GPG keys maintained by Docker, Inc. The Docker Engine - Enterprise daemon, itself, is digitally signed. Furthermore, all... |
| V-235787 | Low | Docker Enterprise must alert the ISSO and SA (at a minimum) in the event of an audit processing failure. | The Universal Control Plane (UCP) and Docker Trusted Registry (DTR) components of Docker Enterprise provide audit record generation capabilities. Audit logs capture all HTTP actions for the... |
| V-235829 | Low | The Docker Enterprise per user limit login session control must be set per the requirements in the System Security Plan (SSP). | The Universal Control Plane (UCP) component of Docker Enterprise includes a built-in access authorization mechanism called eNZi which can be integrated with an LDAP server and allows for automatic... |
| V-235807 | Low | Docker Enterprise CPU priority must be set appropriately on all containers. | By default, all containers on a Docker host share the resources equally. By using the resource management capabilities of Docker host, such as CPU shares, the user control the host CPU resources... |
| V-235775 | Low | The Docker Enterprise Per User Limit Login Session Control in the Universal Control Plane (UCP) Admin Settings must be set to an organization-defined value for all accounts and/or account types. | The UCP component of Docker Enterprise includes a built-in access authorization mechanism called eNZi which can be integrated with an LDAP server and subsequently configured to limit the number of... |
