SSP Completeness Checks: 8 Illustrated Architecture and Narratives

[brian-ruf]

This is a ...

fix - something needs to be different

This relates to ...

• the Guide to OSCAL-based FedRAMP System Security Plans (SSP)
• the FedRAMP SSP OSCAL Template (JSON or XML Format)
• the FedRAMP OSCAL Validations

User Story

As a consumer of FedRAMP automated completeness checks I want the following OSCAL-based SSP items to be automatically verified for completeness by metaschema constraints:

• At least one authorization boundary diagram
• At least one network diagram
• At least one data flow diagram

Goals

SSP Completeness checks are defined, tested and documented

Dependencies

No response

Acceptance Criteria

• [ ] All FedRAMP Documents Related to OSCAL Adoption (https://github.com/GSA/fedramp-automation) 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.
• [ ] all constraints associated with the review task have been converted/created
• [ ] automate.fedramp.gov content has been updated accordingly
• [ ] the metaschema help prop has an appropriate link to the constraint
• [ ] the template has an content that models the desired OSCAL presentation
• [ ] the constraint runs against the example template
• [ ] known-bad content has been created
• [ ] the constraint appropriately flags the known-bad content as invalid

Other information

No response

[brian-ruf]

Check #881 and #882 for alignment with this issue.

[aj-stein-gsa]

Check #881 and #882 for alignment with this issue.

Sorry when I spoke earlier I didn't see what epic you were talking about. I mean those in relation to the PPSM. I would like to review those in the context of #806.

I misunderstood your question. In the context of this diagrams epic, we need to talk about #864 and previous touchups from before that (but you will see in that PR).