# asset identity matching

GLOSSARY, read 10 Nov 2026

**Definition.** Asset identity matching decides that two records, from two tools or two platforms, are the same machine. A wrong match merges two assets or splits one into two, and either distorts counts. Brinqa 11.34.71 now rejects a manually created record whose unique identifier value already exists.

Choose the match keys before the load: hostname, IP, cloud instance ID, MAC or an external ID. Run the match on the exported assets and count merges and splits against the source total.

Kenna's asset list returns active assets with open vulnerabilities by default, and inactive assets need a filter, so an export that skips the filter drops retired machines.

## A sourced example

Brinqa's 11.34.71 release notes, dated September 29, 2026, describe a guardrail that rejects manual entry of a record with a unique identifier value that already exists.

## Related terms

- [field mapping](/glossary/field-mapping/)
- [tag migration](/glossary/tag-migration/)
- [ticket re-linking](/glossary/ticket-re-linking/)
- [connector parity](/glossary/connector-parity/)

## Sources

- Source for the example: asset identity matching: https://docs.brinqa.com/docs/v11/releases/platform/11-34-71 (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/asset-identity-matching/
