OpenParable
Skip to content
← Back to skills

Cis Docker 5.7

DevOps & Security
cis-docker-5.7

Cis Docker 5.7 is an Agent Skill for devops & security published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Ensure sshd is not run within containers

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/CIS_benchmarks/Server_Software/Docker/CIS_Docker_Benchmark_v1.8.0/cis-docker-5.7/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cis-docker-5-7, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

5.7 Ensure sshd is not run within containers (Manual)

Profile Applicability

  • Level 1 - Docker - Linux

Description

The SSH daemon should not be running within the container. You should SSH into the Docker host, and use docker exec to enter a container.

Rationale

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.

Impact

None.

Audit Procedure

List all the running instances of containers by executing below command:

docker ps --quiet

For each container instance, execute the below command:

docker exec <CONTAINER_ID> ps -el

Ensure that there is no process for SSH server.

Remediation

Uninstall the SSH daemon from the container and use and use docker exec to enter a container on the remote host.

docker exec --interactive --tty <CONTAINER_ID> sh

OR

docker attach <CONTAINER_ID>

Default Value

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

References

  1. https://jpetazzo.github.io/2014/06/23/docker-ssh-considered-evil/

CIS Controls

v8

4.8 Uninstall or Disable Unnecessary Services on Enterprise Assets and Software

Uninstall or disable unnecessary services on enterprise assets and software, such as an unused file sharing service, web application module, or service function.

v7

9.2 Ensure Only Approved Ports, Protocols and Services Are Running

Ensure that only network ports, protocols, and services listening on a system with validated business needs, are running on each system.