https://github.com/complianceascode/auditree-framework
The Auditree framework tool to run compliance control checks as unit tests.
https://github.com/complianceascode/auditree-framework
compliance compliance-as-code compliance-automation continuous-compliance devops devsecops python
Last synced: 24 days ago
JSON representation
The Auditree framework tool to run compliance control checks as unit tests.
- Host: GitHub
- URL: https://github.com/complianceascode/auditree-framework
- Owner: ComplianceAsCode
- License: apache-2.0
- Created: 2020-04-29T14:21:12.000Z (about 5 years ago)
- Default Branch: main
- Last Pushed: 2024-08-20T12:48:36.000Z (9 months ago)
- Last Synced: 2025-04-03T02:11:14.796Z (about 1 month ago)
- Topics: compliance, compliance-as-code, compliance-automation, continuous-compliance, devops, devsecops, python
- Language: Python
- Homepage: https://auditree.github.io/
- Size: 2.08 MB
- Stars: 63
- Watchers: 8
- Forks: 23
- Open Issues: 28
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGES.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
- Codeowners: .github/CODEOWNERS
Awesome Lists containing this project
README
[![OS Compatibility][platform-badge]](#prerequisites)
[![Python Compatibility][python-badge]][python]
[![pre-commit][pre-commit-badge]][pre-commit]
[][lint-test]
[][pypi-upload]
# 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](https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/)
### Check out the code
```shell
git clone [email protected]:ComplianceAsCode/auditree-framework
cd auditree-framework
```
### For users
```shell
python3 -m venv venv
. venv/bin/activate
make install
```
### For developers
```shell
python3 -m venv venv
. venv/bin/activate
make develop
```
#### Code style and formatting
This repository uses [black][black] for code formatting and [flake8][flake8] for code styling. It also
uses [pre-commit][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][pre-commit-config] 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:
```shell
make code-format
make code-lint
```
...will run `black` and `flake8` on the entire repo and is equivalent to:
```shell
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:
```shell
pre-commit run black --files compliance/*
pre-commit run flake8 --files compliance/*
```
#### Unit tests
To run the frameworks test suite, use:
```shell
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:
```shell
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:
```shell
$ touch ~/.credentials
```
- Set up your environment:
```shell
cd demo
python -m venv
. ./venv/bin/activate
pip install -r requirements.txt
```
- Run the fetchers:
```shell
compliance --fetch --evidence local -C auditree_demo.json -v
```
- Run the checks:
```shell
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](https://github.com/ComplianceAsCode/auditree-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](https://github.com/ComplianceAsCode/auditree-harvest) which lets you process your evidence locker and generate reports over the data held.
We have a tool called [Prune](https://github.com/ComplianceAsCode/auditree-prune) which lets you mark evidence as no longer being collected, in a suitably tracked manner.
We have a tool called [Plant](https://github.com/ComplianceAsCode/auditree-plant) which lets you add evidence to evidence lockers without the use of fetchers or checks.
[CONTRIBUTING]: https://github.com/ComplianceAsCode/auditree-framework/blob/master/CONTRIBUTING.md
[credentials file]: https://github.com/ComplianceAsCode/auditree-framework/blob/master/doc/design-principles.rst#credentials
[flake8]: https://gitlab.com/pycqa/flake8
[platform-badge]: https://img.shields.io/badge/platform-osx%20|%20linux-orange.svg
[pre-commit-badge]: https://img.shields.io/badge/pre--commit-enabled-brightgreen?logo=pre-commit&logoColor=white
[pre-commit]: https://github.com/pre-commit/pre-commit
[pre-commit-config]: https://github.com/ComplianceAsCode/auditree-framework/blob/master/.pre-commit-config.yaml
[python-badge]: https://img.shields.io/badge/python-v3.6+-blue.svg
[python]: https://www.python.org/downloads/
[quick start guide]: https://github.com/ComplianceAsCode/auditree-framework/blob/master/doc-source/quick-start.rst
[black]: https://github.com/psf/black
[lint-test]: https://github.com/ComplianceAsCode/auditree-framework/actions?query=workflow%3A%22format+%7C+lint+%7C+test%22
[pypi-upload]: https://github.com/ComplianceAsCode/auditree-framework/actions?query=workflow%3A%22PyPI+upload%22
[credentials]: https://complianceascode.github.io/auditree-framework/design-principles.html#credentials