DKER-EE-001970 - SSH must not run within Linux containers for Docker Enterprise.

Information

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 the complexity of security management by making it:

- Difficult to manage access policies and security compliance for SSH server
- Difficult to manage keys and passwords across various containers
- Difficult to manage security upgrades for SSH server
- It is possible to have shell access to a container without using SSH, the needlessly increasing the complexity of security management should be avoided

By default, SSH server is not running inside the container. Only one process per container is allowed.

Solution

This fix only applies to the use of Docker Engine - Enterprise on a Linux host operating system and should be executed on all nodes in a Docker Enterprise cluster.

Remove SSH packages from all Docker base images in use in the user's environment.

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_Docker_Enterprise_2-x_Linux-Unix_V2R2_STIG.zip

Item Details

Category: CONFIGURATION MANAGEMENT

References: 800-53|CM-7a., CAT|II, CCI|CCI-000381, Rule-ID|SV-235803r960963_rule, STIG-ID|DKER-EE-001970, STIG-Legacy|SV-104779, STIG-Legacy|V-95641, Vuln-ID|V-235803

Plugin: Unix

Control ID: 7e461e8ce29fca37cad6f29fbc848fd7927818a1bd4dbfc4c7d9df49132cf5c8