Skip to content
Alle documentatie
Compliance

CPE-koppelingen beheren

Manage CPE Mappings

CPE Mapping is the admin workflow for matching application records to NVD CPE dictionary entries so vulnerability scanning can find relevant CVEs. The page separates pending review, confirmed mappings, and explanatory settings. Auto-mapping can process unmatched applications, proposes ranked candidates with confidence labels, and admins confirm or move mappings back to pending review.

Voor wie

Beheerders, medewerkers en IT-teams die ITLedger gebruiken voor dienstverlening, assets, compliance en rapportages.

Taken

Kies je taak. De volledige werkwijze, voorwaarden en aandachtspunten staan hieronder in het Engels.

Manage CPE Mappings

CPE Mapping is the admin workflow for matching application records to NVD CPE dictionary entries so vulnerability scanning can find relevant CVEs. The page separates pending review, confirmed mappings, and explanatory settings. Auto-mapping can process unmatched applications, proposes ranked candidates with confidence labels, and admins confirm or move mappings back to pending review.

Who can do this: Tenant administrator

Before you start

  • Use an account with access to the stated page and permission for the chosen action.

Safeguards

  • The current scan scope shown in settings is Applications; hardware, operating systems, databases, and infrastructure entities are not supported for auto-mapping in that UI.
  • Auto-mapping runs every 4 hours according to the settings text, and the Pending Review tab can trigger Run Now manually.
  • A high-confidence candidate is still not proof; admins should verify vendor, product, version, and context before confirming.
  • Confirmed mappings can be moved back to pending review if later evidence shows the CPE is wrong or invalid.
  • NVD attribution is shown in the UI because the product uses NVD data but is not endorsed or certified by NVD.
  1. Open Configuration → CPE Mappings.
  2. Start in Pending Review to see application products that need human confirmation.
  3. Use Run Now if new unmatched applications should be auto-mapped immediately.
  4. Review the recommended CPE candidate and expand alternatives when confidence or version context is uncertain.
  5. Confirm the selected candidate only after checking vendor, product, and version fit.
  6. Use the Confirmed tab to inspect scan status, CVE counts, urgency, affected asset count, and stale/error states.
  7. Move a confirmed mapping back to pending if it needs correction.
  8. Use Settings to explain scan scope and confidence levels.

Expected outcome: The user has reviewed the result of manage cpe mappings in the application.

Aanbevolen werkwijze

  • Wijs eigenaren toe voor bewijs en herstelwerk.
  • Controleer verouderde informatie vóór gebruik bij een audit.

Gerelateerde handleidingen

Lees verder in Compliance

Bewijs, NIS2, risico’s, gegevensprofielen en kwetsbaarheden.