SSP Back-Matter constraints development

[Rene2mt]

This is a ...

improvement - something could be better

This relates to ...

• the FedRAMP OSCAL Registry
• the FedRAMP OSCAL baselines
• the Guide to OSCAL-based FedRAMP Content
• the Guide to OSCAL-based FedRAMP System Security Plans (SSP)
• the Guide to OSCAL-based FedRAMP Security Assessment Plans (SAP)
• the Guide to OSCAL-based FedRAMP Security Assessment Results (SAR)
• the Guide to OSCAL-based FedRAMP Plan of Action and Milestones (POA&M)
• the FedRAMP SSP OSCAL Template (JSON or XML Format)
• the FedRAMP SAP OSCAL Template (JSON or XML Format)
• the FedRAMP SAR OSCAL Template (JSON or XML Format)
• the FedRAMP POA&M OSCAL Template (JSON or XML Format)

User Story

As a FedRAMP stakeholder, I need to use FedRAMP's external constraints so that I can make sure my OSCAL SSP back-matter content is valid in accordance with FedRAMP requirements.

Goals

The goal is to ensure the following FedRAMP validations are either developed as Metaschema-based constraints or dropped.

• resource-is-referenced
• attachment-type
• resource-base64-available-filename
• base64-has-content
• resource-base64-available-media-type
• has-allowed-media-type
• transport-type
• resource-has-base64-or-rlink
• attachment-type-is-valid
• resource-has-base64
• resource-has-base64-cardinality
• has-fedramp-logo
• has-user-guide
• has-rules-of-behavior
• has-information-system-contingency-plan
• has-configuration-management-plan
• has-incident-response-plan
• has-separation-of-duties-matrix
• has-policy-link
• has-policy-attachment-resource
• has-procedure-link
• has-procedure-attachment-resource
• hash-algorithm
• base64-has-filename

Dependencies

No response

Acceptance Criteria

• Metaschema-based external constraint is developed

• External constraint has PASS & FAIL unit tests

• Unit test content (e.g., valid and invalid SSP) is provided

• Constraints testing harness produces expected results when unit tests are run

• The constraint is documented and mentioned in the https://automate.fedramp.gov/documentation site (confirm by reviewing SSP sub-pages)

• 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.

Other information

No response

[aj-stein-gsa]

Per discussion today with ongoing work in #626 and upcoming work to follow on how we publish our progress against the public strategy doc, we will close this out issue to be replaced with the thematic objective and epic issue approach.

(For public stakeholders who follow these updates, more to follow.)