Skip to content
This repository has been archived by the owner on Dec 12, 2023. It is now read-only.

Check PIA and PTA #100

Closed
7 tasks done
ohsh6o opened this issue Jun 16, 2021 · 0 comments · Fixed by #108
Closed
7 tasks done

Check PIA and PTA #100

ohsh6o opened this issue Jun 16, 2021 · 0 comments · Fixed by #108
Assignees
Labels
story task it's a task
Milestone

Comments

@ohsh6o
Copy link

ohsh6o commented Jun 16, 2021

Extended Description

As a FedRAMP reviewer, to ensure proper completion of necessary supporting artifacts for a complete SSP and overall FedRAMP package, I want validations to check and indicate errors when the Privacy Impact Assessment and/or Privacy Threshold Analysis is not properly defined.

(Part of #98)

Preconditions

  • None at this time

Acceptance Critera

  • A clear, explanatory validation message with an associated test indicating the Privacy Impact Assessment and/or Privacy Threshold Analysis is or is not properly defined in OSCAL.
  • Indication that a PIA and PTA was checked for, but not required given other OSCAL SSP data that negates required use of a PIA and PTA for the information system.

Definition of Done

  • Unit test coverage of our code > 90% (from QASP) this may be fuzzy and hard to prove
  • Code quality checks passed - Enable html tidy with XML code standards as part of the build (from QASP)
  • Code reviewed - Code reviewed by at least one other team members (or developed by a pair)
  • Source code merged - Code that’s demoed must be in source control and merged
  • Code refactored for clarity - Code must be clean, self-documenting
@ohsh6o ohsh6o added story task it's a task labels Jun 16, 2021
@ohsh6o ohsh6o added this to the Sprint 4 milestone Jun 16, 2021
@GaryGapinski GaryGapinski self-assigned this Jun 18, 2021
@GaryGapinski GaryGapinski linked a pull request Jun 25, 2021 that will close this issue
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
story task it's a task
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants