Uncia
FR / EN Demo

Glossary

IT asset inventory

An IT asset inventory is the maintained list of the components an organization runs or relies on (hardware, software, services, data), each with a description, a location and an owner. It answers the question of what you have, before any mapping or risk analysis.

Updated

What is an IT asset inventory?

An IT asset inventory is the maintained list of the components an organization runs or relies on, each described by a few attributes: what it is, where it sits, who answers for it, what state it is in. Security frameworks use a broad meaning of asset. NIST's Cybersecurity Framework 2.0 lists data, hardware, software, systems, facilities, services and people. When the list also assigns an owner and a classification to every entry, it is usually called an asset register.

The frameworks agree on the principle. NIST asks that inventories of hardware (ID.AM-01) and of software, services and systems (ID.AM-02) be maintained. The French cybersecurity agency ANSSI defines the inventory as the list of components and their detailed description, and treats it as the first half of any map of the estate.

The textbook case is the server nobody owns. It runs, it answers on the network, and it appears in no file. It gets discovered the day its operating system goes out of support, or the day of an incident. The first job of an inventory is to make sure there are none of those.

What is the difference between an inventory, a map and a CMDB?

An inventory says what you have. A map of the estate says how it holds together. For ANSSI, mapping includes the inventory and adds views, meaning partial representations of the systems, their links and how they work. Its five-step guide builds the inventory first and the views second.

A CMDB is a configuration management database: it records items and the relationships between them, and it lives inside change and incident management processes. It can serve as the inventory if it is fed. Many organizations have a CMDB and, next to it, a de facto inventory spread across the hypervisor console, the endpoint management tool and the directory.

An asset register kept for a security management system is an inventory with accountability added: an owner for each asset and, most of the time, a classification.

What must an IT asset inventory contain?

Scope comes first: physical servers and virtual machines, workstations, network and security equipment, applications and databases, cloud resources (accounts, instances, managed databases), and services bought from suppliers. NIST CSF 2.0 separates inventories of hardware, of software, services and systems, of services provided by suppliers (ID.AM-04), and of data and its metadata (ID.AM-07).

Each row needs a stable identifier that is not just the name, a type, a location (site, cluster, cloud account), an environment, an owner and a status. For a logical server, ANSSI's mapping guide proposes its identification (identifier, IP address, MAC address), its model, its operating system and version, its active network services and the applications attached to it.

Two fields separate a list from an inventory you can use: the source and date of each piece of information, without which nobody knows which row to trust, and the version of the operating system or software, without which no end-of-support date can be established.

The level of detail is a choice. The NIS2 implementing regulation says the granularity of the inventory shall be at a level appropriate for the needs of the entity.

What do NIS2, ISO/IEC 27001 and NIST ask for?

NIS2 asset inventory. Article 21 of Directive (EU) 2022/2555 does not use the word inventory. Its paragraph 2 lists ten groups of measures, and point (i) reads "human resources security, access control policies and asset management". Implementing Regulation (EU) 2024/2690 is more specific, but it applies only to certain entities: DNS service providers, cloud computing and data center service providers, managed service providers, trust service providers and online marketplaces, among others. Point 12.4 of its annex requires them to "develop and maintain a complete, accurate, up-to-date and consistent inventory of their assets", to record changes to the entries in a traceable manner, and to include the list of operations and services together with the network and information systems and other associated assets that support them. For the other entities in scope of NIS2, Article 21 is addressed to Member States, which transpose it into national law (Article 41).

ISO 27001 asset inventory. ISO/IEC 27002:2022, the reference set of controls designed for use with a management system based on ISO/IEC 27001, titles its control 5.9 "Inventory of information and other associated assets". Practitioners cite it as Annex A 5.9. The text of the standard is not freely available, so only the title is quoted here.

NIST. The asset management category of the Cybersecurity Framework 2.0 adds two outcomes worth noting: assets are prioritized based on classification, criticality, resources and impact on the mission (ID.AM-05), and systems, hardware, software, services and data are managed throughout their life cycles (ID.AM-08).

How do you build an inventory from existing sources, and why do tools disagree?

Nobody starts from zero. The hypervisor knows its virtual machines: an RVTools export lists them with their operating systems, disks and networks. The AWS and Azure consoles know the resources in each account. The directory knows the machines joined to the domain, the endpoint management tool those that carry its agent, the CMDB those that were declared, the monitoring platform those being watched, the antivirus those it protects.

Put side by side, these lists rarely give the same count. The reasons are ordinary. Each tool sees only its own scope, and the agent is not installed everywhere. A machine switched off six months ago is still in the directory, and one created last week is not in the CMDB yet. Names differ: short name here, fully qualified name there, an environment suffix somewhere else. The extracts were not taken on the same day.

Those gaps are the most useful result of the exercise. A machine the hypervisor sees and the CMDB does not probably has no declared owner. A machine in the CMDB and nowhere else has probably been deleted. Match on technical identifiers (the ID assigned by the hypervisor or the cloud provider, serial number, MAC address) before matching on names, and keep the source of every value.

How do you keep an inventory current, and with which tools?

For the entities it covers, the NIS2 implementing regulation requires the inventory to be reviewed and updated regularly and the history of changes to be documented. ANSSI's mapping guide recommends regular update campaigns in which each owner checks their own scope, and a function in charge of controlling those updates.

A spreadsheet works for a small estate as long as one person maintains it. It keeps no history and does not cope well with ten contributors.

An endpoint or asset management tool, agent-based or network-scanning, gives an accurate reading of what it reaches: hardware, operating system, installed software. It knows nothing about what it does not reach.

A CMDB adds relationships and the link to changes. It demands a data entry discipline that is hard to sustain unless tools feed it.

A source-derived inventory reconciles what each tool already knows and shows the gaps. It depends on how fresh the extracts are.

Whatever the family, two rules hold: a source and a date on every row, and a review on a fixed schedule instead of whenever someone has time.

What Uncia adds, and what it does not do

Uncia reads your sources read-only and reconciles them in a knowledge base: clouds, hypervisors, CMDB, firewalls and scanners through connectors, and your files dropped in as they are (exports such as RVTools, flow matrices, architecture documents). It changes nothing in your systems. Each element has a record that says what is known about it and where each piece of information comes from; when two sources disagree, both values stay visible. Each end-of-support date carries its source, and the knowledge base updates with every collection. The page on inventory and connectors describes how it works.

Uncia works from what your sources contain and tells you which files it is missing. Information absent from every source is shown as undetermined; a person fills it in, and when the language model proposes a value, someone decides. Reports structured along NIS2, ReCyF, DORA or ISO 27001 attach each section to the requirement it addresses; they do not amount to compliance. Uncia reads your CMDB and does not stand in for it.

Sources

Frequently asked questions

Does NIS2 require an asset inventory?

Article 21(2)(i) of the directive lists asset management among the minimum measures and does not use the word inventory. Implementing Regulation (EU) 2024/2690, which applies only to the entities named in its Article 1 (DNS, cloud, data center and managed service providers, among others), requires in point 12.4 of its annex a complete, accurate, up-to-date and consistent inventory of assets.

Does ISO/IEC 27001 require an asset inventory?

ISO/IEC 27002:2022, which details the security controls used with ISO/IEC 27001, includes a control 5.9 titled "Inventory of information and other associated assets". The full text of the standard is not freely available.

What is the difference between an asset inventory and an asset register?

The two terms are often used for the same thing. Asset register tends to be used when each entry also carries an owner and a classification, which is how security management systems use the list.

How often should an IT asset inventory be updated?

The texts consulted set no numeric frequency. Implementing Regulation (EU) 2024/2690 speaks of regular review and update with a documented history of changes. ANSSI's mapping guide recommends regular update campaigns.

Should cloud and SaaS services be in the inventory?

Yes. NIST CSF 2.0 includes an outcome for inventories of services provided by suppliers (ID.AM-04), alongside inventories of the hardware, software, services and systems the organization manages itself.

Every week, an article to know your IT estate better

Architecture documents, end of support, NIS2, CMDB, migrations: methods you can apply with or without Uncia.

Get a call from our team

Thirty minutes with a member of our team, remote or on site: Uncia on a demonstration instance, then on part of your own estate if you wish. We reply within 48 hours.

Request received

Thank you. A member of our team will reply within 48 hours to set a date.