IT asset management, or ITAM, is the practice of knowing what technology your organization owns, where it is, who uses it, what it costs and what rights and obligations come with it, from the day it is planned until the day it is retired. It is one of the least glamorous disciplines in IT and one of the most financially important.
This guide explains what ITAM is, why organizations need it, and how it is changing as software moves to subscriptions, cloud and SaaS spread across business units, AI tools arrive without procurement involvement and hardware prices behave differently from the last decade. Where we use figures, we name the source. Where a source is a vendor or a market research firm, we say so.
The short answer
ITAM is the discipline of knowing what technology you own and use, what it costs and what you are obliged to do about it, across its whole life. It is required because cost, audit exposure, security and service quality all depend on accurate asset data. In 2027 the pressure points are SaaS, cloud and AI visibility, hardware prices and the move from defensive compliance to optimization.
What is IT asset management?
An IT asset is anything the organization pays for, depends on or is accountable for in technology: physical hardware, installed software, cloud instances, SaaS subscriptions, licenses, contracts and now AI applications and agents. ITAM is the set of processes, data and roles that keep an accurate record of those assets and manage them through their life to get value, control cost and limit risk.
The international standard for the practice is ISO/IEC 19770-1, which sets requirements for an IT asset management system. It applies to all types of IT assets and to organizations of any size, and it is an extension of the general asset management standard ISO 55001 to the IT discipline. ISO records show the 2017 edition was last reviewed and confirmed in 2024 and that an amendment on climate action was issued in 2024.
The lifecycle matters more than the list. A list tells you what existed on the day it was compiled. A lifecycle process keeps the list accurate because every purchase, deployment, move and retirement creates or updates a record as a normal part of the work.
What ITAM covers
ITAM is an umbrella over several specialist areas. They share a lifecycle and a data model but need different skills, which is one reason organizations run them with different teams and then struggle to join the data.
ITAM, SAM and HAM
Hardware asset management, HAM, tracks physical devices through procurement, deployment, maintenance and disposal. Software asset management, SAM, tracks software installations and entitlements to manage cost and compliance. We cover SAM in depth in our companion guide, What Is Software Asset Management? The Complete 2027 Guide. Cloud and SaaS asset management applies the same ideas to subscriptions and instances that appear and disappear quickly, often outside IT.
ITAM and the CMDB
A configuration management database holds the configuration items that support services and the relationships between them. ITAM holds financial, contractual and lifecycle data about assets. The two overlap, and a common mistake is to build them as separate data stores with different owners. The better pattern is shared identifiers, clear rules on which system owns which attribute and regular reconciliation. Our review of AI in CMDB tools shows where the tooling is heading.
The standards behind the practice
Why ITAM is required
- You cannot control cost you cannot see. Software, cloud and SaaS spend is spread across contracts and cards. ITAM provides the inventory and contract data needed to reclaim, rightsize and renegotiate. Our guide to reducing IT spend in 2027 builds on that data.
- Audits and compliance carry real cost. In the Flexera 2026 survey, 48% of organizations were audited in the last year and 44% spent more than $1 million on software audits over three years.
- Security depends on knowing what exists. Unknown devices, unmanaged software and forgotten cloud instances are exposure. Patching, vulnerability management and access reviews all start from an inventory.
- Service management needs accurate data. Incident, change and problem decisions rely on knowing what a configuration item is, who owns it and what depends on it.
- Lifecycle decisions need evidence. Refresh, repair, reuse and disposal choices depend on age, condition, warranty and use.
- Sustainability and reporting questions are increasing. Device lifetimes, reuse and secure disposal are now questions that ITAM data can answer. ISO added climate action changes to ISO/IEC 19770-1 in 2024.
- AI adoption needs governance. Teams adopt AI applications quickly, often through expense cards. Without a record of what is in use, there is no basis for security review, cost control or data protection.
The survey also records that complete IT asset visibility fell to 36%. That number deserves attention. It does not say organizations are careless. It says the estate is growing in forms that the old tools did not cover: SaaS, cloud services, bring your own license arrangements and AI.
How ITAM is changing
1. Scope is widening beyond what discovery can see
Traditional ITAM relied on agents and network discovery of devices and installed software. SaaS, cloud and AI services are bought by credit card, invoice or an API key and leave little on the network. Flexera reports that visibility has improved fastest where tools have caught up: SaaS visibility rose from 50% to 66%, cloud instance visibility from 63% to 74% and visibility of cloud and bring your own license entitlements from 27% to 43%. On premises hardware visibility slipped from 76% to 74%.
Notice what the chart says about priorities. The areas with the least visibility, bring your own license in the cloud and AI software, are also where cost and compliance surprises are likely to appear.
2. AI software is the new visibility gap
The 2026 survey measured AI software visibility for the first time: 31% report accurate visibility. The same survey found 84% name tracking or adopting AI applications as their top combined challenge, 59% say wasted AI spend rose, and only 29% measure the value of their AI software. Nearly half are already tracking AI as part of software spend, and 45% actively identify unsanctioned AI use.
Our view is that the answer is not a new silo for AI assets. AI applications, models and agents should be recorded with the same lifecycle, owner, cost and contract fields as other assets, plus a few AI specific fields such as data classification, model provider, usage limits and approved use cases. Gartner’s 2027 guidance for ITSM points the same way: track the AI agents that are persistent, that affect service delivery or that carry regulatory significance, and avoid an exhaustive registry of everything.
3. The goal has shifted from compliance to optimization
The Flexera survey shows ITAM teams still spend a large share of effort on audits: 22% on audit response and 22% on audit allocation, against 32% on software optimization. At the same time, optimizing software spend is named as the top SAM priority, more than 19 percentage points ahead of the next item. The direction is clear. Teams want to move effort from defense to savings and decisions.
4. ITAM is moving closer to FinOps and the cloud team
Flexera’s ITAM survey found that 78% of organizations have a FinOps team, and an analysis of the report by ITSM.tools notes that the share of ITAM teams reporting to the CIO or CTO fell by 6 points while the share reporting into cloud or FinOps functions rose by 5 points. Flexera’s separate 2026 State of the Cloud survey of more than 750 cloud decision makers found that wasted cloud spend rose to 29%, the first increase in five years, and that 63% have FinOps teams. Different surveys give different shares, so compare the direction and not the exact figure. The practical point is that ITAM data on assets, owners and contracts is the input FinOps needs, and the two functions should share it.
5. Hardware economics have changed
For years, hardware planning assumed falling or stable prices. Gartner’s October 2026 forecast says memory prices have more than doubled over the past 12 months, expects the effect to persist through 2027 and says affordability pressure will suppress end user demand. Gartner’s April forecast noted that higher memory costs are lifting device average selling prices and constraining replacement cycles. Device spending is forecast at $916 billion in 2027, up 8.1%.
For ITAM, this has a direct meaning. Accurate age, warranty, condition and utilization data lets a team extend the life of devices that are still fit for purpose, target replacement where it matters and decide between repair, reuse and replacement with evidence. That is our interpretation of the forecasts, not a Gartner conclusion, and it is a good reason to review refresh policies before the 2027 budget is fixed.
6. Data quality beats completeness
The temptation in ITAM is to record everything. The better test is whether a record is accurate enough to support a decision someone actually makes. Prioritize the attributes used for cost, security and service decisions: owner, location, status, lifecycle dates, contract link, cost and the services that depend on it. A smaller accurate set beats a large stale one, which is also the direction of Gartner’s 2027 guidance on trusted service data.
7. The market is growing, slowly and with consolidation
Mordor Intelligence, a market research firm, estimates the ITAM market at about $2.2 billion in 2026 growing to about $3.0 billion by 2031, a compound annual growth rate of 6.28%, with cloud deployment the largest share. Market estimates differ widely between firms and this figure is not an official statistic, so use it as a rough indicator of a mature, steadily growing category.
Where do you stand? An ITAM maturity view
Use the ladder below to judge the current state for each asset class. Most organizations are more mature for laptops than for SaaS, and less mature for AI than for anything else. Our hardware asset management tool assessment and software asset management tool assessment can help structure that conversation.
A practical ITAM plan for 2027
Step 1: Set scope and owners
Write down which asset classes are in scope, for each class who owns the data, and what decisions the data supports. Include SaaS and AI from the start, even if the first version is a short list built from finance and expense data.
Step 2: Discover and reconcile
Combine discovery, endpoint management, procurement, HR joiner and leaver data, contracts and general ledger data. Resolve duplicates and mismatches. Expect the first reconciliation to expose a large unmatched set. That is the finding, not a failure.
Step 3: Run the lifecycle
Write short, testable processes for receipt and tagging, assignment, moves and returns, repair, and secure disposal. Embed the record updates in the work that people already do, such as onboarding and offboarding, so the data stays accurate without a separate effort.
Step 4: Connect the data
Feed accurate records to the CMDB, security tooling, finance and the service desk. Agree identifiers and field ownership. Review the integration quarterly. This is where ITAM starts to pay back to other teams.
Step 5: Optimize and govern
Use the data for reclaim, rightsizing, renewal timing and replacement decisions. Put AI assets under the same policy as other assets with additional fields for data and risk. Report savings and risk reduced, not only inventory counts.
Measures that show ITAM is working
| Measure | What it shows |
|---|---|
| Inventory accuracy from sample audits | Whether records match reality |
| Discovery and procurement match rate | How much of the estate is explained |
| Unowned assets | Accountability gaps |
| Hardware age profile and warranty coverage | Refresh exposure and repair options |
| Reclaimed licenses and subscriptions | Savings delivered by the process |
| Contracts with owners and renewal dates | Whether renewals are planned or reactive |
| AI applications with an owner and approved use | Control of the fastest growing category |
| Audit findings and outcomes | Compliance posture |
Common mistakes to avoid
- Buying a tool before deciding the data model. A tool cannot fix unclear ownership.
- Treating hardware, software and SaaS as separate projects. They share a lifecycle and should share data standards.
- Running ITAM only for audits. Defensive ITAM never pays for itself the way optimization does.
- Letting the first reconciliation become a blame exercise. Use the gaps to fix process.
- Ignoring disposal. Retirement records matter for security, finance and sustainability reporting.
Frequently asked questions
What is the difference between ITAM and ITSM?
ITSM manages services and the work around them, such as requests, incidents and changes. ITAM manages the assets behind the services through their lifecycle, including cost, contracts and ownership. They share data, especially configuration items, and work best when the records are consistent.
What is the difference between ITAM and a CMDB?
A CMDB records configuration items that support services and their relationships. ITAM records the financial, contractual and lifecycle data of assets. Many organizations hold both and link them with shared identifiers.
Which assets should we track first?
Start with the ones that carry the most cost or risk: high value software contracts, cloud and SaaS subscriptions, servers and end user devices. Add AI applications early, since they are growing fast and are often bought outside IT.
Do we need a dedicated ITAM tool?
Not always on day one. A well run process with reliable data sources can start in a controlled spreadsheet. As volume and complexity grow, a dedicated platform is needed to reconcile sources automatically and keep records current.
How is AI changing ITAM?
AI software is a new asset class with a visibility gap: only 31% of organizations report accurate visibility in the Flexera 2026 survey. ITAM teams are asked to find unsanctioned use, track contracts and cost, and measure value, while AI features also begin to help with data cleanup and classification.
How long does it take to set up ITAM?
A first useful view of the main asset classes is possible in a few weeks if data sources are available. A reliable, process driven record across hardware, software, cloud and SaaS typically takes several months and keeps maturing after that.
Get a clear picture of your asset estate before the 2027 budget is set
We help organizations design ITAM processes, choose and implement tools and build the asset data that finance, security and service management can trust.
ITAM process and tool consultingHardware asset management assessmentITAM Starter Kit
Sources and notes
- Flexera, 2026 State of ITAM Report press release (June 24, 2026)
- Flexera, How teams are regaining control of cloud, SaaS and AI
- Flexera, How leaders are balancing AI cost optimization and governance
- ITSM.tools, Asset management teams are governing AI spend they cannot see
- Flexera, 2026 State of the Cloud press release
- Gartner, Worldwide IT spending forecast for 2027 (October 2026)
- Gartner, Worldwide IT spending forecast for 2026 (April 2026)
- SolarWinds, Gartner Top Trends in AI for ITSM for 2027 (report page)
- ISO, ISO/IEC 19770-1:2017 IT asset management systems requirements
- ITAM Standards, ISO/IEC 19770-1 and 19770-3
- Wikipedia, ISO/IEC 19770 parts overview
- Mordor Intelligence, IT asset management market (market research estimate)
