An incident is a question of “when”, not “if”. What separates companies is whether people know what to do at that moment. Ukraine’s cybersecurity law defines cyber incident response as a structured set of actions: preparing for incidents, detecting and analysing them, minimising the damage and preventing recurrence.
Below: what an incident response plan should contain, how to write playbooks for common attacks and how to check that the plan works. Separate requirements for NBFIs are covered in “Cyber incident response plan under NBU rules”.
What an incident response plan is
CISA describes an incident response plan as a written document, formally approved by the senior leadership team, that helps an organisation before, during and after a confirmed or suspected security incident. It sets out roles and responsibilities, key activities and a list of people who may be needed in a crisis.
A plan is not just a technical instruction. It should answer who makes decisions, whom to notify and when, what to tell customers and how to get back to normal operations.
Roles
CISA recommends assigning during an incident:
- an incident manager — coordinates the work, communication and tasks, keeps an eye on the clock and does no technical work themselves;
- a tech manager — the subject matter expert who brings in internal and external specialists;
- a communications manager — for reporters, customers and partners.
Add company management, a lawyer, business process owners and external parties: the SOC, investigators, providers.
Stages of response
NIST’s incident response guidance (SP 800-61 Rev. 3) builds response into overall risk management: preparation, detection, response, recovery. ENISA describes incident handling like this:
- Triage: is it really an incident, how serious is it, who handles it.
- Analysis: what happened, which systems and data are affected.
- Containment: isolate affected systems, block accounts.
- Eradication and recovery: remove the cause and restore operations — see “Disaster recovery: RTO, RPO and a recovery plan”.
- Closing the incident.
- Lessons learned: what to change so it does not happen again.
Playbooks: scenarios for common incidents
A playbook is a step-by-step instruction for a specific type of incident. It saves the most valuable thing — the first minutes. Start with a few of the most likely scenarios:
| Scenario | First steps | More |
|---|---|---|
| Ransomware | Isolate affected systems without switching them off, protect backups | Cyberattacks on business |
| Compromised email or account | Reset the password and sessions, check forwarding rules, warn counterparties | Phishing |
| Suspicious payment or changed bank details | Stop the payment, contact the bank, verify through another channel | Social engineering |
| DDoS attack | Confirm the attack, notify the provider, turn on protection | DDoS attack |
| Lost laptop or phone | Lock the device and accounts, assess what data was on it | — |
In each playbook, record: the signs, the first actions, who decides on isolating systems and stopping services, whom to notify, what to preserve for the investigation.
Communications
- Inside the company: who receives information and through which channel. During an incident, email and chat may be down, so CISA recommends printing the plan and the contact list.
- Customers and partners: a short statement prepared in advance in case reporters or customers ask.
- State bodies: CERT-UA, the cyber police and, for some industries, regulators. NBFIs have their own NBU requirements, and critical infrastructure operators are required by law to report incidents immediately — see “Critical infrastructure: cyber protection rules”.
Preparing for an incident
Following CISA’s recommendations:
- train staff to report suspicious events — and thank them even for false alarms;
- review the plan with a lawyer;
- choose outside investigators in advance;
- review the plan regularly — CISA recommends quarterly;
- run exercises: tabletop exercises where the team walks through a scenario “on paper”.
After an incident
CISA recommends a blameless retrospective: incidents rarely result from one person’s action — they are almost always a failure of the overall system. The retrospective should look at people, processes and technology, and its findings should feed into updated policies and procedures.
The role of the SOC
According to ENISA, the SOC is the first line: it receives all alerts, filters out false ones, escalates real incidents and passes on data for investigation. Without monitoring, a response plan only kicks in once you have learned about an attack some other way. How a SOC is organised: “SIEM vs SOC: the difference for business” and “SOC as a Service or in-house SOC: how to choose”.
Checklist
- The incident response plan is approved by management
- Roles are defined: incident manager, tech manager, communications
- There are playbooks for ransomware, compromised email, fraudulent payments, DDoS
- Contacts and the plan are available without corporate email and network
- It is known whom to notify and when, regulators included
- Outside investigators are chosen in advance
- Exercises are held regularly
- Every incident is followed by a retrospective
How Bereg-IT can help
At a consultation or audit we assess your current response process and help prepare a plan. SOC as a Service takes on collecting and analysing security events, triage and investigation, notifications with a severity assessment and recommended actions, response according to an agreed playbook and regular reports. Who does what is fixed before launch: Bereg-IT proposes and carries out isolation of business-critical systems, and you approve it.
If an incident is happening right now, see the first steps on the “Security incident” page.
The first consultation is free. Send a request and an information security specialist will get in touch.
Sources
- CISA, Incident Response Plan (IRP) Basics (31.01.2024): https://www.cisa.gov/resources-tools/resources/incident-response-plan-irp-basics
- NIST SP 800-61 Rev. 3, Incident Response Recommendations and Considerations for Cybersecurity Risk Management: A CSF 2.0 Community Profile (April 2025): https://csrc.nist.gov/pubs/sp/800/61/r3/final
- ENISA, How to set up CSIRT and SOC (10.12.2020): https://www.enisa.europa.eu/publications/how-to-set-up-csirt-and-soc
- Law of Ukraine “On the Basic Principles of Ensuring Cybersecurity of Ukraine” of 05.10.2017 No. 2163-VIII — Article 1 (in Ukrainian): https://zakon.rada.gov.ua/laws/show/2163-19