An independent information publicationDirective (EU) 2022/2555 · The NIS2 DirectiveNot an official publication
The Independent NIS2 Desk
NIS2 Compliance
Independent information on the NIS2 Directive, for the organisations it covers.
HomeArticlesVulnerability Scanning and NIS2: Coverage, Prioritisation and Evidence
Security Testing Audit / 2026-10-09

Vulnerability Scanning and NIS2: Coverage, Prioritisation and Evidence

Vulnerability scanning helps organisations identify known weaknesses in systems and applications, but a scan report does not by itself demonstrate compliance with NIS2. Scanning should be risk-based, authorised, repeatable and linked to remediation and effectiveness assessment.

Why scanning matters to NIS2 assurance

Article 21(2)(e) addresses security in network and information systems acquisition, development and maintenance, including vulnerability handling and disclosure. Article 21(2)(f) requires policies and procedures to assess whether cybersecurity risk-management measures are effective. Vulnerability scanning can provide evidence for both activities when findings are connected to the relevant assets and risks.

The Directive does not impose one universal scanner, score threshold or monthly scanning interval on every covered entity. An organisation must check applicable national legislation and sector-specific rules before treating a chosen schedule as a legal obligation.

Identify the systems that must be visible

Start with an inventory of internet-facing services, internal infrastructure, applications, cloud resources and operational technology that support covered services. Define who owns each environment and whether scanning access is authorised. A tool that reports no findings against half the estate leaves an important assurance gap.

Record exclusions, systems that cannot tolerate active probing and resources controlled by suppliers. For sensitive industrial equipment, use passive discovery or supplier-supported assessment where active testing could interrupt operations. Document the reason and any compensating controls.

Choose scanning methods for the environment

Network scanning, authenticated host assessment, software composition analysis, container image review and cloud configuration analysis identify different classes of weakness. An unauthenticated external scan may detect exposed ports and some vulnerable services but cannot reliably establish the patch state of every internal component.

Use authenticated checks where appropriate and protect scanning credentials. Validate signatures and tool configuration, record the scan date and scope, and retain evidence of failures to reach intended targets. A scanner's reported severity is an input to risk assessment, not a substitute for business context.

Prioritise exposures instead of counting findings

Assess whether a vulnerability is exploitable, whether the affected asset is reachable, what service it supports and whether reliable mitigations exist. A high-scoring weakness on an isolated nonproduction machine may require different treatment from an actively exploited issue on a critical service.

Assign remediation owners and deadlines using documented risk criteria. Track exceptions, planned changes and temporary mitigations. When a patch cannot be applied promptly, record the residual risk and the basis for any acceptance decision rather than silently removing the item from the report.

Verify remediation and preserve meaningful evidence

Rescan after remediation where safe and appropriate. A changed ticket status or a software update notification does not establish that the identified exposure has been removed. Investigate persistent findings and scan failures, including whether vulnerable software remains in another environment.

Retain inventory coverage, methods, scan results, evidence of triage, change records and retest outcomes. Report gaps in asset coverage separately from the number of vulnerabilities resolved, since an improving closure rate can mask disappearing scan coverage.

Points of clarification

Does NIS2 prescribe one universal assessment frequency?

No. Article 21 does not set a single frequency for every entity and technique. The programme should be risk-based and reflect applicable national or sector-specific requirements.

Can evidence of completed activity prove a control is effective?

Not by itself. Effectiveness requires evidence that the measure achieves its intended security outcome in the relevant environment.

What should management receive?

Management should receive the scope, material findings, exposure, limitations, corrective owners and evidence of verified closure.

Further entries on this subject

The texts relied on

General editorial guidance only: it does not determine your organisation's legal obligations. See our editorial policy for how this site works and corrects errors.