A Crisis Is More Than a Technical Incident
Incident response often begins with detection, containment and technical investigation. Crisis management becomes particularly important when decisions affect service continuity, external communications, safety, legal obligations or multiple parts of the organisation. The same event can require both processes.
A sustained outage of a critical supplier may require executives to choose between reduced operations and a risky restoration route. The crisis team should understand who owns that decision and what facts must be reported before it is made.
Define Activation Triggers and Authority
A useful crisis process names the conditions for escalation, the person able to declare a crisis, alternates if that person is unavailable and the responsibilities of each team. Activation triggers can include prolonged service unavailability, widespread dependency failure or material uncertainty about compromised systems.
Avoid criteria so vague that every incident becomes a crisis. Establish thresholds appropriate to the organisation and make it possible to escalate before a complete impact assessment is available. Record decisions and rationale as the situation changes.
Coordinate Technical and Business Work
Security responders investigate threats and contain affected systems. Operations personnel establish recovery options. Legal and compliance teams assess reporting duties. Communications teams coordinate messages, while leadership chooses among material business risks. A crisis plan should connect these activities without diluting accountability.
The organisation also needs a reliable record of what is known, unknown and awaiting confirmation. Use a defined information cadence and assign owners to critical questions, rather than letting parallel teams make contradictory assumptions.
Build Communications That Survive an Outage
An internal messaging platform may be unavailable during a major cyber incident. Identify alternate contact channels and protect sensitive information shared through them. Plan communication with employees, affected customers, suppliers and relevant authorities as the situation warrants.
For entities covered by Regulation 2024/2690, Annex 4.3 specifies communication arrangements with competent authorities and a process for handling information from CSIRTs or authorities. NIS2 incident notification under Article 23 remains a separate requirement and should be assessed through the appropriate reporting process.
Practice Decisions, Not Just Meeting Attendance
Tabletop exercises can test whether the crisis team knows who activates the plan, when to accept downtime, how to handle incomplete facts and when to notify stakeholders. Include scenarios involving unavailable executives or conflicting supplier information.
Evaluate the timing and quality of decisions and communications. Capture unclear responsibilities, inaccurate contacts and assumptions that failed. Revise and retest the plan after material incidents or changes; Annex 4.3 also includes review and testing rules for its covered entities.
Keep Governance Evidence and National Context
A dated crisis management plan, escalation matrix, contact arrangements, exercise results, decision logs and follow-up actions help demonstrate that arrangements are operational rather than merely theoretical. Identify who approves the process and who keeps it current.
Read Article 21 with national implementing requirements. Do not assume that every illustrative measure in ENISA guidance is a universal statutory command, or that having a crisis team removes any separate incident-reporting duty.
Questions on the text
Does NIS2 require every covered entity to use an identical crisis team?
No. The framework is risk-based. Specific responsibilities must match the applicable legal rules and the organisation’s operating model.
Is crisis management the same as incident reporting?
No. Crisis management addresses decisions and coordination during disruption; incident reporting concerns notifying the relevant bodies under applicable reporting rules.