Asset identity
A single record per asset, regardless of the source.
The same server appears in the EDR under a hostname, in the scanner as an IP address, in the CMDB under an asset tag, and in the cloud console as an instance ID. CAASM recognizes that these records describe the same asset and consolidates all four, without merging records that must remain separate.
Example
Four records, one asset.
A cloud web server published through a CDN typically appears in four tools, each holding part of the information. CAASM correlates these records through their shared identifiers and presents a single asset, with all four sources indicated.
As a result, the asset count reflects reality, the vulnerabilities reported by the scanner are associated with the asset protected by the EDR, and the owner recorded in the CMDB applies to the consolidated record.
How the decision is made
Identifiers with different levels of confidence.
Merging records by device name is a common practice and prone to error, because names repeat, change, and get reused. CAASM classifies each identifier by confidence level and unifies records only when there is sufficient evidence.
Sufficient to unify
Identifiers assigned by the system itself that do not repeat, such as the cloud instance ID, the EDR agent ID, and the serial number.
Requires additional evidence
MAC address and fully qualified domain name. They contribute to identification, but the records are unified only when another piece of evidence also matches.
Indicative only
Short hostnames and IP addresses change over time and repeat across networks. CAASM treats them as indications, never as proof.
Blocking rules
Protection against incorrect merges.
Merging two distinct assets is more serious than keeping a duplicate record, because one device disappears from the inventory along with its coverage gaps. For this reason, specific rules prevent a merge even when part of the data matches.
- Different strong IDs. Two records with different instance IDs or serial numbers are never unified.
- Reused address. The same IP address seen on different dates and on different systems remains in separate records.
- Cloned image. Machines built from the same image, with the same name, are treated as distinct assets.
Every merge and every split is recorded with its justification. The team can review the decision, and the correction is applied in subsequent synchronizations.
Origin of every data point
A recorded origin for every piece of information.
When two sources disagree about an asset's operating system or owner, CAASM adopts the most reliable source for that information and records the criterion used. The operating system reported by the agent takes precedence over the one inferred from a network scan, and the owner is taken from the CMDB.
For audit purposes, the team can demonstrate the origin of every data point in the inventory and the date from which it is valid.
See your records consolidated into a single inventory.
During the demo, we connect the sources your organization uses and show how records are consolidated per asset.