Skip to content
CMDB Alternatives Compare

LESSON 3 OF 10 · Why records drift · 3 MIN

Configuration items and assets: why the two lists disagree

SHORT ANSWER

IT asset management counts what you own and pay for; configuration management records what you run and how it connects. The two lists overlap but never match exactly, and confusing them is a common source of CMDB disputes.

By The Record Desk · CMDB Alternatives Compare · Published 2026-09-06 · Updated 2026-10-11

What is the difference?

An asset is something the organization owns or pays for: a laptop with a purchase order, a software license, a SaaS subscription. A configuration item is something IT must control to deliver a service: a server, a database instance, a load balancer, an application, and the links between them. Many things are both. Some are only one.

What is an asset but not a CI?

A spare laptop in a cupboard is an asset with a cost and a warranty, but it supports no service yet. A software license is an asset to finance and procurement, but configuration management cares about the installed instance, not the entitlement. Oomnitza's pages describe this side of the record: reconciling procurement, MDM, EDR and ITSM data into "One trusted record for every physical asset you own", and automating license reclamation.

What is a CI but not an asset?

A virtual machine that lives for six hours, a container, a DNS record or a cloud security group is a configuration item that matters to change and incident work, yet it never appears on a purchase order. ServiceNow Discovery's event-driven updates for cloud environments exist because these items change faster than any scheduled scan.

Why do the lists disagree?

They are filled from different places. The asset list comes from procurement, finance and MDM. The CI list comes from discovery and connectors. Each side sees things the other cannot. When both are pushed into one CMDB without matching, the result is duplicates and arguments about which number is right.

How do the options on this site handle the split?

The three option types take different sides of it. CMDBs with discovery, such as ServiceNow CMDB, Freshservice and Device42, start from configuration items. Network discovery tools such as Lansweeper, runZero and Armis start from what is on the network. Reconcile-and-sync platforms such as Axonius, Oomnitza and JupiterOne start from the tools you already run, including finance and identity systems, and match the two views. None of these is wrong; they answer different first questions.

What should you decide first?

Decide which questions the record must answer. If the main use is change and incident work, the CI view matters most. If audits, license spend or security coverage drive the work, the asset view matters more. Most organizations need both, which is why reconciliation and sync carry 36% of the weight in our ranking together.

Next lesson

Lesson 4 of 10

Three ways to fill a CMDB without typing

There are three automatic routes into a configuration record: the CMDB's own discovery, network discovery tools that feed it, and platforms that reconcile data from tools you already run. Most mature setups combine two of them.