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

Design approach for managing OSCAL and non-OSCAL attachments #1061

Open
1 of 2 tasks
aj-stein-gsa opened this issue Jan 3, 2025 · 0 comments · May be fixed by #1062
Open
1 of 2 tasks

Design approach for managing OSCAL and non-OSCAL attachments #1061

aj-stein-gsa opened this issue Jan 3, 2025 · 0 comments · May be fixed by #1062

Comments

@aj-stein-gsa
Copy link
Contributor

aj-stein-gsa commented Jan 3, 2025

This is a ...

research - something needs to be investigated

This relates to ...

  • the FedRAMP OSCAL Validations

User Story

As a FedRAMP developer, in order to properly handle a set of common use cases in FedRAMP in handling OSCAL and "pre-OSCAL" (i.e. non-OSCAL) attachments in a transitional state, I would like a documented pattern for handling such use cases documents.

Goals

  • Document a reusable pattern for multiple use cases of handling OSCAL and non-OSCAL content simultaneously

Dependencies

N/A

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.

Other information

Per standup, the need for an ADR discussing benefits, drawbacks, and best practice for such data modeling in OSCAL came up as part of #934.

@aj-stein-gsa aj-stein-gsa moved this from 🆕 New to 📋 Backlog in FedRAMP Automation Jan 3, 2025
@aj-stein-gsa aj-stein-gsa self-assigned this Jan 3, 2025
@aj-stein-gsa aj-stein-gsa moved this from 📋 Backlog to 🔖 Ready in FedRAMP Automation Jan 3, 2025
aj-stein-gsa added a commit to aj-stein-gsa/fedramp-automation that referenced this issue Jan 3, 2025
@aj-stein-gsa aj-stein-gsa linked a pull request Jan 3, 2025 that will close this issue
7 tasks
aj-stein-gsa added a commit to aj-stein-gsa/fedramp-automation that referenced this issue Jan 3, 2025
@aj-stein-gsa aj-stein-gsa moved this from 🔖 Ready to 🏗 In progress in FedRAMP Automation Jan 3, 2025
aj-stein-gsa added a commit to aj-stein-gsa/fedramp-automation that referenced this issue Jan 3, 2025
aj-stein-gsa added a commit to aj-stein-gsa/fedramp-automation that referenced this issue Jan 3, 2025
aj-stein-gsa added a commit to aj-stein-gsa/fedramp-automation that referenced this issue Jan 3, 2025
@aj-stein-gsa aj-stein-gsa linked a pull request Jan 3, 2025 that will close this issue
7 tasks
@aj-stein-gsa aj-stein-gsa moved this from 🏗 In progress to 👀 In review in FedRAMP Automation Jan 3, 2025
aj-stein added a commit to aj-stein-gsa/fedramp-automation that referenced this issue Jan 6, 2025
aj-stein added a commit to aj-stein-gsa/fedramp-automation that referenced this issue Jan 6, 2025
aj-stein added a commit to aj-stein-gsa/fedramp-automation that referenced this issue Jan 6, 2025
aj-stein added a commit to aj-stein-gsa/fedramp-automation that referenced this issue Jan 6, 2025
aj-stein added a commit to aj-stein-gsa/fedramp-automation that referenced this issue Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment