Skip to content
This repository has been archived by the owner on Oct 3, 2018. It is now read-only.


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time


This project is obsolete, the functionality is provided by the oscap-docker tool that ships with OpenSCAP.

Container Compliance

Resources and tools to assert compliance of containers (rocket, docker, ...).

  • Assessing running containers and cold images
  • Vulnerability and compliance audit

Build Status

Vulnerability scan of Docker image

# oscap-docker image-cve IMAGE_NAME \
    [--results OVAL.XML [--report REPORT.HTML]]

This command will attach docker image, determine OS variant/version, download CVE stream applicable to the given OS, and finally run vulnerability scan.

Exemplary usage

Tested on Fedora host.

# yum install openscap-scanner docker-io
# service docker start
# docker pull
# oscap-docker image-cve \
    --results oval.xml --report rhel7.html
$ firefox rhel7.html

Scanning Docker image using OpenSCAP

Run any OpenSCAP command within chroot of mounted docker image.

# oscap-docker image IMAGE_NAME [OSCAP_ARGUMENTS]

Learn more about OSCAP_ARGUMENTS in man oscap.

Exemplary usage

Tested on Fedora host.

# yum install scap-security-guide openscap-scanner docker-io
# sed -i 's/<platform idref=.*$//g' /usr/share/xml/scap/ssg/fedora/ssg-fedora-ds.xml
# service docker start
# docker pull fedora
# oscap-docker image fedora xccdf eval \
    --profile xccdf_org.ssgproject.content_profile_common \

Scanning Docker container

Run OpenSCAP scan within chroot of running docker container. This may differ from scanning docker image due to defined mount points.

# oscap-docker container CONTAINER_NAME [OSCAP_ARGUMENTS]

Vulnerability scan of Docker container

Run OpenSCAP scan within chroot of running docker container. This may differ from scanning docker image due to defined mount points.

# oscap-docker container-cve CONTAINER_NAME \
    [--results OVAL.XML [--report REPORT.HTML]]

Future features

Vulnerability scan of all images

The output of the tool could look like:

# oscap-docker cve --all --download --arf report-arf.xml
Fetching OVAL definitions for RHSA ........ ok
Inflating ....... ok
Scanning rhel7-elasticsearch ...... ok (compliant, no CVE identified)
Scanning rhel7-mongodb ......... fail (2 CVE found)
Scanning ubuntu-httpd ......... notchecked (no CVE definitions)
Exporting Asset Report ......... ok
CVE Scan finished in 1m35s

Contribute ? Build yourself ?


In order to build this image, you will need:

Basic workflow

  1. Fork this repository on Github
  2. Clone your forked version on your machine
  3. Within your command line, navigate to the root of this repository
  4. Just run one of these make targets:
  • make all: to run the full workflow
  • make build: just to build the Docker image
  • make test: to launch testing of the docker image
  • make deploy: to do nothing since it will run only in CI environment

Under the Hood

  • Make is used to express the lifecycle with its targets: build, test, deployand all

  • Docker-Compose will describe the Docker options in a centralized way:

    • What are the instance parts of the build ?
    • What to build ?
    • What are the options to pass to docker (shared volumes, etc.)
  • Docker is used as a Linux instance hypervisor here: it is ligthweight isolation that helps to reproduces software behaviors across differents machines.

  • TravisCI is used for continuous Integration. If all tests are passing, then it will "deploy" by requesting the DockerHub to "autobuild" the image: providing full testing AND open Dockerfile.


Copyright (c) 2014--2015 Šimon Lukašík

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program. If not, see


Assessing compliance of a container







No releases published


No packages published

Contributors 4