Inventory, diffs and reports
Inventory
Every scan and passive capture is stored in a SQLite database, by default %LOCALAPPDATA%\NetworkScope\inventory.sqlite on Windows; --db FILE selects another. SQLite is bundled into the executable. Scan settings are recorded per snapshot; notes are retained in JSON/CSV exports. Completed, stopped and partial runs are stored and marked as such.
network-scope history lists the saved snapshots as JSON.
Diff
network-scope-cli diff OLD NEW [--format lines|json|text] [--ignore K,K]
lines(default) is a JSON array of change lines.jsonis a structured report for CI and monitors: a summary withhighest_new_severity, changes tagged bykind, new/resolved/unconfirmed findings, ignored keys.textis plain lines.
A finding counts as resolved only if the new scan looked at its evidence again (host answered; TCP ports checked; UDP port probed in both); otherwise it is unconfirmed.
--ignore adds exact keys, globs (http.*.title) or suffixes (.server) to the always-ignored volatile keys *.days_left, *.clock_skew and *.boot_time.
Comparisons are meaningful only between completed scans with matching scope and settings. A timeout never proves that a device is offline.
Device history
devices --history MAC|IP [--format text|json] gives the timeline of one device across all saved scans and captures: first/last seen, addresses, MACs, names, the open ports of the latest completed scan, and events (first-seen, ip-changed, mac-changed, hostname-changed, port-opened, port-closed, udp-answering, udp-silent).
- Only sightings create events: a scan that does not mention the device produces no “not seen” event.
- Port events come only from completed active scans that checked the device’s ports with the same TCP port set; UDP is compared only for ports probed in both; SMB-only names are not compared.
Reports
network-scope-cli report ID [--baseline ID] --output report.html
One self-contained HTML file with summary cards, SVG charts, findings with NVD links, a findings-by-host table (highest severity, count per severity), a CPE column when any host has a CPE, changes since a baseline (“New findings”, “Resolved findings” and “Findings not re-checked”), a network map from traceroute data, a device table, per-host details and passive observations.
The report contains no scripts, sets a restrictive Content-Security-Policy, and HTML-escapes every scanned string. Captured metadata is treated as untrusted input.
export ID --format html produces the same report.
Exports
| Format | Content |
|---|---|
json | Full snapshot |
csv | One row per host. CSV cells that start with =, +, -, @, TAB or CR get a leading ' (CSV injection); purely numeric cells such as -1 are unchanged |
md | Markdown summary: scope, totals, findings, findings by host, devices, changes since --baseline |
jsonl | One JSON object per responding host (passive-only devices: use devices ID --format json) |
html | The HTML report |
nmap | nmap-compatible XML |
Exports carry the real scan time: the stored time for saved or reopened scans, the current time for live GUI results.
nmap XML interchange
export ID --format nmapwrites nmap XML (scanner="network-scope"), with product names in nmap spelling (Microsoft-IIS→Microsoft IIS httpd,Apache→Apache httpd, …;OpenSSH for Windows 8.1→ productOpenSSH, versionfor_Windows_8.1) andsvc.<port>.cpeas<cpe>elements.import FILE.xmlreads nmap XML (up to 256 MB) into the inventory as a normal scan and maps product names back, so the CVE rules fire on imports and Windows OpenSSH does not look like a vulnerable portable OpenSSH.<cpe>children becomesvc.<port>.cpe.- The
svc.<port>summary keeps the imported wording except for files written by Network Scope, so export → import is lossless. - Imports stored by 0.4 have the original spellings in
svc.<port>.product, so a diff against a new import shows those keys once. - Down hosts and non-open ports are not imported.
Network Scope only reads and writes the documented XML format; it is not a drop-in replacement for nmap and contains no nmap code or data.