link
s with @rel
"proof-of-compliance"
constraint conflicting with @rel
"validation"
#2102
Labels
link
s with @rel
"proof-of-compliance"
constraint conflicting with @rel
"validation"
#2102
Describe the bug
There appear to be a series of constraints that overlap or conflict with one another in relation to validation and testing components. Different portions of documentation for the implementation layer discuss "proof of compliance" versus validation information for cryptographic components.
https://pages.nist.gov/OSCAL/learn/tutorials/implementation/validation-modeling/
https://pages.nist.gov/OSCAL/resources/concepts/layer/implementation/component-definition/
Given the structure of the example components in the former link and narrative in t, it would appear the
link[@rel="proof-of-compliance"
constraint is overlapping or conflicting withlink[@rel="validation"]
with an overly specific index lookup.https://github.com/usnistgov/OSCAL/blob/v1.1.3/src/metaschema/oscal_ssp_metaschema.xml#L618-L626
the last constraint ensures you cannot have a URL to a CMVP FIPS-140 record, but it must cross-reference to a sibling component of type validation by UUID with a URI reference. This constraint does not seem optimal, and it is advisable to remove it or model it with a different approach. The former is more expedient.
Who is the bug affecting
Processing OSCAL data with OSCAL-enabled software to cross-reference cryptographic validation records.
What is affected by this bug
Metaschema
How do we replicate this issue
link[@rel="proof-of-compliance"]
that is not a URI reference to a sibling component.oscal-cli
validations.See an example and discussion of the FedRAMP constraint modeling with oscal-cli validation failures in CI/CD via the links below.
GSA/fedramp-automation#1158 (review)
https://github.com/GSA/fedramp-automation/actions/runs/13288489054/job/37103011171?pr=1158
Expected behavior (i.e. solution)
Constraints permit URI data that is not specifically indexed to a
component[@type="validation"]
.Other comments
No response
Revisions
No response
The text was updated successfully, but these errors were encountered: