DKER-EE-001990 - 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 container can be run just with the ports defined in the Dockerfile for its image or can be arbitrarily passed run time parameters to open a list of ports. Additionally, over time, Dockerfile may undergo various changes and the list of exposed ports may or may not be relevant to the application running within the container. Opening unneeded ports increase the attack surface of the container and the containerized application. As a recommended practice, do not open unneeded ports.

By default, all the ports that are listed in the Dockerfile under EXPOSE instruction for an image are opened when a container is run with -P or --publish-all flag.


Document the ports required for each container in the SSP.

Fix the Dockerfile of the container image to expose only needed ports by the containerized application. Ignore the list of ports defined in the Dockerfile by NOT using -P (UPPERCASE) or --publish-all flag when starting the container. Use the -p (lowercase) or --publish flag to explicitly define the ports needed for a particular container instance.

docker run --interactive --tty --publish 5000 --publish 5001 --publish 5002 centos /bin/bash

See Also

Item Details


References: 800-53|CM-7a., CAT|II, CCI|CCI-000381, Rule-ID|SV-235804r627539_rule, STIG-ID|DKER-EE-001990, STIG-Legacy|SV-104781, STIG-Legacy|V-95643, Vuln-ID|V-235804

Plugin: Unix

Control ID: b0b768770282ad1450e3d27c85c0fa3bd03c31d43335b474f45707bc99a10fbe