[Company name]
Cybersecurity Incident Response Plan
| Organization | [Company name] |
|---|---|
| Document | Cybersecurity Incident Response Plan |
| Document owner | [Owner name], [Owner title] |
| Approved by | [Approver name], [Approver title] |
| Effective date | [Effective date] |
| Version | [Version] |
| Review frequency | Reviewed [Review frequency] and after any significant change |
| Classification | Internal use |
1. Purpose and Scope
This Incident Response Plan ("the Plan") describes how [Company name] detects, responds to, and recovers from cybersecurity incidents. Its goals are to protect people and data, limit damage and cost, preserve evidence, meet legal and contractual obligations, and restore normal operations quickly.
A security incident is any event that actually or potentially threatens the confidentiality, integrity, or availability of company systems or information. Examples include:
- Ransomware or other malware on any company device or server
- A compromised email or user account, including suspicious sign-ins or mailbox rules
- Fraudulent payment requests, changed bank details, or wire fraud (business email compromise)
- Lost or stolen laptops, phones, or storage devices containing company data
- Unauthorized access to, or disclosure of, customer, patient, employee, or financial information
- A security incident at a vendor that holds or can access our data
This Plan applies to all employees, contractors, and service providers, including [IT provider / MSP]. Restoration of systems after an incident follows the IT Disaster Recovery Plan.
2. How to Report a Suspected Incident
Every employee is responsible for reporting suspected incidents immediately. Reporting quickly is always the right choice, even if you are not sure, and even if you clicked something you should not have. No one will be disciplined for promptly reporting an honest mistake.
- Stop. Do not keep working on a device you think is compromised, and do not try to fix it yourself.
- If a device is showing ransom messages or files are being renamed, disconnect it from the network (unplug the network cable and turn off Wi-Fi). Do not turn it off unless instructed.
- Report by phone to [IT contact] at [IT contact phone] and by email (from a different, unaffected device if possible) to [Security reporting email].
- Tell your manager or the IR lead, [Incident response lead].
- Write down what you saw, what you clicked, and the time. Take a photo of the screen if you can.
Drafting note: Post the reporting steps near workstations and include them in onboarding and annual security awareness training. A laminated card with the phone number and security email works well.
3. Incident Response Team
| Role | Assigned to | Responsibilities |
|---|---|---|
| Incident response (IR) lead | [Incident response lead] | Leads the response, declares severity, makes day-to-day decisions, keeps the incident log, and coordinates the team. |
| Backup IR lead | [Backup IR lead] | Acts as IR lead if the primary is unavailable. |
| Executive sponsor | [Approver name], [Approver title] | Approves major decisions: spending, shutting down operations, engaging outside firms, public statements, and any ransom-related discussion. |
| Technical lead | [IT contact] ([IT provider / MSP]) | Investigates, contains, eradicates, and restores systems; preserves logs and evidence. |
| Communications lead | [Owner name] | Prepares and approves messages to staff, clients, vendors, and media; ensures one consistent voice. |
| Legal and insurance liaison | [Legal counsel]; [Cyber insurance carrier] | Advises on legal privilege, notification obligations, law enforcement, and insurance requirements. |
| HR contact | [HR contact] | Handles incidents involving employee conduct or employee data. |
Drafting note: Many cyber insurance policies require you to call their breach hotline first and use their approved forensic firms and breach counsel. Read your policy now and record the requirements here so you do not jeopardize coverage during an incident.
4. Contact Tree
The person who discovers or receives a report calls the technical lead and the IR lead. The IR lead then contacts the rest of the team and outside parties as needed.
| Contact | Organization | Phone | When to contact | |
|---|---|---|---|---|
| [Incident response lead] | [Company name] | [IR lead mobile] | Every suspected incident | |
| [IT contact] | [IT provider / MSP] | [IT contact phone] | [IT contact email] | Every suspected incident |
| Executive sponsor | [Company name] | Severity 2 and above | ||
| Cyber insurance breach hotline | [Cyber insurance carrier] | [Insurer claims / breach hotline] | Severity 2 and above, before engaging outside vendors | |
| Breach counsel | [Legal counsel] | Any possible data exposure | ||
| Bank fraud department | [Bank fraud department contact] | Any fraudulent or suspicious payment, immediately | ||
| FBI Internet Crime Complaint Center (IC3) | ic3.gov | Wire fraud, BEC, ransomware | ||
| Local law enforcement | Theft of equipment, threats, extortion | |||
| Key vendors (line-of-business, payment processor) | If their system or our access to it is involved |
Keep a printed copy of this contact tree off-site. During an incident, assume company email and phones may be compromised or unavailable, and use personal mobile phones for coordination.
5. Severity Levels
| Severity | Description | Examples | Response |
|---|---|---|---|
| 1 - Low | Contained event, no evidence of data exposure or spread | Phishing email reported but not clicked; malware blocked by antivirus | Technical lead handles; logged; reviewed monthly |
| 2 - Medium | Single user or device affected; data exposure possible but unconfirmed | User entered password on phishing site; lost encrypted laptop; single infected PC | IR lead notified within 1 hour; containment the same day |
| 3 - High | Multiple systems or sensitive data affected, or financial loss | Compromised mailbox sending fraud emails; confirmed unauthorized access to client data; fraudulent wire sent | Full team activated; insurer and counsel notified; executive sponsor informed immediately |
| 4 - Critical | Business operations stopped or large-scale data compromise | Ransomware across servers; destructive attack; large data theft | Full team activated around the clock; insurer hotline; DR Plan activated |
When in doubt, classify higher. Severity can be lowered as facts become clear.
6. Response Phases
Phase 1: Preparation
- Keep this Plan, the contact tree, and insurance details current and available offline.
- Maintain protections: MFA, endpoint detection and response, patching, email filtering, and backups with an immutable or offline copy.
- Enable and retain logs from [Email / productivity platform], firewalls, and endpoints long enough to investigate (90 days or more where possible).
- Train employees to recognize and report incidents.
- Run a tabletop exercise at least once a year.
Phase 2: Detection and analysis
- Confirm whether an incident has occurred and what type it is.
- Identify affected users, devices, accounts, and data.
- Assign a severity level and open the incident log.
- Determine whether sensitive data (personal, health, financial, payment card) may be involved.
Phase 3: Containment
- Short-term: isolate infected devices from the network, disable or reset compromised accounts, revoke active sessions, and block malicious senders, domains, or IP addresses.
- Preserve evidence before making changes wherever practical (see Section 11).
- Long-term: apply temporary controls such as additional monitoring or restricted access while the root cause is found.
Phase 4: Eradication
- Find and remove the root cause: malware, malicious accounts, forwarding rules, unauthorized applications, or vulnerable services.
- Patch the vulnerability or close the entry point used by the attacker.
- Reset credentials that may have been exposed, including service and administrator accounts.
Phase 5: Recovery
- Restore systems from known-clean backups following the IT Disaster Recovery Plan.
- Verify systems are clean and working before returning them to users.
- Monitor closely for signs of reinfection for at least 30 days.
Phase 6: Post-incident review
- Hold a lessons-learned meeting within 10 business days of closing a Severity 2 or higher incident.
- Document what happened, what worked, what did not, and the cost.
- Assign owners and due dates for improvements, and update this Plan and training.
7. First 24 Hours Checklist
For any Severity 3 or 4 incident, the IR lead works through this checklist and records the time each item is completed.
- Confirm staff safety and designate a meeting method that does not rely on possibly compromised systems (personal phones, a separate chat).
- Open the incident log and record the time of discovery and who reported it.
- Contact the technical lead, [IT contact], and agree on immediate containment steps.
- Isolate affected systems from the network; do not power off or wipe them unless instructed.
- Disable or reset compromised accounts and revoke active sessions and tokens.
- Call the cyber insurance breach hotline ([Cyber insurance carrier]) before hiring outside firms or making public statements.
- Contact breach counsel ([Legal counsel]) if personal or regulated data may be involved.
- If money was sent fraudulently, call the bank immediately and file a complaint at ic3.gov.
- Confirm that backups are intact and protected from the attacker; disconnect or lock backup access if needed.
- Preserve logs and evidence (Section 11).
- Brief the executive sponsor and agree on the next update time.
- Tell staff what they need to know and what not to discuss outside the company.
- Prepare a holding statement for clients, in case one is needed.
- Do not communicate with the attacker or discuss any ransom without the executive sponsor, counsel, and insurer.
8. Playbook: Ransomware
Signs: ransom notes, files with unusual extensions or that will not open, sudden widespread file changes, security alerts about encryption, or systems that suddenly stop working.
- Disconnect affected devices from the network immediately (network cable and Wi-Fi). Leave them powered on unless the technical lead says otherwise, as memory may contain evidence.
- Declare Severity 4 and activate the full team.
- Protect backups: confirm the immutable or off-site copies are intact and cut off any network path between infected systems and backup storage.
- Call the insurer's breach hotline and breach counsel before engaging forensic or recovery vendors.
- Identify the ransomware variant and scope with the technical lead and any approved forensic firm. Determine whether data was stolen as well as encrypted, since many ransomware groups do both.
- Reset all passwords, starting with administrator, email, remote access, and backup accounts. Require MFA on every account.
- Decide on the recovery path with the executive sponsor: restore from clean backups (preferred) or other options advised by counsel and the insurer.
- Do not pay or negotiate without counsel and insurer involvement. Payments may raise legal issues, and payment does not guarantee recovery or deletion of stolen data.
- Rebuild and restore following the IT Disaster Recovery Plan, restoring from a backup taken before the attacker's first access where possible.
- Evaluate notification obligations if data was accessed or stolen (Section 12).
- Report to the FBI (ic3.gov) as advised by counsel.
9. Playbook: Business Email Compromise and Wire Fraud
Signs: a request to change bank or payment details, an urgent payment request from an executive or vendor, clients reporting odd emails from us, unfamiliar inbox rules, or sign-in alerts from unusual locations.
If money has already been sent
- Call the bank immediately and ask for a recall of the wire or ACH and a fraud hold. Speed matters: the sooner the bank acts, the better the chance of recovering funds.
- File a complaint with the FBI Internet Crime Complaint Center at ic3.gov with transaction details.
- Notify the insurer; many policies treat social engineering or funds-transfer fraud separately, with their own requirements.
Contain the account
- Reset the compromised user's password and revoke all active sessions.
- Confirm MFA is enabled and remove any authentication methods the attacker may have added.
- Check for and remove malicious inbox rules, forwarding addresses, delegates, and connected applications.
- Review sign-in logs and the mailbox audit log in [Email / productivity platform] to determine what the attacker accessed and when.
- Search for other accounts that received phishing from the compromised mailbox and check them too.
Communicate and prevent
- Warn clients and vendors who may have received fraudulent messages, using a phone number you already have on file, not one from the email.
- Review whether the mailbox contained personal or sensitive data that may trigger notification obligations (Section 12).
- Reinforce the payment verification rule: any new or changed payment instructions are confirmed by calling a known phone number, and large payments require a second approver.
10. Playbook: Lost or Stolen Device
- Employee reports the loss to [IT contact] as soon as it is discovered, including when and where it was lost.
- Technical lead locks or remotely wipes the device through [Device management (MDM) tool] and records confirmation.
- Reset the user's password and revoke sessions on the device.
- Confirm whether the device was encrypted and whether it stored sensitive data locally.
- If stolen, the employee files a police report and gives the report number to the IR lead.
- If the device was unencrypted and held sensitive data, treat as Severity 3 and evaluate notification obligations.
11. Evidence and Log Preservation
Evidence helps determine what happened, supports insurance claims, and may be needed for law enforcement or legal proceedings. Unless the technical lead decides otherwise to stop active harm:
- Do not wipe, reimage, or throw away affected devices until evidence has been collected or counsel approves.
- Isolate rather than power off devices where possible.
- Export and save logs: [Email / productivity platform] sign-in and audit logs, firewall logs, endpoint security alerts, VPN and remote access logs, and backup system logs.
- Preserve ransom notes, phishing emails (as attachments, with headers), and screenshots.
- Keep a chain-of-custody record for any device removed from the office: who took it, when, and where it went.
- Record every action taken in the incident log with the time and the person responsible.
12. Notification Considerations
Some incidents create legal obligations to notify affected individuals, regulators, clients, or others. Decisions about notification are made with [Legal counsel], and this section is a reminder, not legal advice.
- Florida: The Florida Information Protection Act (Fla. Stat. 501.171) generally requires notice to affected Florida residents no later than 30 days after a breach of personal information is determined or there is reason to believe one occurred, and notice to the Florida Department of Legal Affairs when 500 or more Florida residents are affected. Counsel should confirm whether and how the law applies.
- Other states: If affected people live in other states, those states' laws may also apply.
- Industry rules: Healthcare, financial services, tax preparers, and businesses that accept payment cards may have additional notification or reporting requirements under federal rules and contracts.
- Contracts: Client agreements, vendor agreements, and insurance policies may require notice within specific timeframes.
- Insurance: Notify the insurer as the policy requires; late notice can affect coverage.
Drafting note: Work with counsel in advance to list which laws and contracts apply to your business, and record them here.
13. Incident Log
The IR lead keeps a running log for every Severity 2 or higher incident. The log is stored outside potentially compromised systems during the incident.
| Date / time | Action or observation | Person | Systems / accounts involved | Notes |
|---|---|---|---|---|
Incident summary (complete at closure)
| Item | Details |
|---|---|
| Incident ID and type | |
| Date and time detected / contained / closed | |
| Severity (initial and final) | |
| Root cause | |
| Data affected and number of people | |
| Notifications made (who, when) | |
| Estimated cost and downtime | |
| Improvements assigned (owner, due date) |
14. Training and Testing
- All employees learn how to recognize and report incidents during onboarding and annual security awareness training.
- The incident response team conducts a tabletop exercise at least annually, rotating scenarios (ransomware, BEC, lost laptop, vendor breach).
- The contact tree is tested at least twice a year.
- This Plan is reviewed [Review frequency] and after every Severity 3 or 4 incident.
15. Revision History
| Version | Date | Description of change | Author |
|---|---|---|---|
| [Version] | [Effective date] | Initial adoption of this Cybersecurity Incident Response Plan | [Owner name] |
16. Approval
This Cybersecurity Incident Response Plan has been reviewed and approved by the undersigned and is effective as of [Effective date]. It will be reviewed [Review frequency], after any significant incident, and whenever there is a material change to our systems, staff, or legal obligations.
| Signature: | Name / title: [Approver name], [Approver title] | Date: |
| Signature: | Name / title: [Owner name], [Owner title] | Date: |
Template adapted from the free Cybersecurity Incident Response Plan template by PinellasIT (pinellasit.com/templates). Review with your legal counsel and insurer before adoption.
