Incident Response Plan – how companies build a practical plan for cyber incidents
An incident response plan describes how an organization acts from the first signs of a cyber incident until operations are stable, evidence is secured, mandatory reporting is completed, and lessons learned are translated into action. The plan should be concise enough to be used under stress, but detailed enough to eliminate hesitation regarding roles, communication channels, and decision-making.
What should an incident response plan cover?
The plan should apply to events that may affect the confidentiality, integrity, availability, or authenticity of the organization's systems and information. Examples include ransomware, account hijacking, data leaks, denial-of-service attacks, compromised suppliers, misconfigurations, sabotage, and major operational disruptions.
Define a single entry point for alerts, even when an event is uncertain. Employees should not have to determine whether something is legally an "incident" before it can be reported internally.
Roles and decision mandates – decide before the incident
Incidents often escalate when everyone is waiting for the same manager. Therefore, assign roles in advance. A smaller organization can combine several roles, but the responsibilities still need to be clear.
| Role | Responsibility |
|---|---|
| Incident Lead | Coordinates situational awareness, priorities, decisions, and meeting rhythms. |
| Technical Lead | Analysis, containment, logs, remediation, and recovery. |
| Business Owner | Assesses business impact, critical services, and acceptable downtime. |
| Legal/Data Protection | Assesses reporting and notification obligations as well as contracts. |
| Communications | Coordinates internal and external information. |
| Management | Makes decisions outside the incident team's mandate. |
Also document backups, emergency numbers, and how the incident team will convene if standard communication systems are unavailable.
Eight-step incident flow
- Detect and register. Create an incident ID, time, reporter, and initial observation.
- Triage. Quickly assess which systems, data, users, and services may be affected.
- Classify and escalate. Set preliminary severity levels and activate the correct roles.
- Contain. Limit the damage without unnecessarily destroying evidence or complicating recovery.
- Analyze. Determine the likely cause, timeline, point of entry, and scope.
- Remediate. Remove the cause, close vulnerabilities, and verify that the threat is gone.
- Recover. Restore services in a controlled manner and strengthen monitoring.
- Post-analysis. Document root cause, decisions, lessons learned, and improvement measures.
Create a simple classification model
Classification needs to support decision-making, not become an academic scoring model. For example, assess:
- if critical operations are down,
- how many users/customers are affected,
- if personal data or other sensitive information may have been exposed,
- if the attacker has privileged access,
- if the incident is spreading,
- if suppliers or other organizations are affected,
- if regulatory reporting may be triggered.
Decide which level automatically activates management, legal, data protection, or an external incident partner.
Preserve logs and evidence without stopping the response
Under time pressure, it is easy to delete or overwrite important information. The plan should therefore specify who secures relevant logs, snapshots, timelines, emails, account events, and other technical documentation. Document who did what and when.
The need for evidence must be balanced against the requirement to limit ongoing damage. In severe incidents, external forensic expertise may need to be activated early.
Communication and external reporting
Create separate contact lists for authorities, the incident response provider, cyber insurance, critical IT suppliers, management, and communications. Prepare templates for initial internal status reports and decision points.
For organizations covered by the Cybersecurity Act, special rules apply regarding the reporting of significant incidents. The law requires an initial notification no later than 24 hours after the operator becomes aware of the incident, followed by an incident report according to the deadlines applicable to the type of operation. The details are covered separately in the guide on NIS2's 24/72-hour flow.
Recovery is more than just switching systems back on
Define criteria for when a service may be reopened. Verify that the vulnerability has been fixed, that privileged accounts have been secured, that restored data is reliable, and that monitoring is reinforced for a period.
Connect the recovery order to the organization's BIA and continuity plan. Read BIA step-by-step and what a continuity plan should contain.
Post-analysis: make learning mandatory
After the incident, the organization should document the root cause, what worked, what delayed the work, and which controls need to change. Every action should have an owner and a deadline. Then, follow up to ensure it has actually been completed.
Test the plan before it is needed
An incident plan that has never been practiced almost always contains incorrect phone numbers, unclear mandates, or assumptions about systems that no longer exist. Conduct at least recurring table-top exercises where management, IT, business units, and relevant support functions handle a realistic scenario.
Vary the scenarios: ransomware, a compromised SaaS provider, a leaked admin account, or an extended outage. Update the plan after each exercise.
Checklist for the plan
- A single clear internal alarm path
- Roles, substitutes, and mandates
- Contact details for outside business hours
- Severity levels and escalation criteria
- Steps for containment, analysis, and recovery
- Procedures for logs and evidence
- Decision point for NIS2 and other authority reporting
- Decision point for GDPR/personal data breach
- Internal and external communication responsibilities
- Connection to BIA and continuity plan
- Post-analysis with assigned improvement measures
- Exercise and update intervals

Do you need to document the incident flow?
Mallbutiken’s NIS2 Template Package 2026 contains integrated templates for incident management, reporting, risk management, continuity, and supplier security, among others. Store price: 199 SEK.
See the NIS2 template packageThree reporting tracks: cybersecurity law, GDPR and DORA
A single cyberincident may require several independent legal assessments. Record when the organisation became aware, who owns each report and why the event is or is not reportable.
- NIS2/Swedish Cybersecurity Act: A significant incident at an entity in scope requires an early warning within 24 hours and generally an incident notification within 72 hours of awareness. Trust service providers have 24 hours for the latter too. A final report is usually due within a month after notification, or an interim report if ongoing. See NCSC's NIS2 reporting guidance.
- GDPR: A personal data breach is normally reported to the Swedish data authority within 72 hours of awareness unless it is unlikely to pose a risk to individuals' rights and freedoms. Assess notification of affected individuals separately. See the Swedish data protection authority's breach guidance.
- DORA: Financial entities in scope may need to report major ICT incidents to the Swedish financial supervisor under different rules and deadlines. NIS2 time limits are not enough by default. See the Swedish financial supervisor's DORA instructions.
For internal command, decisions, communication, evidence and recovery, consider the Incident Response & Cyber Crisis templates. An internal plan does not replace filing reports through the required official channel.
Related guidance
Also read NIS2 security measures, incident reporting 24/72 hours, and continuity plan.
Sources and further reading
This guide provides general information. The incident plan needs to be adapted to the organization's systems, operations, contracts, and applicable reporting requirements.
Templates in this article
Explore the topic
Business guides – contracts, HR, AI & complianceNIS2 incident reporting – 24 hours, 72 hours and final report
This is how incident reporting works under the Cybersecurity Act: notification within 24 hours, incident report within 72 hours, and a final report...
Business guides – contracts, HR, AI & complianceBIA – how to conduct a Business Impact Analysis step by step
A BIA identifies which activities and resources the organization must be able to restore first following a disruption. Here you will find a practic...
Business guides – contracts, HR, AI & complianceContinuity plan – what should it contain and how is it developed?
A business continuity plan describes how critical operations should continue or be restored in the event of disruptions. See what the plan should i...




