compliance-trestle

compliance-trestle copied to clipboard

## Types of changes - [ ] Hot fix (emergency fix and release) - [x] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change...

degenaro

## Describe the bug Some links may links to other sites, e.g. NIST OSCAL, may not be working, e.g. due to relocation. ## To Reproduce Check external links. If all...

degenaro

Trestle Roadmap

1

Here is the roadmap for trestle for next few months. This list will be kept updated. - Update trestle to latest OSCAL version v1.1.1 - New feature requests have been...

vikas-agarwal76

## Issue description / feature objectives The csv-to-oscal-cd task has utilities for creating rule set properties that could be used outside of the context of CSV transformation. The objective of...

jpower432

Validate a field has at least 1 value assigned to it in governed header section

1

## Describe the bug While performing trestle validations to a governed header instance against its template, there is a validation outperforming the actual expected result of at least having 1...

AleJo2995

CRM/Leveraged SSP Support

3

## Issue description / feature objectives For SSPs that inherit controls from leveraged SSPs, support the ability to extract `component` UUIDs and `provided` and `responsibility` statements from a leveraged SSP...

jpower432

task csv-to-oscal-cd should not ignore $Check_Id and $Check-Description when value is: na

1

## Issue description / feature objectives When component type is validation, the $Check_Id and $Check_Description cells must be present. Sometimes there may be no check, for example data is provided...

degenaro

improve error message for task csv-to-oscal-cd when creating property with namespace that is missing or invalid

1

## Issue description / feature objectives before: `RuntimeError: Invalid property row: 3 name: Rule_Id value: workers-in-inventory-appear-in-latest-iks-scan ns: xyz remarks: rule_set_00` after: `RuntimeError: property for row: 3 ns: xyz is invalid`...

degenaro

## Issue description / feature objectives Different heading case should be tolerated. For example $$Control_Id_List, $$control_id_list, $$Control_id_list, etc. should all be allowed. ## Caveats / Assumptions N/A ## Completion Criteria...

degenaro

## Issue description / feature objectives If optional column $Component_Purpose is specified in csv it should map to the `purpose` field of OSCAL Component Definition. ## Caveats / Assumptions N/A...

degenaro