---
title: Incoming container traffic should be bound to a specific host interface
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: >-
  Docs > Datadog Security > OOTB Rules > Incoming container traffic should be
  bound to a specific host interface
---

> For the complete documentation index, see [llms.txt](https://docs.datadoghq.com/llms.txt).

# Incoming container traffic should be bound to a specific host interface
Classification:complianceFramework:cis-dockerControl:5.14 
## Description{% #description %}

Containers should publish their ports on a specific host interface.

## Rationale{% #rationale %}

A port published on every interface is reachable from every network of the host, where the service may need one.

## Audit{% #audit %}

Inspect the containers:

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

Datadog checks the running containers. It passes the rule when every published port binds a specific host address, and fails it when one binds `0.0.0.0`, `::` or every address.

## Remediation{% #remediation %}

Publish the port on the address that should serve it:

```bash
docker run -p 10.0.0.5:8080:80 <image>
```

## Impact{% #impact %}

None.

## Default value{% #default-value %}

Docker publishes ports on every interface of the host.

## References{% #references %}

1. [https://docs.docker.com/engine/network/](https://docs.docker.com/engine/network/)
