Start with covered services and material assets
Define the legal entity and regulated services to be considered. Identify systems, devices, applications, network equipment, cloud resources, backups and information repositories that materially support them.
Do not omit assets operated by suppliers merely because they are not owned by the entity. Record visibility limitations and contractual responsibilities without implying direct management rights over a provider's infrastructure.
Choose fields with an operational purpose
Recommended fields include asset identifier, type, service dependency, responsible owner, hosting location, criticality, lifecycle state, important supplier and last verification date. Technical attributes such as software version or authentication configuration can be added where maintained reliably.
Avoid collecting confidential credentials or cryptographic keys inside the asset register. Use access-controlled references to approved systems for sensitive details.
Assign classifications and control responsibilities
Assess how loss of availability, integrity or confidentiality could affect the supported service. Link classification to access control, vulnerability response, monitoring, recovery and disposal decisions.
A low-cost component may be critical if it enables identity verification or remote administration. Set inventory priorities by risk and dependency, not only financial valuation.
Reconcile the register with real environments
Compare procurement and configuration records, cloud inventories and suitable technical discovery. For sensitive industrial systems, choose safe inventory methods rather than performing intrusive scans without authorisation.
Sample records against live systems and investigate unidentified resources, obsolete entries, missing owners and gaps in cloud coverage. Document what could not be verified.
Maintain the lifecycle and evidence trail
Connect provisioning, change management, service migration and retirement to inventory updates. Assign owners for disputed records and investigate discrepancies found during incidents or recovery exercises.
Retain dated assurance evidence, corrections and any relevant exception decisions. The template is useful only when the register remains accurate enough to support real cybersecurity decisions.
Questions on the text
Does completing the template prove NIS2 compliance?
No. Templates support assessments and decisions, while applicable national rules and operational evidence determine the relevant conclusions.
Who should review and maintain the information?
Assign accountable owners and periodic review, escalating material risks or decisions to the appropriate management body.