Software Asset Management · Foundations
What is Software Asset Management –
and how is it different from licence management?
Software Asset Management, or SAM, governs software across its entire lifecycle: from initial demand through procurement, deployment, and use to optimisation and retirement. Licence management is a central discipline within it—but SAM covers more.
In short
SAM is not an inventory and not a single tool.
SAM is an operating model that connects people, processes, data, and technology so software is used safely, economically, and according to demand.
- 01Licence management primarily asks: What are we entitled to use?
- 02SAM also asks: What do we have, who uses it, and why?
- 03SAM covers the full software lifecycle.
- 04Value comes from decisions—not data collection alone.
More than a licence position
Software becomes an asset
when it is actively governed.
Software now extends beyond locally installed applications. The portfolio includes SaaS subscriptions, cloud software, platform services, mobile apps, open source, embedded components, and traditional server products. SAM creates one operating model for them.
Definition & scope
SAM governs software, rights, usage, and accountability as one system
ISO positions Software Asset Management as a specialisation within IT Asset Management. In practice, SAM connects commercial, contractual, technical, operational, and risk perspectives.
Products & components
Operating systems, applications, databases, middleware, mobile apps, open source, and embedded software.
On-premises, SaaS & cloud
Installations, user assignments, subscriptions, instances, containers, and cloud-based services.
Process & accountability
Demand, procurement, approval, ownership, cost, security, usage rights, optimisation, and retirement.
A useful organising model
IT Asset Management
Covers IT assets such as hardware, software, services, and subscriptions.
Software Asset Management
Specialises in software and its complete lifecycle.
Licence Management
Governs licences, usage rights, metrics, contracts, and compliance within that model.
Team names and responsibilities vary. Some organisations use licence management and SAM almost interchangeably. The label matters less than whether the complete lifecycle is actually covered.
SAM and licence management
Closely connected—but not identical
Licence management is a core part of SAM. The following distinction is a practical model, not a rigid organisation chart.
| Perspective | Software Asset Management | Licence Management |
|---|---|---|
| Guiding question | How do we govern software across its full lifecycle? | Which rights do we own, and are we using them correctly? |
| Scope | Portfolio, demand, procurement, inventory, usage, cost, risk, and retirement | Agreements, entitlements, metrics, usage rights, licence position, and compliance |
| Time horizon | Continuous, from demand through retirement | Continuous, with focus on procurement, change, renewals, and reviews |
| Data | Catalogue, owner, technology, identity, usage, finance, contract, and lifecycle status | Evidence, agreements, rights, quantity, metrics, deployment, and consumption |
| Stakeholders | Business, IT, procurement, security, finance, architecture, service management, and legal | Licence management, procurement, IT, legal, finance, and vendor owners |
| Outcome | A transparent, secure, and economical software portfolio | A traceable licence position and compliant, economical use |
The SAM lifecycle
Seven decision points—not an annual inventory exercise
SAM accompanies software through every phase. Each transition needs data, accountability, and a clear decision.
- 01
Demand
Understand the business problem, user group, required capability, and existing alternatives.
Do we need new software at all? - 02
Assessment & approval
Review architecture, privacy, security, integration, licence model, cost, and supplier.
Is the solution suitable for the organisation? - 03
Procurement
Document quantity, metric, edition, agreement, term, notice period, and owner.
What are we buying—and on which terms? - 04
Deployment
Distribute, assign, or enable software under control and update the asset record.
Who receives which version or edition? - 05
Operations & use
Monitor activity, support status, vulnerabilities, cost, compliance, and service quality.
Is the software used safely and meaningfully? - 06
Optimisation & renewal
Evaluate reclaim, downgrade, standardisation, quantity, commitment, or alternatives.
What should be renewed, changed, or saved? - 07
Retirement
Remove access, retain or delete data, uninstall software, and end contracts and cost.
Has the asset been closed completely and traceably?
The data foundation
Five data worlds create one reliable software view
A discovery tool supplies only part of the truth. SAM needs normalised and connected data from several systems.
Product & normalisation
Publisher, product, version, edition, category, support status, and standardised naming.
Contract & entitlement
Order, agreement, proof of licence, metric, quantity, term, and special rights.
Discovery & deployment
Installation, device, server, VM, cloud instance, package, and technical dependency.
Identity & usage
Assignment, role, organisation, activity, last access, and actual feature need.
Cost & accountability
Owner, cost centre, service, contract date, budget, risk, and business criticality.
Knowing that an application is installed does not tell you whether it is authorised, supported, secure, licensed, actively used, necessary, or economical.
Practical case · Duplicate purchasing
A new software request is often a portfolio question—not just a purchase request
A business team wants to purchase a new survey and workshop tool quickly. The need is valid, but the existing portfolio has not yet been reviewed.
‘We need 80 licences for a new collaboration tool.’
The request is considered in isolation
- The new product's features and price are assessed.
- Existing platforms and similar agreements remain invisible.
- Another supplier, contract, and administrative burden are added.
- Overlaps become expensive and difficult to unwind later.
Demand is checked against the portfolio
- The requirement and necessary capabilities are made specific.
- Existing suites, unused rights, and similar applications are compared.
- Security, data, integration, cost, and ownership are considered together.
- The organisation deliberately chooses an existing solution, an extension, or a new product.
SAM ensures the decision reflects the whole portfolio, existing rights, real demand, and the downstream cost.
Tangible value
SAM creates value far beyond licence compliance
An effective SAM programme supports cost, risk, security, operations, and technology governance at the same time.
Understand the portfolio
Products, versions, owners, cost, agreements, usage, and dependencies become visible together.
A reliable basis for decisionsOptimise demand
Unused assignments, wrong editions, duplicate purchases, and unfavourable quantities are identified.
Avoidance, savings, and better forecastingGovern compliance
Usage rights and technical reality are reconciled, gaps prioritised, and evidence protected.
Fewer audit surprisesReduce unknown software
Unauthorised, outdated, or unsupported products can be handled deliberately.
A smaller attack surface and clearer ownershipGovern technology deliberately
Standardisation, cloud migration, SaaS consolidation, and architecture decisions gain better data.
More business value from the portfolioA practical start
Turn a software list into a SAM operating model
Not every organisation needs maximum tool depth on day one. A clear scope, reliable ownership, and a few working processes are a better starting point.
- 01
Define scope and objectives
Start with critical or high-cost vendors, SaaS portfolios, or one clearly defined business area.
- 02
Build a software catalogue and ownership
Normalise products and name business, technical, and commercial owners for each relevant asset.
- 03
Connect core processes
Embed SAM controls into procurement, deployment, joiner-mover-leaver, change, renewal, and retirement.
- 04
Make data quality visible
Document source, recency, coverage, and known gaps instead of creating false precision.
- 05
Measure value regularly
Track compliance, avoided cost, realised savings, portfolio reduction, support status, and cycle time together.
LizenzFrau rule of thumb
SAM is not a tool. SAM is an operating model for software.
A tool can discover software and process data. Clear accountability, connected processes, and repeatable decisions turn it into Software Asset Management.
Primary and official sources
Verified against ISO, CIS, and Microsoft sources.
This guidance is based on information available on 13 August 2026. A new edition of ISO/IEC 19770-5 is currently under development; the published edition remains authoritative until replaced.
- 01ISO/IEC 19770-5:2015 — ITAM and SAM overview and vocabulary↗Open source
- 02ISO/IEC 19770-1:2017 — IT asset management systems↗Open source
- 03ISO/IEC TS 19770-10:2025 — Guidance for implementing ITAM↗Open source
- 04ISO/IEC 19770-3:2016 — Entitlement schema↗Open source
- 05ISO/IEC 19770 standards catalogue↗Open source
- 06CIS Control 2 — Inventory and Control of Software Assets↗Open source
- 07Microsoft — Introduction to Asset Intelligence↗Open source
Note: This article describes a practical operating model. Specific responsibilities, licence positions, and controls must be adapted to the organisation, supplier agreements, and technical environment.
Deep dive · Licence ManagementLicense management is more than compliance
How usage rights, technical inventory, cost, and business demand come together.