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.
HomeArticlesNIS2 Crisis Communication Plans
Business Continuity / 2026-10-09

NIS2 Crisis Communication Plans

Crisis communication supports coordinated decisions during a disruptive cyber incident. Under Article 21(2)(c), crisis management is part of NIS2 cybersecurity risk-management measures. A communication plan should clarify roles, audiences, approval processes and reliable alternatives when normal channels are disrupted.

Distinguish operational communication from regulatory reporting

Internal escalation enables decision-makers to understand the impact and authorise recovery actions. Customer, supplier and staff messages address operational needs. Formal NIS2 incident notification under Article 23 is a separate legal process with its own conditions and timing.

Do not assume every disruption meets the significant-incident threshold. Equally, a decision to delay a public statement must not obstruct any mandatory authority notification.

Specify who communicates what

Assign roles for incident command, legal review, security facts, leadership decisions, customer communication and regulatory liaison. Document deputies for unavailable contacts and define who may approve urgent messages outside business hours.

Avoid a single shared distribution list that exposes unnecessary incident information. Teams need dependable channels and clear boundaries for information that can be disclosed.

Prepare channels that survive outages

Maintain out-of-band contact methods for key personnel, critical suppliers and the competent authority or CSIRT where relevant. Test access to contact details when corporate identity or messaging platforms are unavailable.

Check that alternate channels meet security and confidentiality requirements. A private messaging application should not become an uncontrolled substitute for incident records.

Make messages accurate and useful

Initial communications should distinguish verified facts from working assumptions. Explain the service impact, available workarounds and where stakeholders can receive updated instructions. Avoid unsupported assurances about containment or restoration times.

Keep a log of audience, message version, approval, delivery time and corrections. The same incident may require distinct technical instructions for staff and carefully scoped service information for customers.

Rehearse and update the plan

Tabletop exercises should test conflicting reports, absent approvers and the loss of normal communication tools. Coordinate with the incident response and continuity plans so recipients know how to act on messages.

Review templates and contacts after organisational changes or major incidents. Check applicable national NIS2 law, data protection duties and contractual notification provisions without treating their reporting timelines as interchangeable.

Questions on the text

Does every cyber incident require a public announcement under NIS2?

No. Communication decisions depend on the incident, relevant legal duties, competent authority directions and the people affected.

Can a crisis communication plan replace NIS2 Article 23 reporting?

No. Significant-incident notifications require a distinct assessment and compliance with the applicable reporting procedures.

More from the Desk

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.