Inventory - Unique Asset Identifier

[Rene2mt]

Constraint Task

Consistent with parent issue #813, this constraint work focuses on ensuring that all inventory items and software images have a unique asset ID.

Intended Outcome

• All inventory items and software images have an asset-id prop
• All asset-id props on component and inventory-item have unique values

Syntax Type

This is a mix of required, optional, and/or extended syntax.

Allowed Values

There are no relevant allowed values.

Metapath(s) to Content

context="//( component[@type='software' and ./prop[@name='asset-type' and @value='image']] | inventory-item)"

target="."

count(./prop[@name='asset-id']) = 1

enforce uniqueness

Purpose of the OSCAL Content

No response

Dependencies

This constraint helps assessors and reviewers confirm that every inventory item and software image is accounted for in the integrated inventory workbook and has the required unique asset identifier.

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