Identify services that must be maintained or restored
List the services in scope, their owners and the business processes and systems on which they depend. Include identity systems, network connectivity, specialist staff, suppliers and physical facilities rather than assessing a server without its operating context.
Record the consequence of interruption for recipients, safety, contractual obligations and dependent organisations. Recovery priorities should follow this impact analysis rather than the age or purchase cost of equipment.
Define recovery objectives and practical dependencies
Set recovery time and data-loss objectives for material services, and obtain accountable approval where disruption would be significant. Check whether documented objectives reflect actual technical capacity, supplier contracts and staffing.
An objective is not evidence that restoration can meet it. Examine whether encryption keys, credentials, configuration backups and necessary communications remain available when primary facilities or identity systems fail.
Review backup protection and restoration
Document which data and configurations are backed up, the frequency, retention, integrity checks and protection against deletion or alteration. Include systems operated by suppliers when their recovery responsibilities affect the covered service.
Test restoration rather than assuming successful backup-job notifications prove recoverability. Capture the tested scope, elapsed time, missing dependencies, result and remediation decision.
Prepare crisis decisions and communications
Assign incident leadership, decision authority, communications ownership and escalation routes. Prepare alternatives for outages of ordinary email, telephone or collaboration systems, with controlled access to necessary contact information.
Exercise scenarios involving ransomware, regional outages and unavailable third-party services. Coordinate cybersecurity incident handling and business continuity without assuming every operational disruption automatically meets Article 23 significance thresholds.
Verify resilience and review the checklist
Conduct proportionate exercises, document failures and confirm corrections through re-testing. Track review dates and triggers such as new critical services, mergers, supplier changes and incidents.
Article 21(1) calls for appropriate and proportionate measures under an all-hazards approach. Applicable national legislation and sector rules may add details; a completed checklist alone does not prove compliance.
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.