TroutTrout
Back to Blog
NIS2Asset Management

NIS2 Asset Inventory Requirements: What to Track and How to Do It On-Premise

Trout TeamLast updated: 4 min read

Introduction

NIS2 Article 21 requires essential and important entities to maintain an accurate inventory of network and information system assets. This article lists what your asset inventory must contain under the NIS2 Directive and how to build and maintain it on-premise.

What NIS2 is and why the inventory matters

The NIS2 Directive replaces the original NIS Directive and sets stricter cybersecurity rules across the EU. It requires specific security measures and active risk management. NIS2 depends on asset management: you cannot assess risk, report incidents or control access without knowing what is on your network.

Key Objectives of NIS2

  1. Stricter security measures: NIS2 sets stricter security requirements for network and information systems.
  2. Incident reporting: Entities must notify the relevant authorities of incidents promptly.
  3. Cooperation and information sharing: Member states and sectors share information and work together.

Asset Inventory Requirements Under NIS2

An asset inventory is a list of every hardware, software and virtual asset in the organization. NIS2 compliance requires that list to be accurate and current.

Why Asset Inventory Matters

  • Visibility: The inventory shows what is on your network and where the security gaps are.
  • Risk management: You can assess risk and fix vulnerabilities on the assets you know about.
  • Compliance: The inventory meets the regulatory requirement and gives you evidence for reports.

What to Track in Your Asset Inventory

To comply with NIS2, your asset inventory should include:

  1. Hardware Assets: Servers, workstations, network devices, mobile devices, and IoT devices.
  2. Software Assets: Operating systems, applications, and proprietary software.
  3. Virtual Assets: Virtual machines, containers, and cloud-based services.
  4. Network Components: Routers, switches, firewalls, and access points.
  5. Data Assets: Sensitive information repositories and databases.

How to build the inventory on-premise

Cloud tools are flexible. An on-premise inventory keeps the data inside the plant and under your control. These steps set one up:

Step 1: Define Asset Categories

Sort assets into groups such as hardware, software and network components. Categories make the inventory faster to build and show which groups are missing.

Step 2: Use Automated Tools

Deploy tools that scan the network and record what they find. The tools should discover both managed and unmanaged devices, so no device is left off the list.

Step 3: Update and Audit the Inventory

Schedule regular updates and audits. Run periodic scans and check a sample by hand to confirm the data is correct.

Step 4: Connect the Inventory to Your Security Systems

Connect the inventory to your intrusion detection system (IDS) and your security information and event management (SIEM) system. Alerts then name the asset involved, which speeds up incident response.

Step 5: Document and Report

Record the details, owner, location and known risks of each asset. Set up reporting procedures that match the NIS2 requirements.

Best Practices for Asset Management

  • Assign an owner: Name one person responsible for each asset or group of assets.
  • Control who edits the inventory: Use role-based access control so only authorized staff can change asset records.
  • Train your teams: Teach IT and security staff the inventory procedures and the NIS2 requirements.

Common problems and how to fix them

Challenge 1: Data Silos

Solution: Keep one inventory that pulls in data from every source, so every team works from the same list.

Challenge 2: Rapid Addition of New Device Types

Solution: Choose an inventory system that can record new types of assets, such as IoT devices and cloud services, as you add them.

Challenge 3: Resource Constraints

Solution: Rank inventory work by risk and handle the high-risk assets first.

What to do next

NIS2 compliance starts with knowing what you have. Run a network discovery scan this week, compare the results with your current inventory, and document every gap. Then automate: schedule recurring scans, assign asset owners, and connect the inventory to your incident response process. Every other NIS2 control depends on an accurate, current inventory.


For more NIS2 resources, sovereign deployment options, and compliance guides, visit the NIS2 Compliance for On-Premise OT hub.

Other Articles

Cold ChainOT Security

CISA Fact Sheet on Industrial Refrigeration and Cold Chain Controllers: The Eight Mitigations as a Checklist

On November 5, 2026, CISA, the FBI, HHS, USDA and DOT published a joint fact sheet on malicious activity against industrial refrigeration and cold chain monitoring systems. Attackers go after unpatched or internet-accessible temperature controllers and push units into continuous heating and defrost. The fact sheet lists eight mitigations. Most of them come down to taking the controllers off the internet and controlling how the refrigeration contractor connects.

ICS AdvisoriesOT Security

Hitachi Energy TRO600: Unauthenticated File Read Exposes Router Passwords (ICSA-26-302-02)

On October 29, 2026, CISA republished Hitachi Energy advisory 8DBD000224 as ICSA-26-302-02. It covers two CVEs in the TRO600 series of industrial cellular routers: an unauthenticated file read that exposes configuration files and password data, and a port-forwarding bypass that lets a logged-in user reach services meant for localhost only. Version 9.2.2.1 fixes both.

ICS AdvisoriesOT Security

Siemens SIMATIC WinCC, PCS 7 and Process Historian: NTLM Relay With No Fix (ICSA-26-321-08)

CISA's ICSA-26-321-08 republishes Siemens SSA-970803: CVE-2026-58114, an NTLM relay weakness in SIMATIC WinCC V7.5 to V8.1, WinCC Runtime Professional V17 to V21, PCS 7 V9.1, BATCH V9.1, Process Historian and Information Server. An on-path attacker can take over a user's session and run code with that user's rights. No product has a fix, and four will not get one, so the SQL traffic has to be encrypted and the servers closed off from every host that does not need them.