Open brian-ruf opened 4 years ago
When evaluating this, look at the parameter in Rev 5, AU-2, statement c, which states it's a subset of the supplied parameter value of statement a, with applied frequency of (or situation requiring) logging for each event type.
This issue requires building a relationship between parameters in the catalog model. It also requires some thought on how to address parameter pairs related to set-parameter in catalogs, profiles, and SSPs. This is a big undertaking to complete for 1.1. Moving this back to 1.2 for now.
User Story:
In controls such as CA-7(g) (NIST 800-53, Rev 4), there are two parameters intended to work together as a pairing; however, each can have multiple values. One parameter identifies who should receive a report, and the second identifies how often the party in the previous parameter should receive the report.
An OSCAL modeling limitation arises when the following situation is encountered (real-world example):
ISSO receives the report monthly
System owner receives the report quarterly
Parameter 1: ISSO, System-Owner
Parameter 2: Monthly, Quarterly
This would be better modeled as: Parameter Group 1:
This limitation impacts constraints as well as values. FedRAMP requires (parameter constraint) one reporting party (_parm_1) and frequency (_parm_2), while wishing to leave the option open for additional organizationally-defined reporting parties and frequencies. While a human could reasonably infer this from the current presentation, the current modeling does not allow a computer to parse the data consistently for this scenario.
Goals:
Expand the OSCAL modeling syntax to handle this scenario. NOTE: the Parameter Group notation above is just an example, and is not intended to prescribe a specific solution.
Dependencies:
This was originally reported as a bug via Issue #472. See that issue for additional comments/discussion.
Acceptance Criteria
{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.}