Define the scope and assessment context
Specify the legal entity, covered services, information systems, business owner, assessment date and relevant national law. Include physical and supplier dependencies where failure could affect the services.
The Directive uses an all-hazards framework in Article 21(1). Consider accidental failures and environmental disruption as well as malicious cyber activity. Identify assumptions and information gaps instead of silently treating them as low risk.
Describe risk scenarios precisely
For each risk, identify the asset or service, threat event, relevant weakness and potential consequence. A scenario such as loss of privileged identity access during an identity-platform outage is more actionable than a row labelled simply cybersecurity risk.
Consider confidentiality, integrity, availability and authenticity as appropriate. Record dependencies such as cloud providers and operational technology rather than assessing every asset independently.
Score likelihood and impact consistently
Choose documented assessment scales supported by understandable criteria. Describe what each likelihood level means and tie impact to measurable service disruption, safety concerns, information exposure or contractual consequences.
NIS2 does not mandate a single numerical risk matrix for every entity. Avoid treating arithmetic precision as evidence that uncertain probabilities are known, and explain the basis for material ratings.
Record controls and decide treatment
List safeguards already operating and distinguish proposed measures from implemented ones. Record residual risk and the decision to mitigate, avoid, transfer where applicable or accept a risk within approved authority.
For every action, name an owner, due date and measure of successful implementation. A risk may remain open while a mitigation project is underway; do not prematurely describe planned controls as active.
Connect reassessment with evidence and oversight
Retain evidence references, review decisions, control tests and management approvals. Reassess after incidents, major system changes, new suppliers, changes in exposure or updates to applicable law.
Use the risk register to inform Article 21 gap remediation, management reporting and testing schedules. The template is an aid to a real decision process, not a legal certificate.
Questions on the text
Does this template provide a binding NIS2 compliance finding?
No. It structures a documented preliminary assessment that requires review against applicable legislation and relevant facts.
Does NIS2 prescribe one scoring methodology?
The Directive requires appropriate and proportionate risk-management measures; the assessment approach must suit the circumstances and applicable rules.
When should the assessment be revisited?
Review it after material changes to services, risks, corporate structure or the legal framework.