Set the inventory boundary
Start with the legal entity, covered services and supporting technology. Include cloud systems, backups, networking, endpoints and supplier-operated dependencies where relevant.
Document assets for which direct visibility is limited. Outsourcing a service does not make its dependencies irrelevant to risk assessment.
Choose fields people can maintain
Useful fields may include asset identifier, owner, location or hosting environment, supported service, lifecycle status, criticality and supplier. Add software details and protection status where reliable.
Avoid collecting fields that no team will update. Protect technical identifiers and management information from unnecessary distribution.
Reconcile discovery with owner knowledge
Use suitable configuration records, procurement data, cloud inventories and safe technical discovery. Ask service owners to confirm which assets perform critical functions.
Track discrepancies and systems that cannot be assessed safely. A discovered network address is not necessarily an accurately classified asset.
Connect assets to cybersecurity work
Associate records with vulnerability handling, access control, supplier oversight, continuity and incident response. When new vulnerabilities are announced, the inventory should help locate affected systems and owners.
Capture missing dependencies discovered in recovery exercises, incidents or architecture changes so future decisions are based on more complete information.
Test accuracy and govern changes
Sample live systems and confirm their entries exist; sample inventory entries and verify that the systems still exist. Investigate orphaned records and gaps in critical services.
Assign update responsibility, maintain review evidence and verify corrective action. Article 21(2)(f) supports assessments of effectiveness, while Article 21(2)(i) includes asset management.
Points of clarification
Does NIS2 prescribe one mandatory product or inventory format?
No. Control design should reflect applicable national and sector-specific rules and the organisation's risks.
Is an approved policy enough to prove effectiveness?
No. Operational evidence, testing and corrective actions help demonstrate how the controls work.