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

Approval Status and Date for Specific Portions of an OSCAL Document Instance #1034

Closed
3 tasks
ohsh6o opened this issue Oct 4, 2021 · 1 comment
Closed
3 tasks

Comments

@ohsh6o
Copy link
Contributor

ohsh6o commented Oct 4, 2021

User Story:

As an OSCAL tool developer, in order to allow my tools to show that different stakeholders from the organization authoring the information system's security documentation (SSP, SAP, SAR, and/or POA&M) had approved specific portions of a document, I want to add metadata to show the responsible parties for approval and dates of these approvals for these specific portions.

Goals:

Per discussion during the last week's model meeting, we will want to take the work of #1033 and then make the approver and date tracking to be made more specific to not the overall document instance, but specific portions of the document (that was presumably updated).

See GSA/fedramp-automation#162 for more context.

Dependencies:

Completion of #1033 prior to starting this work.

Acceptance Criteria

  • All OSCAL website and readme documentation affected by the changes in this issue have been updated. Changes to the OSCAL website can be made in the docs/content directory of your branch.
  • A Pull Request (PR) is submitted that fully addresses the goals of this User Story. This issue is referenced in the PR.
  • The CI-CD build process runs without any reported errors on the PR. This can be confirmed by reviewing that all checks have passed in the PR.

{The items above are general acceptance criteria for all User Stories. Please describe anything else that must be completed for this issue to be considered resolved.}

@david-waltermire
Copy link
Contributor

Talked with @ohsh6o / @aj-stein-nist. he is good with closing this issue.

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