Verify legal scope and accountability
Confirm the entity's jurisdiction, essential or important classification, competent authority, applicable national law and any relevant sector-specific rules. Identify the management body and control owners.
The corporate group may include different legal entities with different classifications. Record the rationale for each assessed entity rather than assuming group-wide uniformity.
Review cybersecurity risk management
Check whether Article 21 risk assessment, incident handling, continuity, supplier security, vulnerability handling, effectiveness review and access controls have operational owners and current evidence.
Match each measure to the services it protects. A control marked complete without tested implementation or known limitations can overstate readiness.
Test incident and regulatory notification decisions
Confirm escalation contacts, significant-incident assessment criteria, reporting channels and decision records. Exercise the distinction between technical response and mandatory notification.
Test alternate contacts where normal communications could fail. Keep the dates and facts associated with exercise results instead of implying simulated notifications were actual filings.
Review audit and information-request procedures
Identify who authenticates authority communications, gathers documents, manages sensitive material and tracks deadlines. Distinguish supervisory approaches under Articles 32 and 33.
Ensure relevant teams know where evidence is held and who can authorise disclosure. The process should support truthful responses, not scripted claims of perfect compliance.
Close or escalate material findings
Examine overdue vulnerabilities, untested recovery arrangements, unaddressed supplier risks and previous audit findings. Require accountable plans, compensating measures where justified and verified retesting.
Management should understand major unresolved exposure. A risk acceptance record does not guarantee that an inadequate measure becomes compliant.
Reassess after material changes
Review readiness following incidents, supplier transitions, mergers, new national implementing rules or changes in the service portfolio. Record the review date and next decision owner.
NIS2 does not prescribe one universal readiness checklist or annual supervisory audit for every entity. Use this process as a practical aid, not a substitute for national legal requirements.
Questions on the text
Does an incident automatically prove an NIS2 infringement?
No. An infringement requires assessment of the applicable legal duties and relevant facts.
Is a documented policy sufficient evidence?
Not on its own. Implemented controls, appropriate tests and risk decisions provide important additional evidence.