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

assessment-assets missing in POAM's local-definitions #1291

Closed
CyberDaedalus00 opened this issue May 27, 2022 · 1 comment · Fixed by #1417
Closed

assessment-assets missing in POAM's local-definitions #1291

CyberDaedalus00 opened this issue May 27, 2022 · 1 comment · Fixed by #1417
Assignees
Labels
Milestone

Comments

@CyberDaedalus00
Copy link

Describe the bug

In circumstances where a POAM is provided without a System Security Plan (SSP), for circumstances where no OSCAL-based SSP exists, or is not delivered with the POA&M, there is no means to specify the definitions of components and assessment-platforms used in the assessment and referenced by an origin's actor as the source of the information. As a result there is no means to resolve/lookup details about the referenced actor.

{A clear and concise description of what the bug is.}

Who is the bug affecting?

What is affected by this bug?

{Describe the impact the bug is having.}

When does this occur?

{Describe the conditions under which the bug is occurring.}

How do we replicate the issue?

{What are the steps to reproduce the behavior?

  1. Do this...
  2. Then this...
  3. See error

If applicable, add screenshots to help explain your problem.}

Expected behavior (i.e. solution)

The local-definition of the POAM should be revised to contain an assessment-assets field that would enable definitions for both components or assessment-platforms used in the assessment to be defined so that references can be resolved.

Other Comments

{Add any other context about the problem here.}

@david-waltermire
Copy link
Contributor

To correct this assessment-assets needs to be added to local-definitions in the POAM model to allow for the assessment tooling to be cross-referenced. This should have the same structure as the local-definitions/assessment-assets allowed in the OSCAL assessment-results model.

@david-waltermire david-waltermire added this to the OSCAL 1.1.0 milestone May 31, 2022
@david-waltermire david-waltermire self-assigned this May 31, 2022
Compton-US added a commit to Compton-US/OSCAL that referenced this issue Aug 17, 2022
@david-waltermire david-waltermire linked a pull request Aug 21, 2022 that will close this issue
aj-stein-nist pushed a commit to aj-stein-nist/OSCAL-forked that referenced this issue Oct 6, 2022
aj-stein-nist pushed a commit to aj-stein-nist/OSCAL-forked that referenced this issue Jan 10, 2023
aj-stein-nist pushed a commit to aj-stein-nist/OSCAL-forked that referenced this issue Feb 6, 2023
aj-stein-nist pushed a commit to aj-stein-nist/OSCAL-forked that referenced this issue Jun 29, 2023
aj-stein-nist pushed a commit to aj-stein-nist/OSCAL-forked that referenced this issue Jul 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants