What software asset management covers
Software asset management (SAM) keeps a register of every application installed on an organization’s computers. For each entry it records the application name, the publisher, the version, the installation date, the size, and the file path. An administrator can then answer more than “is this program installed anywhere?” They can answer “on which machine, and since when?”
SAM is part of inventory management, but it is not a one-time count. Applications are installed, updated, and removed all the time, so the register works as a continuous process. It shows what runs today, not what was true at the last manual check.
Standards describe software inventory data in different ways. SWID tags are one machine-readable format, and vendors differ on whether they adopt such formats or use their own set of attributes. Check which approach a tool takes before you assume it can exchange data with others.
How the register is built
Building the register starts with IT asset discovery, the process that finds software on each machine. The register becomes useful only after its entries are checked against licenses and policy. The work follows four steps:
- 1
Discover installed software
Agents or scans find every application on each computer, including the ones nobody requested.
- 2
Record the attributes
Name, publisher, version, installation date, size, and file path go into one register entry.
- 3
Match against licenses
Installed copies are compared with the licenses the organization has bought and is entitled to use.
- 4
Review and act
Flag unapproved software, confirm licenses, or open a ticket to remove what should not be there.
Ways to build the register
Software records can be built in three ways. Each one trades accuracy against effort, and the table shows where it breaks down.
Most mature SAM programs use automated discovery as the base layer. Administrators then review what it finds, flag what is not approved, and decide what to keep.
| Method | How it finds software | Main limit |
|---|---|---|
| Manual audit | Someone walks through the machines and records what is installed | Accurate only on the day it is taken |
| User self-report | Employees list the programs they use | People forget rarely used tools and leave out anything they do not consider software |
| Automated discovery | Endpoint agents report installed applications from each computer | Covers only computers where an agent is deployed |
Why software asset management matters
An accurate software register supports several areas that a business depends on:
- License compliance: actual installations are compared with the licenses the business has purchased.
- Unauthorized software detection: unapproved tools surface before they cause problems, including shadow IT that nobody reported.
- Security visibility: software that is not tracked cannot be checked for outdated or vulnerable versions.
- Cost control: licenses on machines that nobody uses can be found and reassigned or cancelled.
Software asset management versus hardware asset management
SAM and hardware asset management (HAM) run side by side, but they track different things. SAM covers what runs on a computer: installed applications, their versions, and the licenses that permit their use. HAM covers the computer itself and its physical components.
HAM answers which equipment the organization owns, and SAM answers which software runs on it. Together they form IT asset management (ITAM). A mature program links both registers, so every application can be traced back to the hardware it runs on.
How the register looks in Anexet
The software inventory in Anexet is built from agent data. Collecting application inventory is one of the toggles in the agent settings, and the result appears on each computer’s Applications tab.
1 / 2
Common mistakes
Most SAM programs fail in the same few ways. They rely on one manual audit that is stale as soon as it ends, count purchased licenses without counting installed copies, or start with a ban before anyone knows what is installed. A ban without a register pushes software further out of sight, so the register should come first.
A ban that comes before the register usually hides software instead of removing it.
- Treating the register as a project with an end date instead of a running process
- Counting purchased licenses without matching them to installed copies
- Blocking programs before the inventory shows which ones people actually use
Where to start
Start with the computers that hold the most licensed or sensitive software, then extend the register to every machine. A current list that covers most of the estate is worth more than a perfect one that never gets finished.
Once the register runs, connect it to purchasing and to removal decisions, so every new license and every new installation is checked against it.
A license you cannot match to an installed copy is a cost you cannot defend.
Anexet TeamHow Anexet handles this
Anexet builds the software register from data that its endpoint agents collect, so every installed application appears without a manual audit:
The platform is deployed on-premise, so the software register and the data behind it stay inside the organization’s own infrastructure.
Applications tab
Agents report installed software for every tracked computer, with the application name, company name, installation date, size, and version.
Per-computer view
The Applications tab sits next to Devices and the Event log on each computer’s card, so software is read alongside the hardware it runs on.
Audit trail
Changes to a computer’s record are logged in the Event log, giving a history next to the software list.
Part of the Inventory module
Software and hardware tracking sit in the same module, so IT and security teams work from one place.
Anexet Inventory
Learn more