Identify relevant assets and dependencies
Consider applications, cloud resources, network equipment, endpoints, information repositories, backups and operational technology. Identify dependencies between assets and the covered services they support.
The security value of an asset is not determined by purchase price. A small authentication or routing component may be essential to the availability of a much larger service.
Assign responsibility and classify criticality
Record accountable owners, operational purpose, hosting arrangements, important suppliers and the consequences of compromise. Asset records should support decisions about access, vulnerability handling, monitoring and restoration.
Use classification that reflects confidentiality, integrity, availability and service impact. Do not treat an inventory containing only equipment serial numbers as a complete risk picture.
Update records throughout the lifecycle
Connect procurement, deployment, cloud provisioning, maintenance and disposal processes to the asset register. Compare inventory entries with discovery records and confirmations from service owners.
Industrial equipment may be sensitive to active scanning. Use safe discovery methods and document blind spots rather than excluding them silently.
Link inventory with protective controls
Use asset data to identify systems requiring patches, restricted administration or resilient backup arrangements. Link suppliers to the systems they operate so security events can be escalated promptly.
Identify unsupported technology and missing ownership as explicit risks, with accountable actions and proportionate compensating safeguards.
Verify coverage and secure disposal
Sample inventory entries against live systems, investigate unregistered resources and record the date and limits of verification. A complete-looking register can still omit important cloud or supplier assets.
When retiring assets, remove access and credentials, securely handle stored information, and update service dependency records. Check applicable Member State requirements.
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.