-
Notifications
You must be signed in to change notification settings - Fork 96
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
Labels
model: catalog
model: poam
model: profile
model: sap
model: sar
model: ssp
scope: constraints
scope: documentation
type: backlog item
For developer work that is not part of a user-facing epic or user story.
type: spike
Comments
aj-stein-gsa
added
model: poam
model: sap
model: sar
model: ssp
type: spike
scope: documentation
scope: constraints
type: backlog item
For developer work that is not part of a user-facing epic or user story.
model: profile
model: catalog
labels
Jan 3, 2025
aj-stein-gsa
added a commit
to aj-stein-gsa/fedramp-automation
that referenced
this issue
Jan 3, 2025
7 tasks
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
added a commit
to aj-stein-gsa/fedramp-automation
that referenced
this issue
Jan 3, 2025
7 tasks
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
Labels
model: catalog
model: poam
model: profile
model: sap
model: sar
model: ssp
scope: constraints
scope: documentation
type: backlog item
For developer work that is not part of a user-facing epic or user story.
type: spike
This is a ...
research - something needs to be investigated
This relates to ...
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
Dependencies
N/A
Acceptance Criteria
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.
The text was updated successfully, but these errors were encountered: