Inventory item Additional Constraints

[brian-ruf]

Constraint Task

The following constraints are needed for inventory items:

• An inventory item MUST NOT reference a "system" component nor a "validation" component. (Note: "validation" components are referenced via a "validation" link)
• If an inventory item does not reference a component, it must have an "asset-type" property.
• In addition to the core allowed values for inventory-item/prop[@name='asset-type']/@value (which allows other values), FedRAMP should recognize:
  • software
  • hardware
  • network
  • infrastructure

Intended Outcome

For an inventory item that is not associated with a component, this provides context that would have been understood based on the associated component's @type property.

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

//inventory-item[not(./implemented-component)]

Purpose of the OSCAL Content

No response

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