How the inventory is collected
Eleven sources, each with what it reads, what it needs to read it, and its real coverage status.
Coverage status
Three labels only: verified in the field, implemented, in progress. A label inflated on this page becomes a promise in a negotiation, so the status here follows the team’s status matrix and is never rounded up.
Network
interfaces, chassis, serial numbers
SNMP v1/v2c/v3, read-only community
[status]
L2 topology
what is connected to which port
CDP or LLDP enabled on the devices
[status]
MAC table
what sits behind a port that does not answer SNMP
read access to the switch forwarding table
[status]
Servers
installed software, services, configuration
SSH, or WMI over DCOM, read-only account
[status]
Closed machines
inventory of hosts unreachable from the network
inventory agent, signed installer
[status]
Virtualisation
hosts, guests, clusters, datastores
read-only API account
[status]
Cloud
instances, services, tags
read-only API credentials, least privilege
[status]
Directory
accounts, groups, machine objects
LDAP bind, read-only
[status]
Power continuity
UPS state, load, battery
SNMP, UPS-MIB and vendor MIBs
[status]
Device configurations
running configuration, with history and diff
read access to the device configuration
[status]
Traffic
who talks to what, and what is exposed
NetFlow, IPFIX or sFlow export towards the probe
[status]
Agentless by default
The agent exists only for machines that cannot be reached any other way, and installing it is a decision taken case by case. Vendors who sell agents have to ask you to put one on everything.
Where a source is listed as implemented rather than verified, it means the chain works but real production environments are still being tested. It is demonstrated, not guaranteed on a specific version without a trial.
Test the sources on your own network
The trial shows which sources answer in your environment, and which do not — with the reason.