What are assets?
An asset is anything that has value to an organisation and whose availability, integrity or confidentiality must be protected: hardware, software, data and also people and processes. In the context of IT and OT (Operational Technology), assets are the physical, digital and logical components that play a role in production, process control or information processing, from a PLC in the field to a configuration file on an engineering station. Assets are the starting point of every risk analysis and of almost every security standard, because you can only protect what you know you have.
π§ What does the term asset cover?
The asset management standard ISO 55000 defines an asset as an item, thing or entity that has potential or actual value to an organisation. That value can be financial or non-financial. In information security (ISO 27001 and ISO 27002, control 5.9) the emphasis is on information and the βother associated assetsβ that store, process or transport it.
Risk assessments based on standards such as ISO 27005 often distinguish two kinds:
- Primary assets β the business processes and information that represent real value, such as a production process, a recipe or the supply of drinking water
- Supporting assets β the components those primary assets depend on: controllers, servers, networks, software, sites and people
That distinction stops an asset list from becoming a purely technical inventory. A historian is not valuable because it is a server, but because the process relies on it.
π§± What types of assets exist in IT and OT?
| Type of asset | Examples |
|---|---|
| Physical assets | PLCs, RTUs, SCADA servers, workstations, network switches, sensors, actuators |
| Software and logical assets | Applications, operating systems, firmware, PLC programs, configuration files, setpoints |
| Information assets | Historical process data, recipe data, alarm notifications, drawings, reports |
| Network assets | Routers, firewalls, VLAN segments, conduits, IP address plans and firewall rules as configuration |
| People and processes | Knowledge held by operators, administrators and external suppliers; procedures and work instructions |
In practice an OT asset inventory focuses mainly on the first two rows. Information, network configuration and knowledge are linked to those technical assets as attributes or dependencies.
π Which OT assets do you find at each Purdue level?
The Purdue Model helps you organise OT assets by function and position in the network:
| Level | Function | Typical assets |
|---|---|---|
| 0 β Process | Measuring and switching | Sensors, actuators, valves, motors, drives |
| 1 β Basic control | Local logic and control loops | PLC, RTU, IED, safety systems (SIS) |
| 2 β Supervisory | Monitoring and operation | SCADA servers, HMIs, engineering stations |
| 3 β Operations | Production management and data | Historian, MES, domain controllers, backup servers |
| 3.5 β IT/OT boundary | Controlled connection | DMZ, jump servers, patch servers, firewalls |
| 4β5 β Enterprise | Planning and office IT | ERP, email, office workstations, cloud applications |
The lower the level, the more direct the influence on the physical process and on safety. Lower levels also more often contain legacy systems that cannot be patched for years.
π― Why is an asset overview so important?
Without an up-to-date overview of your assets, no other security measure works properly:
- Risk analysis β a risk assessment or business impact analysis starts with which assets exist and what they are worth
- Vulnerabilities β only with manufacturer, model and firmware version can you match new CVEs to your installation (vulnerability management and patch management)
- Detection β Monitoring with a SIEM or an IDS only recognises anomalies once you know what normal looks like
- Configuration and change β configuration management and change management rely on a trustworthy baseline
- Incident response β a CSIRT or CERT needs to know quickly which systems are affected and who owns them (incident response)
- Recovery β business continuity requires a backup and a recovery plan for every critical asset
π Without insight into your assets, you cannot know what to protect.
π Which standards and laws require an asset inventory?
Almost every relevant framework starts with assets:
| Framework | Asset requirement |
|---|---|
| IEC 62443 | IEC 62443-2-1 expects an inventory as part of the security programme; IEC 62443-3-3 requires, through SR 7.8 from security level 2 upwards, an up-to-date inventory of all control system components |
| NIS2 | Article 21 lists asset management as a mandatory measure; in the Netherlands it is transposed by the Cyberbeveiligingswet, in force since 15 August 2026 |
| Implementing Regulation (EU) 2024/2690 | For digital infrastructure and ICT service providers, such as cloud and data centre providers and managed (security) service providers: a complete, accurate and up-to-date inventory in which changes are recorded traceably |
| ISO 27001 | Annex A control 5.9 requires an inventory of information and other associated assets, including owners |
| CIS Controls v8.1 | Control 1 (enterprise assets) and Control 2 (software assets) are the first two of eighteen controls |
| NIST CSF 2.0 | The Identify function opens with the Asset Management category (ID.AM) |
| BIO | Based on ISO 27001/27002; BIO2 (September 2025) replaced the three BBN levels with a risk-based approach |
π§ Which data do you record for each asset?
In August 2025 CISA and partners, including the Dutch NCSC and the German BSI, published Foundations for OT Cybersecurity: Asset Inventory Guidance. It names fourteen high-priority attributes:
- Identification β asset number, hostname, role/type and physical location
- Network β IP address, MAC address, active communication protocols and open ports/services
- Vulnerability β manufacturer, model and operating system
- Management and detection β criticality, user accounts and how logging for the asset is set up
Medium-priority attributes include backup frequency, a known-good baseline image and the department or owner. In practice you should add firmware version, lifecycle status (such as the vendorβs end of support) and the supplier holding the maintenance contract.
π How do you discover assets: passively or actively?
Asset Discovery fills the inventory using three complementary methods:
- Passive β a sensor listens through a SPAN port or network TAP and identifies devices from the traffic using deep packet inspection (passive monitoring). Safe, but it only sees what communicates.
- Active β targeted queries to devices in their own protocol, for example an S7 or Modbus TCP read of type and firmware. More complete, but an aggressive network scan can make fragile older controllers hang.
- Physical and documentary β walking the plant, checking cabinets and drawings. Indispensable for serial and non-networked equipment.
Specialised OT platforms such as Claroty, Dragos and Tenable OT combine passive detection with safe active querying.
π‘οΈ How do you build an asset management process in practice?
The CISA guidance describes five steps that work well in European OT environments too:
- Define scope and objectives β which sites, zones and systems are included, and who is responsible
- Identify assets and collect attributes β passively, actively and physically, using the fourteen core attributes
- Create a taxonomy β classify assets by function and criticality (high, medium, low) and group them into zones and conduits following the zones and conduits model
- Manage the data β store it centrally and securely, for example in a CMDB or an asset inventory system
- Lifecycle management β record changes, replacement and decommissioning, and validate the inventory periodically
Criticality then drives the measures: high-criticality assets get the most stringent measures, such as network segmentation and role-based access management (RBAC) within a layered defence-in-depth approach. Medium-criticality assets get robust monitoring and regular updates, and low-criticality assets get baseline measures; they are included in the inventory mainly for completeness.
β Frequently asked questions
What is the difference between an asset and a configuration item?
An asset is something of value to the organisation, such as a PLC or a historian. A configuration item is any component under configuration management, including its relationships, and is usually recorded in a CMDB. Many assets are also configuration items, but a CMDB focuses on relationships and changes.
What is the difference between assets, asset inventory and asset management?
Assets are the valuable components themselves. An asset inventory is the up-to-date overview of those assets and their attributes. Asset Management is the wider process of managing assets across their whole lifecycle, from procurement and maintenance to decommissioning.
Is passive asset discovery safe for OT networks?
Passive asset discovery is safe because no traffic is sent to the devices; the sensor only listens through a SPAN port or TAP. The drawback is that devices that rarely or never communicate stay out of view. Most organisations therefore combine passive detection with safe, protocol-specific active querying and a physical walkdown.
How often should an OT asset inventory be updated?
An OT asset inventory should be updated with every change to the installation and fully validated periodically, for example once a year. NIS2 requires asset management, and Implementing Regulation (EU) 2024/2690 specifies this as an up-to-date inventory in which changes are traceable. Continuous passive monitoring helps you spot new or missing devices immediately.
How do you determine the criticality of an asset?
The criticality of an asset follows from the consequences of failure or manipulation for safety, production, the environment and service delivery. A business impact analysis or a risk assessment according to IEC 62443-3-2 scores those consequences. CISA recommends a simple high, medium and low classification, with the strictest measures for high.
Do people and knowledge count as assets?
People and knowledge count as assets in the broad, risk-based sense used by ISO 55000 and ISO 27005. The departure of the only engineer who understands an old controller is a real continuity risk. A technical asset inventory usually does not record people as items, but it does record them as owners, administrators or contacts.
π In summary
An asset is anything of value that needs to be protected, from a physical PLC to a digital configuration file. An up-to-date asset inventory with the right attributes and criticality is the foundation for risk analysis, vulnerability management, detection, business continuity and Compliance with IEC 62443, NIS2 and ISO 27001.
