The first step to great vulnerability risk remediation is knowing what assets are actually in your environment, and seeing as much relevant information about these assets as possible. To achieve this, after Vulcan ingests data from the different connectors in your environment, the platform sets about correlating and de-duplicating these assets. 

Because each environment is different and each tool, be it Vulnerability Assessment scanner, CMDB or Asset inventory, is configured differently, Vulcan allows you to configure how this de-duplication occurs.

If you would like to change your configuration, please contact Vulcan support or your Customer Success Manager. They will be happy to help you choose and implement the best configuration for your environment.

To decide on the best configuration for you environment, ask yourself the following question:

Vulcan supports the following identifiers:

An easy example would be an environment where each host is assigned a descriptive, unique name. In that case the unique identifier would be Hostname.
​
A more complex example would be an ephemeral environment where IP addresses and hostnames are frequently reused, where in that case a combination of both IP address and hostname would be a more suitable identifier.
In this example the following 2 assets would not be correlated, but result in 2 distinct assets:

And neither will these 2:

Only an exact match on 2 fields will correlate.

In some cases, where a single unique identifier or a unique combination can't be established for all assets, it will be necessary to correlate on one of multiple identifiers. This is supported with the same list of identifiers mentioned above.