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 2f0112497a md formating
Signed-off-by: Thomas Sjögren <konstruktoid@users.noreply.github.com>
2017-07-07 12:02:15 +02:00
distros alpine 3.6 2017-05-29 12:03:04 +02:00
tests add Docker Swarm Configuration tests 2017-07-07 11:43:15 +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 less ugly image 2017-01-26 10:15:38 +01:00
CONTRIBUTING.md md formating 2017-07-07 12:02:15 +02:00
docker-bench-security.sh update versions, CIS Docker Community Edition Benchmark 2017-07-07 10:22:57 +02:00
docker-compose.yml use compose to improve readability 2015-10-06 07:30:21 +02:00
Dockerfile alpine 3.6 2017-05-29 12:03:04 +02:00
helper_lib.sh Modify get_docker_configuration_file_args in order to handle daemon.json better, 2017-03-21 14:49:42 +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 add note tag on informal checks 2017-03-23 11:29:58 +01:00
README.md Update to CIS Docker Community Edition Benchmark 2017-07-07 10:22:27 +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 Community Edition Benchmark v1.1.0. 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. Don't forget to adjust the shared volumes according to your operating system, for example it might not use systemd.

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 \
    -e DOCKER_CONTENT_TRUST=$DOCKER_CONTENT_TRUST \
    -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.10.0 or later in order to run.

Note that when distributions doesn't contain auditctl, the audit tests will check /etc/audit/audit.rules to see if a rule is present instead.

Distribution specific Dockerfiles that fixes this issue are available in the distros directory.

The distribution specific Dockerfiles may also help if the distribution you're using haven't yet shipped Docker version 1.10.0 or later.

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 \
    -e DOCKER_CONTENT_TRUST=$DOCKER_CONTENT_TRUST \
    -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.