The Docker Bench for Security is a script that checks for dozens of common best-practices around deploying Docker containers in production.
Find a file
Thomas Sjögren 34e765cff5 correct image link
Signed-off-by: Thomas Sjögren <konstruktoid@users.noreply.github.com>
2016-04-21 20:33:32 +02:00
distros use debian default docker.io 2016-03-01 21:37:23 +01:00
tests update chap 6 to cis 1.11 2016-04-15 00:23:03 +02:00
.dockerignore add .dockerignore 2015-05-30 12:59:22 +02:00
.gitignore First version of the CIS Docker Benchmark v1.0.0 2015-05-13 15:26:45 -07:00
benchmark_log.png update screenshot 2016-04-20 21:09:57 +02:00
CONTRIBUTING.md tests tree 2015-06-21 22:07:07 +02:00
docker-bench-security.sh missing file as non-root user 2015-09-05 16:23:34 +02:00
docker-compose.yml use compose to improve readability 2015-10-06 07:30:21 +02:00
Dockerfile update to v1.10.0 2016-02-05 20:56:25 +01:00
helper_lib.sh check /etc/systemd/system/ before systemctl, /usr/lib/systemd/ fallback 2015-12-14 20:27:10 +01:00
LICENSE.md Fix unpopulated copyright in license 2015-05-29 11:12:47 -07:00
MAINTAINERS Add MAINTAINERS file 2015-12-07 18:49:11 +01:00
output_lib.sh Double quote to prevent globbing and word splitting. 2015-05-31 12:26:37 +02:00
README.md correct image link 2016-04-21 20:33:32 +02:00

Docker Bench for Security

Docker Bench for Security running

The Docker Bench for Security is a script that checks for dozens of common best-practices around deploying Docker containers in production. The tests are all automated, and are inspired by the CIS Docker 1.11 Benchmark. We are releasing this as a follow-up to our Understanding Docker Security and Best Practices blog post.

We are making this available as an open-source utility so the Docker community can have an easy way to self-assess their hosts and docker containers against this benchmark.

Running Docker Bench for Security

We packaged docker bench as a small container for your convenience. Note that this container is being run with a lot of privilege -- sharing the host's filesystem, pid and network namespaces, due to portions of the benchmark applying to the running host.

The easiest way to run your hosts against the Docker Bench for Security is by running our pre-built container:

docker run -it --net host --pid host --cap-add audit_control \
    -v /var/lib:/var/lib \
    -v /var/run/docker.sock:/var/run/docker.sock \
    -v /usr/lib/systemd:/usr/lib/systemd \
    -v /etc:/etc --label docker_bench_security \
    docker/docker-bench-security

Docker bench requires Docker 1.6.2 or later in order to run, since it depends on the --label to exclude the current container from being inspected. If you can't upgrade to 1.6.2, feel free to remove the --label flag or run the shell script locally (see below).

Additionally, there was a bug in Docker 1.6.0 that would not allow mounting -v /dev:/dev. If you are getting an error while accessing resolv.conf, please update your docker to 1.6.2.
Also note that the default image and Dockerfile uses FROM: alpine which doesn't contain auditctl, this will generate errors in section 1.8 to 1.18. Distribution specific Dockerfiles that fixes this issue are available in the distros directory.

Building Docker Bench for Security

If you wish to build and run this container yourself, you can follow the following steps:

git clone https://github.com/docker/docker-bench-security.git
cd docker-bench-security
docker build -t docker-bench-security .
docker run -it --net host --pid host --cap-add audit_control \
    -v /var/lib:/var/lib \
    -v /var/run/docker.sock:/var/run/docker.sock \
    -v /usr/lib/systemd:/usr/lib/systemd \
    -v /etc:/etc --label docker_bench_security \
    docker-bench-security

or use Docker Compose:

git clone https://github.com/docker/docker-bench-security.git
cd docker-bench-security
docker-compose run --rm docker-bench-security

Also, this script can also be simply run from your base host by running:

git clone https://github.com/docker/docker-bench-security.git
cd docker-bench-security
sh docker-bench-security.sh

This script was build to be POSIX 2004 compliant, so it should be portable across any Unix platform.