1. Home
  2. Security Hardening
  3. CIS Docker 1.6 V1.0.0 L1 Docker
  4. Do not bind Docker to another IP/Port or a Unix socket

Do not bind Docker to another IP/Port or a Unix socket

Details

https://docs.docker.com/articles/basics/#bind-docker-to-another-hostport-or-a-unix-socket

Solution

Do not bind the Docker daemon to any IP and Port or a non-default Unix socket.For example, do not start the Docker daemon as below-$> docker -H tcp-//10.1.2.3-2375 -H unix-///var/run/example.sock -d

Impact-No one can have full access to Docker daemon except ‘root’. Alternatively, you should
configure the TLS authentication for Docker and Docker Swarm APIs if you want to bind
the Docker daemon to any other IP and Port.

Default Value-By default, Docker daemon binds to a non-networked Unix socket.

Supportive Information

The following resource is also helpful.

This security hardening control applies to the following category of controls within NIST 800-53: Configuration Management.This control applies to the following type of system Unix.

References

Source

Updated on July 16, 2022
Was this article helpful?

Related Articles