As an ASAP Developer, in order to provide FedRAMP reviewers easy confirmation that all in-scope objectives have findings, I want to compare the in-scope objectives from the SSP to the findings in the SAR.
Acceptance Criteria
[x] All Schematron assertion messages are declarative statements which affirm the positive test outcome.
[x] All Schematron assertion diagnostic messages are declarative statements which explain the negative test outcome.
[x] The Schematron code has no assertion failures when validated using src/validations/styleguides/sch.sch using the basic phase.
[x] XSpec unit tests for positive and negative Schematron assertion outcomes accompany all Schematron assertions (where feasible).
[x] Ensure that finding elements have child elements target with @id-ref that matches an implemented-control/@control-id value in the SSP.
[x] Ensure that target elements with type of 'objective-id' have property of 'implementation-status'
[x] Ensure that target elements with type of 'objective-id' and property of 'implementation-status' have proper value as described in the fedramp_values document.
[x] Ensure that target elements with type of 'objective-id' have a status element
[x] Ensure that target elements with type of 'objective-id' and a status element have the value 'satisfied' or 'other-than-satisfied'
[x] Ensure that finding/origin/actor elements have a matching uuid value in either the SAP or SAR party assemblies.
Definition of Done
[x] Acceptance criteria met
[x] Unit test coverage of our code > 95%
[x] Automated code quality checks passed
[x] Security reviewed and reported
[x] Reviewed against plain language guidelines
[x] Code must be self-documenting
[x] No local tech debt
[x] Load/performance tests passed – needs to be created/automated
[x] Documentation updated
[x] Architectural Decision Record completed as necessary for significant design choices
Extended Description
Acceptance Criteria
src/validations/styleguides/sch.sch
using thebasic
phase.Definition of Done