Why unique identity matters
Knowing that the organization owns about eight hundred laptops is useless unless it can say which eight hundred, exactly. Asset identification turns a vague population into a precise inventory of objects that can each be told apart. Accounting, licensing, incident response, and replacement planning all assume that the asset mentioned yesterday is the same one mentioned today.
Identification also supports deduplication. When two records describe one machine, or one machine is split across two records, totals stop being reliable. A stable identifier gives reconciliation a key to match on, whatever the source: procurement, a directory or a discovery scan.
Identifier types and their stability
Some attributes are burned into hardware at manufacture, some are generated by software, and some are administrative labels the organization attaches itself. A practical scheme combines several and weighs each by its stability:
| Identifier | What it identifies | Stability |
|---|---|---|
| Serial number | A physical unit from the manufacturer | High, fixed at manufacture |
| UUID / GUID | A system or component instance | High, persists across renames |
| MAC address | A network interface, not the machine | Medium, tied to one network card |
| Hostname | A computer as seen on the network | Medium, renamed and reused |
| IP address | A network location at a point in time | Low, reassigned dynamically |
| Asset tag / inventory number | An organizational bookkeeping unit | High, while the label stays attached |
| SWID tag | An installed software product | High, tied to the installation |
Hardware, software, and composite assets
Hardware identification starts with the serial number, supplemented by manufacturer and model, and anchored by an inventory number. A computer, however, is a composite object. Its CPU, RAM modules, disk drives, monitors, and peripherals each carry their own identities. Inventory practice therefore separates the computer, the primary managed unit, from the devices installed in it.
Software is identified by product name, publisher, version, and installation evidence such as SWID tags (ISO/IEC 19770-2) or registry entries. Two installations of the same application on different machines are separate instances, so license counts and patch coverage can be calculated per machine.
What it looks like in Anexet
In Anexet Inventory, every device has its own card. The serial number, manufacturer, inventory number, and status sit next to the personal computer the device belongs to, so the record of each part stays tied to the right unit.
Where identification breaks down
Identification usually fails in five predictable ways:
| Weak point | What goes wrong |
|---|---|
| Mutable attributes | Hostnames are reused, and MAC addresses can be spoofed or duplicated |
| Virtualization and cloud | Clones share identical IDs or live too briefly to track |
| Component replacement | A swapped disk changes the serial number, not the computer |
| Manual record drift | Hand-kept spreadsheets fill with gaps and inconsistent names |
| Cross-system mismatch | Without a shared key, reconciliation becomes guesswork |
Identification in the inventory workflow
Identification is the first substantive step of IT inventory. Each stage below depends on the key the previous one produced, and tracking and reporting begin only after identification is in place. An asset that cannot be identified cannot be tracked, and an asset identified twice is counted twice.
- 1
Discover
Discovery finds candidate objects on the network and on each workstation.
- 2
Identify
Each candidate receives a durable key built from its stable attributes.
- 3
Match
New observations merge into existing records instead of creating duplicates.
- 4
Track
Status, owner, and location are recorded against one identity per asset.
Keeping identities current
Mature practice defines the identification key before collecting data and captures several attributes so one can stand in for another. It stores results in a single system of record, such as a configuration management database, and re-verifies identity continuously.
Re-verification also makes identification a security control: a device that appears without a known identity, or a familiar one that stops reporting, is itself a signal. That is where identification meets shadow IT, because hardware nobody registered has no identity to check.
Where to start
Start with the attributes that stay with the asset longest: the serial number of the unit and the asset tag while its label stays attached. Treat IP addresses and hostnames as search helpers, never as the key.
Once every asset carries one stable key, counts, licenses, and replacement plans can be trusted without manual checks.
An asset without a stable identity is only a guess about what the company owns.
Anexet TeamHow Anexet handles this
In Anexet, asset identification is automatic: endpoint agents in the Inventory module observe the hardware and software on each machine and feed the identities into inventory records, so the asset list reflects what is actually connected, not what a form once claimed:
The on-premise architecture keeps the collected asset data, configuration baselines, and audit history inside the organization's own infrastructure.
Automatic identifier collection
agents report computer names, operating systems, and connected devices with their types, manufacturers, and serial numbers; inventory cards fill from agent data without manual entry.
Import with deduplication
a hardware import wizard transfers what agents found into the inventory, with search by computer, device, or serial number and a strategy for matches: replace the record, import as new, or skip.
Configuration baselines
each computer's approved devices form a baseline; a component appearing outside it, or a baseline device that stops responding, raises an immediate deviation alert, how component swaps and unauthorized devices surface.
Software identification
installed applications are recorded per computer with publisher, version, installation date, size, and location, the same per-machine identity hardware has.
Lifecycle and ownership
identified assets carry statuses (in use, not in use, in service, to write off), a responsible person, and organizational placement down to the workplace and office-map position.
Audit trail
every addition, deletion, move, configuration, status, and ownership change is recorded in a full, attributable audit log, and asset lists export to xlsx or pdf.
Anexet Inventory
Learn more