Three ways to fill a CMDB without typing

Why not type it?

Typing is the slowest and least reliable way to fill a record. People enter what they know on the day, and the record ages from then on. The drift patterns in lesson 2 all grow faster when the main input is a person.

Route 1: the CMDB's own discovery

ServiceNow, Freshservice and Device42 all document discovery that writes into their own CMDB. ServiceNow describes agentless discovery for on-premises, cloud and container infrastructure plus a unified agent; Freshservice describes agentless discovery of devices, software, storage and cloud resources; Device42 describes agentless discovery "from legacy mainframes to cloud containers" run continuously on a schedule. The strength of this route is that the record and the workflows live in one product. The cost is that discovery is another system to license and run: ServiceNow states Discovery "is available with IT Operations Management".

Route 2: network discovery that feeds the CMDB

Lansweeper, runZero and Armis find devices on the network, including ones no agent or directory knows about, and hand the data to a CMDB or service desk. runZero needs "no agents, authentication, or appliances"; Lansweeper runs passive detection by default; Armis identifies devices passively against a knowledgebase of over 6.5 billion assets. These score well on effort to maintain, with runZero highest at 86. Their limit is the edge of the network: SaaS apps and identities are mostly outside what they document.

Route 3: reconcile what you already run

Axonius, Oomnitza and JupiterOne build the record from tools the organization already operates: EDR, MDM, directories, cloud accounts, HR and the CMDB itself. Axonius lists more than 1,200 adapters, Oomnitza more than 1,500 data surfaces, JupiterOne more than 200 integrations. This route reaches assets the network never shows, such as SaaS apps and identities, and it can compare sources against each other. The cost is credentials: every connection needs API access that someone maintains.

How do the routes combine?

They are not exclusive. A common pattern is the CMDB as system of record, a network discovery tool for devices and a reconciliation layer that compares everything and writes corrections back. Axonius, for instance, documents reading ServiceNow CMDB tables and creating, updating and retiring ServiceNow records, so it works beside the CMDB rather than in place of it.

Which route fits your problem?

• If the record is missing devices on your own network, start with route 2.
• If the record is full but contradictory, start with route 3.
• If there is no CMDB yet and the service desk is the center of IT work, start with route 1.

The ranking shows how each option scores within its route and across all three.