End-to-End Demo: Ubuntu Component Definitions

Repository to demo oscal based component definitions and agile authoring using compliance-trestle and github actions

The demo overview.

1. Input: It was initialized with OSCAL catalog.json, profile.json, Ubuntu yml from ComplianceAsCode, and control selections specified in spread sheets.

2. Processing: Changes to any of the input files will cause regeneration of the software and validation component definitions.

   • type=software Component Definition
   • type=validation Component Definition

3. Output: Updated component-definition.json files in component-definition repo

4. Next action: Updated component-definition.json files pushed to ssp repo

Demo for this repo:

• Show changes to spread sheet (delete control, re-add control) are incorporated into component-definition.json files