ZCR 1 — Scan & vulnerabilities

Import a scan, cross-reference the ZCR 1 inventory with the NVD / ICS-CERT databases, and generate threat scenarios that can be injected into ZCR 5.2.

Three tabs, in order

1. Scan & inventory import

Import a CSV file (generic inventory or a Claroty/Nozomi export, headers auto-detected) or an Nmap XML file, or fill in the inventory by hand. The columns that matter are Vendor/Manufacturer, Model and Firmware/Version: without them, no CVE matching is possible. A banner reports the number of incomplete pieces of equipment.

Then Analyze all CVEs.

2. CVE analysis

One row per CVE found: ID, CVSS score, matching canonical vulnerability, description and publication date. Filters by level: Critical (≥ 9), High (≥ 7), Medium (≥ 4), Low.

The Canonical vuln. column links the CVE to the internal vulnerability reference — this link is what then makes it possible to generate an exploitable scenario, rather than a plain list of CVEs.

3. Suggested scenarios

Generate suggested scenarios button from the CVE tab. Select the relevant scenarios, then Inject into ZCR5.2. Rows already injected are marked ✓ Injected.

AI suggestion

The Suggest CVEs button proposes, for a given piece of equipment, plausible vulnerabilities based on its vendor and model.

WARNING

An AI suggestion is not a scan result: it must be checked against the NVD database before being carried into an analysis. The automatic matching remains the reference source.

Prerequisite

This page finds nothing until the inventory on the SUC scope page contains equipment of type Hardware.