Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feedback]: Revision History elements in Metadata (Metaschemas) #568

Open
9 of 12 tasks
Telos-sa opened this issue Mar 14, 2024 · 0 comments
Open
9 of 12 tasks

[Feedback]: Revision History elements in Metadata (Metaschemas) #568

Telos-sa opened this issue Mar 14, 2024 · 0 comments

Comments

@Telos-sa
Copy link

This is a ...

question - need to understand something

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)
  • the FedRAMP OSCAL Validations

What is your feedback?

Screenshot 2024-03-14 at 10 34 40 AM

In creating the revisions history for the SSP schema, would it be appropriate to include revisions for all of the Appendices, or only include revision history for the SSP itself?

Because FedRAMP requires these appendices as part of the SSP, we thought it would be appropriate to include revisions for all of them in the schema.

Where, exactly?

OSCAL Metaschemas v1.1.2: https://pages.nist.gov/OSCAL-Reference/models/v1.1.2/system-security-plan/json-outline/

Other information

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🆕 New
Development

No branches or pull requests

1 participant