# Cis Docker V170 5.9

> Ensure that only needed ports are open on the container

- Skill: `cyberstrikeus/cis-docker-v170-5-9` (Agent Skill)
- Install (CLI): `npx skillmds@latest add cyberstrikeus/cis-docker-v170-5-9`
- Raw SKILL.md: https://api.skillmd.com/api/skills/cyberstrikeus/cis-docker-v170-5-9/raw
- Safety review: PASS (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: cyberstrikeus (https://skillmd.com/u/cyberstrikeus)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/cyberstrikeus/cis-docker-v170-5-9

---


# CIS Docker Benchmark v1.7.0 - Control 5.9

## Profile Applicability

- Level 1 - Docker - Linux

## Description

The dockerfile for a container image defines the ports which are opened by default on a container instance. The list of ports are relevant to the application you are running within the container and should only be open if they are needed.

## Rationale

A container can be run with only the ports defined in the Dockerfile for its image or can alternatively be arbitrarily passed on the command line parameter to open a list of ports. Additionally, in the course of time, the Dockerfile may undergo various changes and the list of exposed ports may or may not still be relevant to the application you are running within the container. Opening unneeded ports increases the attack surface of the container and the associated containerized application. Good security practice is to only open ports that are needed for the correct operation of the application.

## Impact

None.

## Audit Procedure

You should list all the running instances of containers and their associated port mappings by executing the command below:

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

You should then review the list and ensure that all the ports mapped are in fact genuinely required by each container.

## Remediation

You should ensure that the Dockerfile for each container image only exposes needed ports. You can also completely ignore the list of ports defined in the Dockerfile by NOT using `-P` (UPPERCASE) or `--publish-all` flag when starting the container.

Instead, use the `-p` (lowercase) or `--publish` flag to explicitly define the ports that you need for a particular container instance.

For example:

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

## Default Value

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

## References

1. https://docs.docker.com/engine/userguide/networking/

## CIS Controls

**v8:**

- 13.9 Deploy Port-Level Access Control - Deploy port-level access control. Port-level access control utilizes 802.1x, or similar network access control protocols, such as certificates, and may incorporate user and/or device authentication.

**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.

## Assessment Status

Manual