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

POAM JSON Outline: Risk > Remediation or Response? #1766

Closed
rachkim00 opened this issue Apr 20, 2023 · 2 comments
Closed

POAM JSON Outline: Risk > Remediation or Response? #1766

rachkim00 opened this issue Apr 20, 2023 · 2 comments

Comments

@rachkim00
Copy link

Describe the bug

In the POAM JSON Outline, under 'Risk', instead of 'Response', it uses the term 'Remediations.' This section is the only part where it mentions 'Remediations' and it is confusing for the users whether remediation is another data type or the same as the response referred in 'Risk-log' > 'Related-response'.

XML outline only uses terminology 'response'.

Unless it was intended to have POAM JSON to have different taxonomy by having separate 'Remediation' and 'Response', I suggest to update the 'Remediation' with 'Response'.

POAM_JSON_Outline1

Who is the bug affecting

CSPs creating/implementing OSCAL POAM process.

What is affected by this bug

OSCAL Content, Metaschema, Modeling

How do we replicate this issue

  1. Go to OSCAL Outline > JSON
  2. Find Risk Section and check Remediation
  3. Go to OSCAL Outline > XML
  4. Compare with JSON outline

Expected behavior (i.e. solution)

Term remediation is updated with 'response' in JSON outline

Other comments

No response

Revisions

No response

@rachkim00 rachkim00 added the bug label Apr 20, 2023
@aj-stein-nist
Copy link
Contributor

Hi @rachkim00, thanks for submitting this bug report. This appears to be a potential duplicate of #1618. We will discuss in the team's weekly issue triage and backlog refinement and update with notes in a follow-on comment.

@aj-stein-nist
Copy link
Contributor

Please be sure to follow updates on #1618 for further updates on whether a change proposed here will be performed in the near-term or long-term. Thanks for this report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants