|
| 1 | +# Hyperproof |
| 2 | + |
| 3 | +This is a system to collect evidence (proofs) of our security and compliance |
| 4 | +posture, and sync them with our compliance management system ([Hyperproof]). |
| 5 | + |
| 6 | +## Usage |
| 7 | + |
| 8 | +You can run the system from GitHub Actions (recommended), or locally. |
| 9 | + |
| 10 | +### GitHub Actions |
| 11 | + |
| 12 | +Run the [Hyperproof Sync][workflow] from the GitHub Actions tab of this |
| 13 | +repository. Alternatively, if you have the [GitHub CLI][gh] installed, you can |
| 14 | +run the workflow from the command line: |
| 15 | + |
| 16 | +```bash |
| 17 | +gh workflow run hyperproof.yaml |
| 18 | +``` |
| 19 | + |
| 20 | +### Locally |
| 21 | + |
| 22 | +If you want to run the system locally — to test changes or debug issues, for |
| 23 | +example — you will first need to install the necessary dependencies. Use your |
| 24 | +favorite ruby version manager to install the required [version of |
| 25 | +ruby][ruby-version]. |
| 26 | + |
| 27 | +Make sure you've switched to the `hyperproof` directory in the repository, then |
| 28 | +install the dependencies using `bundler`: |
| 29 | + |
| 30 | +```bash |
| 31 | +cd hyperproof |
| 32 | +bundle install |
| 33 | +``` |
| 34 | + |
| 35 | +You should now be able to run use the provided CLI command. You can check the |
| 36 | +current version to verify that everything is working: |
| 37 | + |
| 38 | +```bash |
| 39 | +./bin/hyperproof version |
| 40 | +``` |
| 41 | + |
| 42 | +If you see the version number, you're good to go! You can now run the full |
| 43 | +system with: |
| 44 | + |
| 45 | +```bash |
| 46 | +./bin/hyperproof collect |
| 47 | +``` |
| 48 | + |
| 49 | +[gh]: https://cli.github.com/ |
| 50 | +[hyperproof]: https://hyperproof.io/ |
| 51 | +[ruby-version]: https://github.com/codeforamerica/cfa-security-controls/tree/main/hyperproof/.ruby-version |
| 52 | +[workflow]: https://github.com/codeforamerica/cfa-security-controls/actions/workflows/hyperproof.yaml |
0 commit comments