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 Disclosure Policy Under NIS2
Secure Acquisition Development Vulnerabilities / 2026-10-10

Vulnerability Disclosure Policy Under NIS2

Vulnerability disclosure arrangements help researchers, customers and suppliers report security weaknesses safely and help organisations coordinate fixes. NIS2 Article 21(2)(e) includes vulnerability handling and disclosure; Article 12 also provides an EU framework for coordinated vulnerability disclosure.

Define what can be reported and by whom

Describe the products and services in scope, the contact channel and the basic information that helps reproduce an issue. Make clear which systems are excluded and whether third-party hosted components require separate contact.

A disclosure policy should not encourage unauthorised testing or imply legal immunity that the organisation cannot grant. Coordinate wording with legal and security teams.

Provide secure intake and acknowledgement

Maintain an inbox or reporting mechanism monitored by a responsible team. Protect sensitive proof-of-concept details and personal information from unnecessary disclosure, and acknowledge reports when practicable.

Ensure reports received through customer support or a supplier are routed to the security function rather than lost in ordinary service queues.

Triage and coordinate remediation

Determine scope, validity, exploitability, impacted services and whether another vendor maintains the affected component. Assign owners, develop mitigations and coordinate a reasonable disclosure timetable.

The appropriate schedule depends on the risk and circumstances. Avoid asserting a universal public-disclosure deadline under Article 21 for all entities.

Engage appropriate coordination structures

Article 12 provides for coordinated vulnerability disclosure arrangements and CSIRTs designated as coordinators. Organisations may seek assistance when a vulnerability spans vendors or coordination is difficult.

Consider the role of relevant national CSIRTs and any competent authority guidance. Disclosure of a vulnerability does not automatically mean a significant incident has occurred.

Publish responsibly and keep records

When publishing advisories, provide affected versions, impact, available fixes or mitigations and a suitable contact for further reports. Avoid sharing exploit details prematurely when this would unnecessarily increase exposure.

Retain the initial report, technical assessment, coordination decisions, remediation verification and publication record to demonstrate a managed process.

Review the policy in practice

Exercise intake and escalation, including periods of reduced staffing, and monitor whether the contact channel remains accessible. Improve procedures following difficult cross-supplier cases.

Check the relevant national implementation and provider-specific rules in Commission Implementing Regulation (EU) 2024/2690 when applicable.

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.

Related entries

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.