Add Control Origination Allowed Values

[Gabeblis]

Committer Notes

Purpose

This PR aims to add a Control Origination Allowed Values constraint that verifies that the control origination of an implemented requirement aligns with one the FedRAMP designated allowed values.

Changes

• Added frr306 and frr307 constraints.
• Added associated negative test data.
• Added associated pass/fail YAML files.

All Submissions:

• Have you selected the correct base branch per Contributing guidance?
• Have you set "Allow edits and access to secrets by maintainers"?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• Have you squashed any non-relevant commits and commit messages? [instructions]
• Have you added an explanation of what your changes do and why you'd like us to include them?
• If applicable, have all FedRAMP Documents Related to OSCAL Adoption affected by the changes in this issue have been updated.?
• If applicable, does this PR reference the issue it addresses and explain how it addresses the issue?

By submitting a pull request, you are agreeing to provide this contribution under the CC0 1.0 Universal public domain dedication.

[Rene2mt]

@Gabeblis, requesting monior change to align constraint ID. Otherwise, all looks good.

[aj-stein-gsa]

I owe you improved acceptance criteria. Apologies in advance, but the changes will be minor. 🤦

[aj-stein-gsa]

I am sorry to do this but please check the much delayed update to the AC and constraint requirements I corrected a few minutes ago. Please also observe there can be multiple occurrences of the prop.

#868 (comment)

Again, thanks again for humoring the last few days of blatant errors in issue requirements. Let me know if you have additional questions. The error is completely on my side, this work was very solid, if only someone did requirements correctly. 😆

stale

[Rene2mt]

Looks good!!