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

Generate Assessment Plan from SSP #811

Open
1 task
meganwolf0 opened this issue Nov 20, 2024 · 2 comments
Open
1 task

Generate Assessment Plan from SSP #811

meganwolf0 opened this issue Nov 20, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@meganwolf0
Copy link
Collaborator

meganwolf0 commented Nov 20, 2024

Is your feature request related to a problem? Please describe.

According to understood OSCAL model process flows, the SSP is the precursor model to the Assessment Plan. This issue is aligned with determining how to generate an Assessment Plan from the SSP. This potentially includes executing Lula Validations to determine contents of the Assessment Plan (and downstream Assessment Results?)

Describe the solution you'd like

  • Given an SSP
  • When lula generate -f <ssp.yaml> <flags>
  • Then an Assessment Plan is created

Describe alternatives you've considered

There may be another OSCAL model flow, this is possibly unclear? This issue conflicts with #518 where an Assessment Plan is documented as an output of a Component Definition. Which is true? Which do we want to go with if both could be true?

Additional context

Outstanding Questions - do we need to run lula validate under the hood as part of this process? Relates to #518, #514.

Additional point of discussion - How many commands do we want to have/users need to memorize to create OSCAL docs? (should we create an assess command or keep as generate?)

Expected Deliverable

  • Discussion and fully scoped issue set on the details of the implementation
@meganwolf0 meganwolf0 added the enhancement New feature or request label Nov 20, 2024
@github-actions github-actions bot added the triage Awaiting triage from the team label Nov 20, 2024
@meganwolf0 meganwolf0 removed the triage Awaiting triage from the team label Nov 20, 2024
@brandtkeller
Copy link
Member

Likely shares an overlap with #514 and #518.

@meganwolf0
Copy link
Collaborator Author

Likely shares an overlap with #514 and #518.

Agree, called out #518 in the description but #514 is probably there as well - seems like the deliverable on this would either scope or close those issues as they relate to the specific assess command (#514 - do we even want to create another command?) and the inputs as a component-definition (#518 - should that be the input or should it be an SSP?)

@brandtkeller brandtkeller moved this from 🆕 New to 🔖 Ready in Lula and Friends Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: 🔖 Ready
Development

No branches or pull requests

2 participants