Inventory - Baseline Configuration Name

[Rene2mt]

Constraint Task

Consistent with issue #813, this work focuses on ensuring the inventory items provides sufficient reference to the appropriate baseline configuration (e.g., STIG or CIS benchmark).

Intended Outcome

• component of type "software", "hardware", or "service" and/or inventory-item have an "attachment" link to the appropriate baseline
• "Internal" components, and components of type "software" or "hardware" have an "attachment" link to the appropriate baseline

Syntax Type

This is optional core OSCAL syntax.

Allowed Values

There are no relevant allowed values.

Metapath(s) to Content

context="//inventory-item"

target=". | //component[@uuid=./implemented-component/@component-uuid]"

count(//resource[@uuid=//(component[@type=('software', 'hardware', 'service')] | inventory-item)/link[@rel='baseline']/substring-after(@href, '#')]) >= 1

-----

context="//component[(@type='service' and ./prop[@name='implementation-point' and @value='internal']) or @type=('hardware', 'software')]"

target="."

count(//resource[@uuid=//(component[@type=('software', 'hardware', 'service')] | inventory-item)/link[@rel='baseline']/substring-after(@href, '#')]) >= 1

Purpose of the OSCAL Content

These constraints ensure there is clear information about what baseline applies to each component / inventory item.

Dependencies

No response

Acceptance Criteria

• All OSCAL adoption content affected by the change in this issue have been updated in accordance with the Documentation Standards.
  • Explanation is present and accurate
  • sample content is present and accurate
  • Metapath is present, accurate, and does not throw a syntax exception using oscal-cli metaschema metapath eval -e "expression".
• All constraints associated with the review task have been created
• The appropriate example OSCAL file is updated with content that demonstrates the FedRAMP-compliant OSCAL presentation.
• The constraint conforms to the FedRAMP Constraint Style Guide.
  • All automated and manual review items that identify non-conformance are addressed; or technical leads (David Waltermire; AJ Stein) have approved the PR and “override” the style guide requirement.
• Known good test content is created for unit testing.
• Known bad test content is created for unit testing.
• Unit testing is configured to run both known good and known bad test content examples.
• Passing and failing unit tests, and corresponding test vectors in the form of known valid and invalid OSCAL test files, are created or updated for each constraint.
• A Pull Request (PR) is submitted that fully addresses the goals section of the User Story in the issue.
• This issue is referenced in the PR.

Other information

No response

[brian-ruf]

Per today's conversation, the //component/link that identifies the baseline will use rel='baseline' instead of rel='attachment'

[aj-stein-gsa]

And @kyhu65867 I will help you with the back-matter/resource content and how it all comes together today.