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.

Sign up for GitHub

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

Jump to bottom

Detail requirements for OSCAL tools #66

Open
aj-stein-gsa opened this issue Sep 26, 2024 · 1 comment
Open

Detail requirements for OSCAL tools #66

aj-stein-gsa opened this issue Sep 26, 2024 · 1 comment
Labels
documentation Improvements or additions to documentation

Comments

@aj-stein-gsa
Copy link
Contributor

As an acquisitions officer, in an agency or cloud service provider part of the FedRAMP ecosystem, I would like to know what OSCAL capabilities my software should or must support depending on the business/mission case for my service or the business/mission I support for my own downstream customers.
@aj-stein-gsa aj-stein-gsa added the documentation Improvements or additions to documentation label Sep 26, 2024
@aj-stein-gsa aj-stein-gsa moved this from 🆕 New to 📋 Backlog in FedRAMP Automation Sep 26, 2024
@aj-stein-gsa
Copy link
Contributor Author

I need to do some pre-work for the requirements on this work with @david-waltermire and @audreamichellewhite before we can move forward and publish how GRC requirements pertain to OSCAL technical requirements so acquisition officers can understand.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
documentation Improvements or additions to documentation
Projects
FedRAMP Automation
Status: 📋 Backlog
Milestone
No milestone
Development

No branches or pull requests
1 participant
@aj-stein-gsa