Hi,
There is a "hierarchy" to vulnerabilities.
At the top of the hierarchy is the CWE. The authoritative source for CWE is mitre.org, so we grab it from the source.
Then comes the CVE (which points to a CWE) and the authoritative source again is mitre.org, so we grab it from the source.
Then comes the Tenable Plugins (Points to the CVE). Tenable custom vulnerability definitions. So we grab that next.
Tenable Asset is a way to pull what Tenable knows about your environment. More about this in a minute.
For whatever reason, this is the way the Tenable API works: Pull the Fix vulnerabilities, then pull the open vulnerabilities. More about this in a minute.
The backfill job is complicated to explain, but the way Tenable works makes this necessary.
Tenable scan credentials are necessary if you wish to conduct rescans via ServiceNow.
A Vulnerable Item is made up of a Vulnerability + a Configuration Item (i.e. an Asset).
Pulling in the Assets matches or creates a Configuration Item
The incoming vulnerabilities are combined with the CI's to creat the VIT.
The Vulnerability part of the VIT points to 1 or more CVE, which points to one or more CWE.
