Knowledge Base Article
How Does Tenable Vulnerability Management Identify an Asset as Unique
APPLIES TO
Tenable Vulnerability Management
OPERATING SYSTEM(S)
N/A
INFORMATION
Identification is the process of matching a set of attributes collected by a sensor (e.g. Nessus) to an existing asset. If Tenable Vulnerability Management is unable to find an existing asset that matches the incoming host, it is treated as a new asset and added to Tenable Vulnerability Management. The following section explains how Tenable Vulnerability Management matches hosts to assets.
DETAILS
Each identification request is based on a list of key-value pairs representing properties that have been observed/collected. Tenable Vulnerability Management uses a subset of these properties, called Identification Attributes (IA), in an attempt to determine whether an asset has been previously seen.
Our current list of IAs is below. These are ordered from authoritative to speculative, based on their ability to accurately link a host to an existing asset.
| Globally Authoritative Identifying Attributes | Network Scoped Identifying Attributes |
|
|
Internal IDs generated by cloud computing platforms (Amazon Elastic Cloud Compute, Microsoft Azure, Google Compute Engine, etc.) are 100% authoritative and unique. If the Tenable Vulnerability Management asset tracking system matches assets using one of these identifiers, the decision is guaranteed to be correct. Every asset should have at most one value for an identifier in this class.
Network Scoped Identifying Attributes are considered to be "scoped" to the network, meaning that for an asset to be considered as unique with the same MAC Address, NetBIOS Name, FQDN or IPv4 the asset will need to belong to the same Tenable Vulnerability Management defined Network as well. For more information, refer to the Tenable Vulnerability Management documentation on Networks.