Paste or upload your asset→CVE inventory — from Cortex Xpanse, Tenable, Qualys, a Nessus export, or a plain CSV — and Omenwave overlays its chaining model on the CVEs you actually have to answer one question: which asset should you remediate first to sever the most modelled chains? This is remediation prioritisation, not exploitation guidance.
Your inventory is parsed in your browser and sent once to compute the overlay. Nothing is stored on the server — no accounts, no saved inventories.
{assets:[{id,cves}]}, a list of objects with an asset-name field (id/host/hostname/name/ip/asset) and a CVE-list field (cves/cve/vulnerabilities/findings), a {"asset":[cves]} map, or CSV with an asset column and a CVE column. CVE ids are extracted wherever they appear.The single CVEs that sit on the most modelled pathways toward full compromise across your estate — the highest-leverage fixes if you patch by CVE rather than by asset.