Add system-characteristics 'information-type' constraints

[Gabeblis]

Committer Notes

{Please provide a description of what this PR accomplishes. Be sure to reference any issues addressed. If the PR is a work-in-progress submitted for early review, please submit the PR as a draft PR using the "Draft pull request" dropdown.}

Description

Added system-characteristics 'information-type' constraints and tests for each of the constraints. These should be added as they are part of the effort write all of the constraints from the constraint tracker.

Changes

• Added constraints information-type-has-confidentiality-impact, information-type-has-integrity-impact, information-type-has-availability-impact to fedramp-external-constraints.xml.
• Added pass and fail yaml tests for all of the above constraints.
• Edited ssp-all-INVALID.xml to ensure all constraints fail correctly.

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.

[aj-stein-gsa]

Does this also have overlap with #610? Seems so.

[Gabeblis]

Does this also have overlap with #610? Seems so.

These constraints should all exist. The only overlap is the issue that we discussed yesterday with Dave regarding allowed-values constraints and expect constraints sharing the same ssp-all-INVALID file.

[aj-stein-gsa]

Does this also have overlap with #610? Seems so.

These constraints should all exist. The only overlap is the issue that we discussed yesterday with Dave regarding allowed-values constraints and expect constraints sharing the same ssp-all-INVALID file.

OK disregard, I can see what you mean. I am still going to need to wrap up some docs pertaining to the doc gaps for this and #610 tracked in GSA/automate.fedramp.gov#55. Sorry for the delayed reply.