Michaela Iorga

@Compton-NIST The SSP model provides : `control-implementation.implemented-requirement.by-component.export` and `control-implementation.implemented-requirement.statement.by-component.export` where information would go at the component level, but there is no equivalent assembly providing this information in a `component definition`...

@aj-stein-nist @Compton-NIST and @wendellpiez - How do we want to allow the community or other team members provide feedback in an easy way (not just leave comment)? Should we keep...

Is the following interpretation accurate, considering the following assumptions: 1) I am creating a new profile derived from FedRAMP's moderate profile, and I want to have an easy way to...

### 10/05/2023 analysis ### OSCAL allows local definitions for the components' type so, if a 'connection' component is necessary, that can be locally defined. With that said, the question is...

@Telos-sa - did you ask FedRAMP for clarification since the Crypto module is called using its API? Is there another proposed approach?

This issue was opened here for community's visibility. Issue https://github.com/usnistgov/oscal-content/issues/237 is addressing it.

issue addressed

@brian-easyd - Will you be willing to drive the [OSCAL-DEFINE](https://github.com/usnistgov/OSCAL-DEFINE) spirals researching this issue? Community's input is crucial here.

This issue is probably safe to close after a sanity check.

Important comments are available under the original issue [OSCAL-Reference/issue#6](https://github.com/usnistgov/OSCAL-Reference/issues/6) Moving the earlier-assigned devs here.