compliance-trestle
compliance-trestle copied to clipboard
oscal-compass
An opinionated tooling platform for managing compliance as code, using continuous integration and NIST's OSCAL standard.
## Issue description / feature objectives The current generator implementation is a step up from the initial implementation. Ontop of this: 1. Add mode to generate unique id's e.g. uuids...
## Issue description / feature objectives Referencing: https://github.com/GSA/fedramp-automation/blob/master/documents/Guide_to_OSCAL-based_FedRAMP_System_Security_Plans_(SSP).pdf and: Image data can be included in documents in two ways: 1. Explicitly by diagram element in an SSP 2. Implicitly by...
## Issue description / feature objectives Today the SSP generation workflow has no 'nice to haves' which make editing for non git experts easier (presuming the documentation is hosted in...
## Issue description / feature objectives OSCAL describe a subset of markdown that is supported for the markup data types. https://pages.nist.gov/OSCAL/reference/datatypes/#markup-data-types Unfortunately this is not captured by our current schema....
## Issue description / feature objectives Parameters in OSCAL can be set in multiple locations (implicitily as a default value in the catalog and profile), explicitly in the profile and...
For this we need need 2-3 tutorials (really small derivatives) under the current banner of 'actions' - One for explicitly for github actions - Another for Travis - Another (ideally)...
Below list captures some of the issues identified in FedRAMP_extensions.json file or some suggestions for improvement. 1. Some of the required fields mentioned in pdf files - both common across...
The current implementation of managed repository is a good step in the right direction but the behavior of some commands such as split will require some tweaking. Some points: -...
## Issue description / feature objectives Today SSP's are consumed in word document format. To facilitate working with organisations not 'onboard' with OSCAL there needs to be an OSCAL ssp...
When I generate a catalog using generators, it does not generate metadata.props. But when I run the following command - trestle split -f 'catalog.json' -e 'catalog.metadata' and then go to...
Metadata
Owner
Metadata
An opinionated tooling platform for managing compliance as code, using continuous integration and NIST's OSCAL standard.