NacTrack
FRRequest access

CVE vulnerabilities

Published CVE that target the versions you run, ranked by exposure.

Manual contents

At a glance

  1. WhereSecurity, then CVE Vulnerabilities.
  2. AccessCompliance module and audit permission.
  3. DataThe collected versions, and an HTTPS path out to our service for the catalogue.
/compliance/vulnerabilities
The demo estate's CVE vulnerabilities.

What the screen shows

The tiles

Total findings, actively exploited (KEV), critical, high, affected devices, devices with KEV.

Exposure

A per device score weighing 40 per critical, 10 per high, 3 per medium and 1 per low, to rank the most exposed devices.

All findings

CVE with NVD link, severity, CVSS, EPSS, KEV, device, software, fixed in version and vendor advisory; search, severity filter, sort by CVSS or EPSS, KEV only.

What you can do

  1. 1

    Update the catalogue

    Refresh CVE sync starts synchronisation in the background; it also runs every night. The page shows the last attempt's result.

Limits and things to know

What leaves the appliance?

For each vendor, system and version combination, the device count. No device name, address or identifier.

A CVE is not a proven flaw

Matching is by version: the device is potentially affected, the configuration may not use the vulnerable feature.

Read next

How-to guide

How to tell whether a Cisco IOS XE version is affected by a CVE

Match a Cisco IOS XE release against Cisco advisories for every device at once, then check the configuration conditions the match cannot see.

Manual

EOL lifecycle

The end of sale and end of support dates of your models, the devices at risk within 180 days, and how the lifecycle catalogue updates.

Manual

Compliance

How to run rule evaluation, read the estate and per device scores, set a waiver on a check, and export the findings as PDF, XLSX or CSV.

Next chapter

EOL lifecycle

ContinueManual contents