Cybersecurity
A Cyber Incident Response Plan for Mid-Sized Companies
A cyber incident response plan sets out who decides what, who gets contacted, and which steps are taken when an incident happens. This template follows NIST SP 800-61 Rev. 3 for mid-sized companies.
SEO and Content Specialist
8 min read Reviewed by Legia Cybersecurity Team
Short answer: a cyber incident response plan is a document that sets out who has the authority to decide, who gets contacted, how an incident’s severity is classified, the steps taken from detection to recovery, how to communicate internally and externally, and the review after an incident. For a mid-sized company, those six parts fit in a few pages, as long as the plan is printed, known to its owners, and rehearsed.
Most mid-sized companies only realize they have no cyber incident response plan once an incident has already happened: a server will not open, the director’s email account is being used by someone else, or a customer reports that their data is circulating. At that point, important decisions are made in a hurry, such as who may shut down a server or who speaks to customers. The template below helps you write those decisions down in advance, while heads are still cool.
It is based on NIST SP 800-61 Rev. 3, published in April 2025, which replaces Rev. 2 from 2012. The new version is written as a Community Profile of the NIST Cybersecurity Framework (CSF) 2.0, so incident response is no longer treated as a separate activity but as part of everyday cybersecurity risk management.
What changed in NIST SP 800-61 Rev. 3?
NIST SP 800-61 Rev. 3 maps incident response to the six CSF 2.0 Functions instead of the old four-phase life cycle (preparation; detection and analysis; containment, eradication, and recovery; post-incident activity). According to NIST, the reason is that incidents are now more frequent and broader, and recovery can take weeks or months.
| CSF 2.0 Function | Role in incident response | Related part of the plan |
|---|---|---|
| Govern, Identify, Protect | Preparation: policy, roles, asset inventory, safeguards | Roles, contacts, severity levels |
| Detect | Finding and analyzing suspicious events | Criteria for declaring an event an incident |
| Respond | Handling a declared incident | Response steps and communication |
| Recover | Restoring assets and operations | Recovery steps and closure |
| Identify (Improvement) | Lessons from all Functions | Post-incident review |
For a mid-sized company the practical meaning is this: an incident response plan is not just an IT team document. Policy, business decisions, and improvements after an incident are part of it too.
Part 1: Roles and authority
Write down roles, not just names, because people go on leave or change jobs. NIST SP 800-61 Rev. 3 gives the following example roles, and each role should have a backup.
| Role | Responsibility during an incident | Name and backup |
|---|---|---|
| Leadership | Decides on high-impact actions, such as shutting down or rebuilding critical services, and approves announcements | … |
| Incident lead | Coordinates the handling of one incident from start to closure | … |
| Technical handling | Confirms the incident is real, collects evidence, limits damage, finds the root cause, restores | … |
| Asset owner | Owner of the affected system, data, or business process; sets recovery priorities | … |
| Legal | Assesses notification obligations and contracts with third parties | … |
| Communications | Prepares statements for customers, partners, and the media | … |
| HR | Involved if an employee is suspected, or if employee accounts need to be revoked | … |
| Third parties | Cloud, hosting, or internet providers, or a contracted incident response provider | … |
The part most often missed is authority. Write down who may disconnect the network, shut down a server, or revoke access without waiting for a meeting. NIST recommends that an incident response policy states which roles have the authority to confiscate, disconnect, or shut down technology assets.
Part 2: Emergency contact list
The contact list must be readable when office systems cannot be reached, so keep a printed copy and a copy outside the office network.
- Internal: leadership, incident lead, IT team, key asset owners, legal, communications. List two ways to reach each person, for example a phone number and a personal messaging app.
- Service providers: internet provider, cloud and hosting, application vendors, and network equipment vendors, with customer or contract numbers.
- Incident handling: the provider contracted to help with incident handling, if any. Record the contract number and how to request help.
- Other external parties: legal counsel, the insurer if the policy covers cyber risk, and the authorities that must be notified under the rules that apply to your company.
Check the list every six months, or whenever someone in a key role changes.
Part 3: Incident severity levels
Severity determines how fast an incident is handled and who must be involved. NIST recommends that incidents are not handled first come, first served, but based on risk factors, including asset criticality, impact on business functions, impact on data, the observed stage of the attack, and how easily it can be recovered.
An example of four levels (adapt it to your company):
| Level | Example situation | Who is involved |
|---|---|---|
| Critical | A core service has stopped, ransomware is spreading, or customer personal data is suspected to have leaked | Leadership, incident lead, legal, communications, third parties |
| High | One important system is disrupted, or an admin account is suspected to be taken over | Incident lead, technical team, asset owner, leadership informed |
| Medium | One device is infected and already isolated, with no sign of data leaving | Technical team, asset owner |
| Low | A failed attack attempt, a phishing email reported before it was clicked | Technical team, recorded |
Also define the criteria for declaring an event an incident, who declares it, and when its level is raised.
Part 4: Response steps
The steps below follow the Detect, Respond, and Recover Functions. For the incident types most likely to happen, write more detailed procedures (playbooks). For example, the first-hour steps for ransomware are in the article What to Do First When Your Office Is Hit by Ransomware, and handling a device used by a botnet is in the article Office Devices Turned Into a Botnet.
- Receive and check the report. Confirm the event is real, estimate its severity, and appoint an incident lead.
- Record from the start. Times, devices, accounts, actions taken, and who took them. These notes are used for analysis, notification, and review.
- Limit the damage. Isolate the affected devices or accounts according to the authority in Part 1.
- Activate other plans if needed, such as the business continuity or disaster recovery plan.
- Find and close the entry point before restoring systems, so the same gap cannot be used again.
- Restore from backups that have been checked. NIST recommends checking backups for signs of compromise and corruption before use, and restoring essential services in the right order.
- Confirm the system runs normally together with the asset owner, then monitor it for a while.
- Declare the incident closed based on the agreed criteria, and complete the documentation.
Part 5: Internal and external communication
NIST SP 800-61 Rev. 3 divides incident communication into four types: coordination among the parties handling the incident, formal notification to affected parties and regulators, public communication, and voluntary sharing of threat information. For each, write down:
| Type | What the plan states |
|---|---|
| Internal coordination | The channel used if office email is suspected to be compromised, the schedule of status reports to leadership |
| Formal notification | Who assesses notification obligations, who signs, the letter template |
| Public communication | A single spokesperson, statements already approved by legal |
| Third parties | When cloud providers, vendors, or partners are informed under the contract |
If the incident involves personal data, Law No. 27 of 2022 on Personal Data Protection (UU PDP), Article 46, requires the data controller to give written notice no later than 3 x 24 hours to the data subjects and the oversight institution. The notice must at least state the data exposed, when and how it was exposed, and the handling and recovery efforts. Because the deadline is short, prepare the letter template before an incident.
Part 6: Review after an incident
NIST recommends an after-action report that documents the incident, the response and recovery actions taken, and the lessons learned. For a mid-sized company, one review meeting with five questions is usually enough:
- What happened, and when was it first detected?
- Which parts of the plan worked, and which did not?
- What was the root cause, and has it been closed?
- What needs to change in the plan, the contact list, or the safeguards?
- Who owns each improvement, and what is the deadline?
Rev. 3 also stresses that lessons should be shared as soon as they are identified, rather than waiting until recovery is complete.
Testing the plan before you need it
A plan that has never been rehearsed usually fails on small things: a phone number that is no longer active, or nobody knowing who is authorized to shut down a server. A one-to-two-hour tabletop exercise is enough to find them: take one scenario, for example ransomware on the file server, then walk through the plan step by step on paper. CISA provides exercise packages like this that can serve as sample scenarios.
Security testing also helps with preparation. Legia provides Penetration Testing and Vulnerability Assessment to find gaps before attackers use them. To be clear, Legia does not provide 24-hour monitoring or on-call incident handling. The “incident handling provider” entry in your contact list therefore needs to be filled by another party, or handled by your internal team. The scope of Legia’s services is on the Cyber Security page.
Frequently asked questions
How long should an incident response plan be for a mid-sized company?
A few pages for the six parts above, plus one to three playbooks for the incidents most likely to happen. A concise plan is more likely to be read and followed during an incident.
Who should own this document?
Leadership approves it and sets the authorities, while the person responsible for IT or security maintains its content. Asset owners and legal also review it, because decisions during an incident affect operations and legal obligations.
Does a company without a security team still need this plan?
Yes. A company without a security team needs a written contact list, authorities, and steps the most, because nobody is used to handling incidents. NIST notes that incident handling can be done by in-house staff, by a contracted party, or by a party called in when needed.
How often should the plan be updated?
After every incident or exercise, and whenever there is a major change in systems, service providers, or the people in key roles.
Sources
- NIST, SP 800-61 Rev. 3: Incident Response Recommendations and Considerations for Cybersecurity Risk Management (April 2025)csrc.nist.gov
- Text of Article 46 of Law 27/2022 on Personal Data Protectionpasal.id
- CISA, Cybersecurity Incident and Vulnerability Response Playbookscisa.gov
- CISA, Tabletop Exercise Packagescisa.gov

