Jennifer Power

OSCAL Import/Update Job fails with OSCAL 1.1.1 content

1

#### Description of problem: ##### Background As described in the comment on https://github.com/ComplianceAsCode/content/pull/11286, the `compliance-trestle` tool does not yet support OSCAL 1.1.1. OSCAL 1.1.1 support is on the `compliance-trestle` [roadmap](https://github.com/oscal-compass/compliance-trestle/issues/1480)....

feat: adds `x-trestle-add-props` to the YAML header in SSP markdown

1

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

Support adding generic properties during SSP authoring

1

## Issue description / feature objectives When a custom YAML header is used with ssp generate, it would be helpful to be able to specify extra properties at the implemented...

Rules are not updated in Component Definition and SSP markdown when control mapping changes are made

1

## Describe the bug In component definition and SSP markdown, the rule information is read-only. When markdown is initially generated from a component definition, the rule information is present. However,...

## Issue description / feature objectives Implementation part headers (e.g `### Implementation part a.`) appear in the SSP Markdown for components when rules are attached. There may be use cases...

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

## 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...

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...

## Issue description / feature objectives To support settings export (provided and responsibility) statements in Component Definition markdown files as properties. These properties are use to set export information in...

Add OSCAL Component Definitions as a release artifact

1

#### Share the context Utilities were added to the content repository to create OSCAL Component definitions from the compliance data stored in YAML. This allows user/devs to create OSCAL Component...