-
Notifications
You must be signed in to change notification settings - Fork 88
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
Review of FedRAMP OSCAL Extensions and Values #564
Comments
Related to issue #587 |
@brian-ruf and @Rene2mt is it possible we discuss this in the Thursday constraint meeting to her team viewpoints and move ahead with this? |
@aj-stein-gsa there is no constraints meeting this Thursday due to stand-down day. I'm also on a plan a good chunk of tomorrow. Happy to discuss Friday. |
🤦 I forgot today is Wednesday .... 😆 Thanks for the update! |
@aj-stein-gsa and @brian-ruf lets discuss Friday |
This is a ...
research - something needs to be investigated
This relates to ...
User Story
As a FedRAMP OSCAL content generator, I need clear and consistent guidance on when to uses specialized FedRAMP OSCAL extensions versus when to use generalized core OSCAL props and values, and a clear understanding of the constraints around all extensions.
Goals
By reviewing each extension and determining the required approach, this will result in clear requirements that when implemented will:
Dependencies
No response
Acceptance Criteria
Other information
This issue is focused on conducting the analysis so that the requirements are clarified. Subsequent issue(s) will implement the necessary updates.
The text was updated successfully, but these errors were encountered: