STIGQter: STIG Summary: Docker Enterprise 2.x Linux/UNIX Security Technical Implementation Guide Version: 2 Release: 1 Benchmark Date: 23 Apr 2021:

Docker Enterprise privileged ports must not be mapped within containers.

DISA Rule

SV-235819r627584_rule

Vulnerability Number

V-235819

Group Title

SRG-APP-000142

Rule Version

DKER-EE-002150

Severity

CAT I

CCI(s)

• CCI-000382 - The organization configures the information system to prohibit or restrict the use of organization-defined functions, ports, protocols, and/or services.

Weight

10

Fix Recommendation

This fix only applies to the use of Docker Engine - Enterprise.

Do not map the container ports to privileged host ports when starting a container. Also, ensure that there is no such container to host privileged port mapping declarations in the Dockerfile.

Check Contents

This check should be executed on all nodes in a Docker Enterprise cluster.

Verify that no running containers are mapping host port numbers below 1024.

via CLI:

Linux: Execute the following command as a trusted user on the host operating system:

docker ps --quiet --all | xargs docker inspect --format '{{ .Id }}: Ports={{ .NetworkSettings.Ports }}'

Review the list and ensure that container ports are not mapped to host port numbers below 1024. If they are, then this is a finding.

Vulnerability Number

V-235819

Documentable

False

Rule Version

DKER-EE-002150

Severity Override Guidance

This check should be executed on all nodes in a Docker Enterprise cluster.

Verify that no running containers are mapping host port numbers below 1024.

via CLI:

Linux: Execute the following command as a trusted user on the host operating system:

docker ps --quiet --all | xargs docker inspect --format '{{ .Id }}: Ports={{ .NetworkSettings.Ports }}'

Review the list and ensure that container ports are not mapped to host port numbers below 1024. If they are, then this is a finding.

Check Content Reference

M

Target Key

5281

Comments