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

Revision History #31

Closed
7 tasks
brian-ruf opened this issue Jan 22, 2020 · 1 comment
Closed
7 tasks

Revision History #31

brian-ruf opened this issue Jan 22, 2020 · 1 comment
Assignees

Comments

@brian-ruf
Copy link
Collaborator

Action Item

This is a ...

  • enhancement - Something could be better.

This relates to ...

  • the Modeling a FedRAMP SSP in OSCAL Guide (PDF)
  • the FedRAMP SSP OSCAL Template (JSON Format)
  • the FedRAMP SSP OSCAL Template (XML Format)

Describe the problem or enhancement

The OSCAL syntax currently lacks the ability to capture document revision history.
NIST recognizes this and intends to add revision history to the syntax under metadata, making it available for all OSCAL files.

Goals:

Once NIST solidifies the syntax for document revision history, the Guide to OSCAL-based FedRAMP System Security Plans must be updated, along with the FedRAMP SSP OSCAL Templates.

Dependencies:

usnistgov/OSCAL#587

Acceptance Criteria

  • NIST OSCAL Revision History Syntax and Documentation Published
  • All FedRAMP Documents Related to OSCAL Adoption 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 Comments

None.

@brian-ruf brian-ruf self-assigned this Jan 22, 2020
@brian-ruf
Copy link
Collaborator Author

The syntax was added by NIST in MR3, and is now reflected in the Guide to OSCAL-based FedRAMP Content released in PR #46

ohsh6o pushed a commit that referenced this issue Jun 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant