Establish system ownership and discovery coverage
Link the asset register to business services, system owners, installed software and external providers. Discover weaknesses through vendor notices, assessment tools, testing and responsible external reports. Record limitations where appliances or operational technology cannot be scanned safely.
A long list of scan findings is not evidence of control if critical systems are missing. Assess which environments and dependencies are excluded and why.
Prioritise actual exposure
Evaluate exploitability, network reachability, privileges, affected data and impact on the covered service. Combine technical vulnerability information with business context and credible threat intelligence.
Do not use severity scores as the only trigger. An actively exploited medium-rated flaw in a critical remote-access component may require faster action than an isolated high-rated defect.
Assign remediation paths
Choose a vendor update, configuration correction, access restriction, isolation, replacement or other proportionate mitigation. Assign ownership and target dates according to risk and realistic maintenance constraints.
If a patch could interrupt essential operations, assess and record the tradeoff, compensating measures and the plan for safe deployment rather than leaving the issue indefinitely unresolved.
Verify fixes and monitor exceptions
Confirm that a deployed change has resolved the exposure and has not broken the service. Record exceptions with an accountable approver and reassessment triggers. Escalate overdue critical work.
Retesting should be risk-based: update installation records alone may not show that affected components are no longer exposed.
Handle disclosures and regulatory boundaries
Provide a route for vulnerability reports to reach an accountable team, and coordinate with suppliers where defects affect their products. Vulnerability disclosure differs from significant-incident notification under Article 23.
Retain inventory scope, findings, risk decisions, remediation results and disclosure communications. Check national law and relevant rules for any more detailed procedural duties.
Assess effectiveness and improve
Review recurrence, ageing of unresolved issues, asset coverage and remediation failures. Use results to improve procurement, configuration and secure-development practices.
Article 21(2)(f) addresses assessment of cybersecurity measure effectiveness. Implementing Regulation (EU) 2024/2690 adds detailed requirements for specified categories of providers, not all NIS2 entities.
Questions arising
Does NIS2 prescribe one universal technical process for every entity?
No. The Directive requires appropriate and proportionate measures; additional rules may apply depending on the entity and jurisdiction.
How should exceptions be handled?
Document the exposure, mitigation, accountable approver, review triggers and an actionable route to resolution.