Inventory

An IT inventory is usually split into two connected parts. Most controls need both at once, so mature programs track them together as part of IT asset management.

Each item is recorded with a status, an owner, a department, and a location. Software records are what license and patch management depend on.

Records can be entered by hand. Manual inventory ages fast, though, in any organization that adds or reassigns equipment regularly.

Administrators record equipment during purchase or a periodic physical audit. The record is accurate when entered, but goes stale as soon as something changes unnoticed.

Software agents on endpoints, or network scans, report hardware and installed applications on their own. New and changed devices appear without anyone typing them in.

Most mature programs combine both. Automated discovery keeps the register populated, and administrators add the ownership, status, and location that discovery cannot infer.

In Anexet Inventory, each device is listed with its type, inventory number, status, workplace, and department. The header counters show computers with deviations and newly found computers, so changes are visible before anyone opens a card.

An accurate inventory supports four needs:

• Visibility. Equipment and software missing from the inventory cannot be patched, monitored, or covered by incident response. Unrecorded tools are a common form of shadow IT and a recurring source of blind spots.
• License and cost control. Software inventory compares what is installed with what is licensed. It catches under-licensing risk and paid seats nobody uses.
• Configuration compliance. A recorded baseline for each machine reveals deviations, such as a rogue device connected to the network or an expected one missing, instead of finding them by accident.
• Maintenance and audit. A current inventory is the starting point for hardware refresh planning, IT audits, and any review of what the organization actually runs.

An inventory is only useful while it stays current. Equipment changes hands, machines are reassigned or replaced, and new software is installed constantly. A yearly snapshot is already wrong when someone reads it.

Audits compare the recorded inventory with what discovery actually finds. Exportable reports by device type, department, status, or software support license renewals, budgeting, and the evidence auditors ask for.

1. 1

   Keep discovery continuous

   Run discovery as an ongoing process, not a periodic scan.

2. 2

   Log every change

   Record each addition, move, and status change so the history stays auditable.

3. 3

   Flag deviations as they appear

   Report departures from the expected configuration at once, not at the next scheduled check.

The three terms overlap and are often used loosely, but they describe different levels of detail. An asset register is the broadest concept. It can include data, people, and services alongside equipment, organized around value and ownership.

Inventory is narrower and more operational. It covers the hardware and software that actually exist, refreshed by discovery rather than by policy. A configuration management database (CMDB) goes one step further. It keeps the same records and adds the relationships between them, so a change to one item can be traced to everything it affects.

In practice, inventory is the living data layer. It feeds the asset register and, in larger environments, the CMDB above it.

Start with the servers, the machines that hold client data, and the software they run. Those records give the fastest return, and the rest of the inventory can follow from them.

Keep the records current from the first day. An inventory that is accurate once and then left alone turns into the same blind spot it was meant to close.