العربية
Under attack? Get help nowActive incidents only
Talk to us

Cyber Incident Response Plan

Download as plain textBack to the guide

[Organisation name]

How to use this template

  • Replace everything in square brackets [ ] with your organisation’s information, and delete the guiding prompts once answered.
  • Add the sections you need and delete those that do not apply.
  • Once filled in, classify the document under your information classification policy and restrict its distribution.
  • Keep an offline copy that can be reached during an incident.
  • This template contains headings and guiding prompts only. It does not replace a review of the regulatory, legal and contractual requirements that apply to you.

Document control

ItemValue
Version[ ]
Approval date[ ]
Approved by[ ]
Document owner[ ]
Next review date[ ]
Classification[ ]
Distribution list[ ]

Change log

VersionDateWhat changedChanged byApproved by
[ ][ ][ ][ ][ ]

Purpose and scope

  • What is the purpose of this plan? [ ]
  • Which systems, services, sites and branches does it cover? [ ]
  • What does it not cover? [ ]
  • Which related plans and policies apply (incident response policy, business continuity plan, disaster recovery plan, backup policy), and where are they kept? [ ]
  • Which regulatory, legal and contractual requirements does this plan meet? [name the body, the document and the clause]

Definitions

  • What do you count as an "event"? [ ]
  • What do you count as a "cyber incident"? [ ]
  • What do you count as a "major incident", and what as a "disaster"? [ ]
  • Other terms used in this plan: [ ]

Roles, responsibilities and authorities

RoleNameJob titleDeputyResponsibilitiesAuthorities
Incident lead[ ][ ][ ][ ][ ]
Incident response team[ ][ ][ ][ ][ ]
Information security lead[ ][ ][ ][ ][ ]
IT lead[ ][ ][ ][ ][ ]
Senior management[ ][ ][ ][ ][ ]
Legal[ ][ ][ ][ ][ ]
Compliance and regulator liaison[ ][ ][ ][ ][ ]
Public affairs and media[ ][ ][ ][ ][ ]
Human resources[ ][ ][ ][ ][ ]
Physical security and facilities[ ][ ][ ][ ][ ]
Asset owners[ ][ ][ ][ ][ ]
Incident response provider (if any)[ ][ ][ ][ ][ ]
[Other role][ ][ ][ ][ ][ ]
  • Who has the authority to declare an incident? [ ]
  • Who has the authority to isolate, disconnect, shut down or rebuild a system? [ ]
  • Who decides to notify regulators, and who signs the notification? [ ]
  • Who decides to activate the business continuity plan or the disaster recovery plan? [ ]
  • What is each service provider responsible for under its contract, and what may it not do on your behalf? [ ]

Contacts

4.1 Internal

RoleNamePrimary contact methodBackup methodWhen to contact
[ ][ ][ ][ ][ ]

4.2 External

PartyContact personContact methodContract or reference numberWhen to contact
Incident response provider[ ][ ][ ][ ]
Internet service provider[ ][ ][ ][ ]
Cloud service provider[ ][ ][ ][ ]
Critical suppliers[ ][ ][ ][ ]
Competent regulator[ ][ ][ ][ ]
Law enforcement[ ][ ][ ][ ]
External legal counsel[ ][ ][ ][ ]
[Other party][ ][ ][ ][ ]
  • Where is the offline copy of this list kept? [ ]
  • When was the list last reviewed, and by whom? [ ]

Severity levels

LevelCriteriaExamples from your environmentTarget response timeTarget resolution timeWho is notified
[Level][ ][ ][ ][ ][ ]
[Level][ ][ ][ ][ ][ ]
[Level][ ][ ][ ][ ][ ]
[Level][ ][ ][ ][ ][ ]
  • Which factors do you use to assess severity (for example asset criticality, service impact, data impact, number affected, recoverability)? [ ]
  • Who sets the level, and who may change it? [ ]
  • How are technical support staff trained to recognise high-severity incidents? [ ]

Escalation and elevation

  • When is an incident escalated (more resources or time)? [ ]
  • When is it elevated to a higher level of management, and to whom? [ ]
  • Escalation tree for each severity level: [describe the sequence or attach a diagram]

Detection and internal reporting

  • How do staff report a suspected incident, and what is the out-of-hours alternative? [ ]
  • How can an outside party (customer, supplier, security researcher) report an incident involving you? [ ]
  • What are your alert sources? [ ]
  • Which fields are mandatory in the initial report? (see Appendix C)
  • What are your criteria for declaring an incident? [ ]

Triage and analysis

  • Have we confirmed that an incident has actually occurred?
  • What type is it? [ ]
  • Which systems, data and parties are affected? [ ]
  • What is the initial severity level? [ ]
  • Who leads this incident? [ ]
  • Do we need an outside provider? [ ]
  • Has logging of facts and actions started (Appendix A)?
  • Have we looked for indicators of compromise on other systems? [ ]
  • Is escalation or elevation needed? [ ]

Containment, eradication and recovery

9.1 Containment

  • Who decides on containment actions? [ ]
  • Which containment options are approved for each incident type? [ ]
  • Which actions may service providers take on your behalf? [ ]
  • How do you balance fast containment against evidence collection, and who decides? [ ]

9.2 Eradication

  • How do you make sure every affected system and service has been identified? [ ]
  • Who approves that eradication is complete? [ ]

9.3 Recovery

OrderSystem or serviceOwnerRecovery time objective (RTO)Recovery point objective (RPO)How it is checked before return
[ ][ ][ ][ ][ ][ ]
  • How is backup integrity verified before use? [ ]
  • What are the criteria for starting recovery? [ ]
  • What are the criteria for declaring recovery complete, and who declares it? [ ]

Communications and reporting

10.1 Internal

  • Who is updated, how often and by what means? [ ]

10.2 Regulators

RegulatorReporting criterionDeadlineMethodRequired contentPrepared bySigned byRegulatory reference
[ ][ ][ ][ ][ ][ ][ ][ ]

10.3 Customers

  • When are customers informed, through which channels, and who approves the text? [ ]

10.4 Media and public

  • Who is the approved spokesperson? [ ]
  • Who approves public statements? [ ]
  • What is not published? [ ]

10.5 Partners and suppliers

  • What reporting obligations do the contracts set? [ ]

10.6 Law enforcement

  • When are they contacted, and who decides? [ ]

10.7 Prepared message templates

TemplateAudienceWhere keptLast reviewed
[ ][ ][ ][ ]

Evidence preservation

  • Who collects evidence? [ ]
  • What is collected first? [ ]
  • Who decides whether affected machines are powered down, isolated or reinstalled? [ ]
  • How is the integrity of copies verified? [ ]
  • Where is evidence stored, and who may access it? [ ]
  • When is a formal chain of custody needed, and who decides with legal? (see Appendix B)
  • How long are evidence and incident records retained? [ ]

Playbook index

ScenarioPlaybook ownerWhere keptLast reviewedLast exercised
[ ][ ][ ][ ][ ]
[ ][ ][ ][ ][ ]

Post-incident

13.1 Incident report

  • When and where did the incident happen? [ ]
  • Why and how did it happen? [ ]
  • Has a similar incident happened before, and how often? [ ]
  • What was its scope (systems, resources, parties affected)? [ ]
  • What was its size (losses, costs, number affected, reputational effect)? [ ]
  • Was any regulatory or contractual requirement breached? [ ]
  • What immediate corrective actions were taken? [ ]
  • What measures address the root cause? [ ]
  • What measures prevent recurrence? [ ]
  • What are the lessons learned? [ ]

13.2 Lessons-learned meeting

  • Who attends, when is it held, and who follows up the recommendations? [ ]

13.3 Recommendations log

RecommendationOwnerDue dateStatus
[ ][ ][ ][ ]

Testing and exercises

Test typePlanned frequencyLast runNext dueOwner
Tabletop exercise[ ][ ][ ][ ]
Functional exercise[ ][ ][ ][ ]
Business continuity plan test[ ][ ][ ][ ]
Disaster recovery plan test[ ][ ][ ][ ]
Backup restore test[ ][ ][ ][ ]
[Other test][ ][ ][ ][ ]

Exercise log

DateScenarioParticipantsKey observationsPlan updates required
[ ][ ][ ][ ][ ]

Maintenance and review

  • How often is the plan reviewed? [ ]
  • Which events trigger an extra review? [ ]
  • Who distributes the updated version, and to whom? [ ]
  • What resources and management support does the plan need? [ ]

Appendix A: Incident log

Date and timeWhat happened or was foundAction takenBy whomNotes
[ ][ ][ ][ ][ ]

Appendix B: Chain-of-custody form

Evidence numberDescriptionReleased byReceived byDate and timePurposeStorage locationSignature
[ ][ ][ ][ ][ ][ ][ ][ ]

Appendix C: Initial report

FieldValue
Reporter’s name and unit[ ]
How to reach the reporter[ ]
Date and time of discovery[ ]
What was observed?[ ]
Systems or services involved[ ]
Is it still happening?[ ]
What has been done so far?[ ]
Who received the report, and when?[ ]

Template from DigiFort Iraq — digifort.iq/en/insights/incident-response-plan/

Version 2026-10