Learn the Discovery Lifecycle

Discovery starts when a scan job runs against a defined target. The scan job references one or more discovery applications or agents that use stored credentials to connect to endpoints through standard protocols such as WMI, SSH, SNMP, or cloud APIs.

After connecting, discovery detects active assets and collects configuration details such as hostname, operating system, and running processes. Identification rules then match the scanned data with existing configuration items in CMDB to prevent duplicates. New configuration items are created automatically when no match is found.

Process jobs analyze discovered processes and network ports to map dependencies among assets.

When processing is complete, discovery updates CMDB with the latest asset information. Dashboards and reports summarize scan results, coverage, and error trends. By automating each stage, discovery removes manual effort, prevents data drift, and keeps CMDB continuously aligned with your evolving IT environment.

Example Automating Asset Updates Across Hybrid Environments

Your IT operations team manages both on-premises servers and cloud workloads. A discovery application performs agentless scans inside the corporate network, while lightweight agents collect data from remote laptops. Separate targets are configured for AWS and Azure using stored credentials. Daily scan jobs detect new virtual machines, map them to existing CIs, and create new records as needed. Process jobs then map application dependencies and dashboards confirm that CMDB reflects the latest infrastructure state.