SSP Completeness Checks: Title Page and Section 3 System Information

[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:

• CSP Name
• CSO Name and Short Name
• FedRAMP Package ID
• FIPS PUB 199 Level
• Service Model
• Deployment Model
• Operational Date
• Digital Identity level (DIL)
• Authorization Path
• General System Description
• Title
• Publication Date
• Version
• Revisions
• FedRAMP Version Prop (OSCAL-specific)
• Document sensitivity

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

Task List

• [ ] #669
• [ ] #689