auditree-framework

Tool to run compliance control checks as unit tests and build up a body of evidence.

This framework gives you the tools you need to create an auditable body of evidence, and is designed to be “DevSecOps” friendly. Collection & validation of evidence is modelled as python unit tests, evidence is stored & versioned in a git repository, notifications can be configured to send to Slack, create issues, contact PagerDuty, or just write files into git. The goal is to enable the digital transformation of compliance activities, and make these everyday operational tasks for the team managing the system.

Installation

Prerequisites

• Supported for execution on OSX and LINUX.
• Supported for execution with Python 3.6 and above.

If you haven’t already you need to generate a new ssh key for your Github account as per this guide

Check out the code

git clone [email protected]:ComplianceAsCode/auditree-framework
cd auditree-framework

For users

python3 -m venv venv
. venv/bin/activate
make install

For developers

python3 -m venv venv
. venv/bin/activate
make develop

Code style and formatting

This repository uses black for code formatting and flake8 for code styling. It also
uses pre-commit hooks that are integrated into the development process and the CI. When
you run make develop you are ensuring that the pre-commit hooks are installed and updated to their
latest versions for this repository. This ensures that all delivered code has been properly formatted
and passes the linter rules. See the pre-commit configuration file for details on
black and flake8 configurations.

Since black and flake8 are installed as part of the pre-commit hooks, running black and flake8
manually must be done through pre-commit. See examples below:

make code-format
make code-lint

…will run black and flake8 on the entire repo and is equivalent to:

pre-commit run black --all-files
pre-commit run flake8 --all-files

…and when looking to limit execution to a subset of files do similar to:

pre-commit run black --files compliance/*
pre-commit run flake8 --files compliance/*

Unit tests

To run the frameworks test suite, use:

make test

Build Documentation

Documentation sources live in doc-source, and are also auto-generated from the source codes doc strings. The auto-generated documentation (compliance*rst, modules.rst) is ignored by git & should not be modified directly - make changes in the python code.

To build the documentation locally run:

make docs

This will update the files in doc with the latest documentation. These files should not be modified by hand.

Try it

Successfully complete the steps below and you should be able to find your local
evidence locker in your $TMPDIR/compliance folder. There you will find a raw
folder that contains all of the raw evidence fetched by the fetchers found in the
demo/demo_examples/fetchers folder along with a reports folder that contains
the reports generated by the checks found in the demo/demo_examples/checks folder.

• Create an empty credentials file:

$ touch ~/.credentials

• Set up your environment:

cd demo
python -m venv
. ./venv/bin/activate
pip install -r requirements.txt

• Run the fetchers:

compliance --fetch --evidence local -C auditree_demo.json -v

• Run the checks:

compliance --check demo.arboretum.accred,demo.custom.accred --evidence local -C auditree_demo.json -v

Contribute

Help us to improve the Auditree framework. See CONTRIBUTING.

Ecosystem

We are building a set of common fetchers/checks in Arboretum. If you have a library of checks, please let us know & we’ll link here.

We have a data gathering and reporting tool called Harvest which lets you process your evidence locker and generate reports over the data held.

We have a tool called Prune which lets you mark evidence as no longer being collected, in a suitably tracked manner.

We have a tool called Plant which lets you add evidence to evidence lockers without the use of fetchers or checks.