Summary:
Please consider enhancing the NVD import for Jira Assets to import full CPE data - including CPE strings, match criteria, version range fields, and additional CPE attributes - so that this information can be mapped and used within Assets.

Expectations:

This would allow use and correlate with the Assets inventory:

• Full CPE strings (e.g. cpe:2.3:...)
• CPE match criteria (criteria)
• Version range fields (e.g. versionStartIncluding, versionEndExcluding)
• Additional CPE attributes (part, update, edition, etc.)

And provide a way to access these attributes via:

• Additional selectors
• Hidden attributes
• Custom mapping configuration

Impact:

The absence of CPE significantly limits the usability of the integration for vulnerability management use cases, particularly regarding:

• precise product/version identification

• reliable matching between assets and vulnerabilities

• automation of impact analysis