Cross-Check for OSCAL and FedRAMP Allowed Values and Constraints

[ohsh6o]

Action Item

This is a ...

• investigation - Something needs to be investigated further.

This relates to ...

• General/Overall
• Other

NOTE: For issues related to the OSCAL syntax itself, please create or add to an issue in the NIST OSCAL Repository.

Describe the problem or enhancement

{A clear and concise description of the problem or enhancement.}

Goals:

{A clear and concise description of what you want to happen. This should be outcome focused. Include concise description of any alternative solutions or features you've considered. Feel free to include screenshots or examples about the feature request here.}

Dependencies:

{Describe any previous issues or related work that must be completed to start or complete this issue.}

Acceptance Criteria

• All FedRAMP Documents Related to OSCAL Adoption affected by the changes in this issue have been updated.
• A Pull Request (PR) is submitted that fully addresses the goals of this User Story. This issue is referenced in the PR.

{The items above are general acceptance criteria for all User Stories. Please describe anything else that must be completed for this issue to be considered resolved.}

Other Comments

{Add any other context about the problem here.}

[ohsh6o]

More details to come but per our conversation this afternoon, @david-waltermire-nist and @wendellpiez.

[ohsh6o]

Actively picking this work back up again and updating with review of changes in usnistgov/OSCAL#1012.

[aj-stein-nist]

@volpet2014 this is the story work I was discussing during our touch-base today.

FYI, we also might want to unassign my old account from this. :-)

[aj-stein-nist]

@volpet2014, as discussed let's start planning some time with @Rene2mt. Contact the 10x team (I assume @GaryGapinski but I assume he'd know best) about getting the validation team to work with us on this. Will take some time and probably not a "solution it out in one meeting" kid of task, so we will need to plan and work through it.

[volpet2014]

Consulted with NIST on this. We are planning a pairing session with NIST, PMO, Reviewers and tech leads to discuss this in the near future.

[volpet2014]

Need to check with @Rene2mt with regards to resolving inconsistencies and differences and reflect in Guides documentation also.

[aj-stein-gsa]

As we have begun to build out the new external constraints approach, we have started to make this cross-check review part of the normal development and review process with the advent of the oscal-external-constraints, the style guide, and the intent to upstream them. It is a more continual process and will not be a static epic with sub-tasks. My initial issue and updated recommendation as a NIST advisor were oft the mark, so now I am closing this one out as "not planned."

We have a better way to do this continuously.