All Collections
Assets and Vulnerabilities
Asset Deduping in the Vulcan Platform
Asset Deduping in the Vulcan Platform

Learn all about Asset deduplication in the the Vulcan Platform

Updated over a week ago

What is Asset Deduping and how does it work?

One of the primary values the Vulcan Platform provides to Cyber Security Managers is the ability to have a single source of truth for all aggregated VM data in a single platform. The Vulcan Platform refines, aggregates, and deduplicates the ingested data to produce a consolidated assets view.

Asset Deduping in the Vulcan Platform is a mechanism that deduplicates assets ingested from multiple CMDB (Asset Inventories) and Scanners, providing a clean aggregation of the Cyber Security attack surface.

Vulcan achieves Asset Deduplication by crossing complex merge criteria and identifying duplications across the data ingested from the different sources.

Asset Type

Deduping Criteria


  • Cloud Instance ID

  • Mac Addresses

  • Hostnames

  • External IP


  • IP


URL/Address (Full)

Code Projects

Repository (Full)

Dockerfile and other Code Project File types: Path (Full)

Cloud Resources

  • Native ID

  • External ID

  • Provider ID (Full)


  • Digest

  • Repositor

  • Image_tag

Any combination of criteria is fully configurable with the assistance of the Vulcan Cyber Customer Success team.

Asset Deduping in the UI

In the Vulcan Platform, the Assets page presents a list of Unique Assets with an indication of the sources of each asset. "Source" is the connector/vendor from which the asset was retrieved and ingested into the Vulcan Platform. Across all asset types, the Vulcan Platform identifies the same asset from inventory and scanner sources, merges the asset details and data, and presents it only once on the assets list.

Expected behavior

Vulcan constantly improves the Asset Deduping mechanism to accurately refine the ingested Raw Assets data from multiple sources and produce a clean list of Unique Assets.

When improvements for better accuracy occur, the SPR could be affected. The change in SPR happens because the number of Unique Assets reduces accordingly. Nevertheless, this is an expected and wanted system behavior when deduplication is improved and accurized.

Did this answer your question?