Incident Response Plan for Iraqi Organisations: A Guide, with a Blank Template
An incident response plan is a document that settles, before anything happens, who decides, who is told and what is done at each stage, so the first hours are not spent improvising. This guide explains the steps of cyber incident response as set out in the third revision of the US National Institute of Standards and Technology (NIST) guidance [1], and connects them to the "Respond" section of the Central Bank of Iraq’s Cyber Resilience Controls for the Financial and Banking Sector in Iraq (ضوابط الصمود السيبراني للقطاع المالي والمصرفي في العراق) [2]. At the end there is a blank template, in Arabic and English, that you can download and fill in.
This guide is an explanatory summary in our own words. It does not replace the original texts linked under Sources, and it is not legal advice. The CBI publishes its controls in Arabic; this English page is an unofficial summary, and the English names of CBI sections and clauses are our unofficial translation.
What is an incident response plan?
NIST distinguishes an "event", meaning any observable occurrence involving computing assets, physical or virtual, networks, services or cloud environments, from a "cybersecurity incident": an occurrence that actually or imminently jeopardises, without lawful authority, the integrity, confidentiality or availability of information or an information system, or that violates, or imminently threatens to violate, law, security policies, security procedures or acceptable use policies [1]. The examples the guidance gives include flooding an internet-facing service with connection requests until it fails, ransomware that stops systems and copies files from them, phishing emails used to take over accounts and commit financial fraud, and a supplier’s software compromised before it reaches its customers [1].
NIST describes the plan itself as the roadmap for building an organisation’s incident response capability [1]. Above the plan sits the incident response policy; below it sit written procedures and playbooks, which give actionable steps for specific scenarios [1].
What changed in NIST SP 800-61 Revision 3?
NIST published Revision 3 of Special Publication 800-61 in April 2025, superseding Revision 2 from 2012 [1]. The document is no longer a detailed incident-handling guide. It is now a "Community Profile" built on the Cybersecurity Framework (CSF) 2.0, which places incident response recommendations across the framework’s six Functions [1]. NIST’s reasoning is that incidents today are more frequent and more damaging, and recovery can take weeks or months, so treating response as a separate activity run by a separate team is no longer realistic [1]. The guidance still leaves each organisation free to choose the life-cycle model that suits it [1].
Why Iraqi organisations, and banks in particular, need one
For Iraqi banks and financial institutions, the reason to have an incident response plan is direct. The CBI’s cyber resilience controls are addressed to institutions and entities in the financial and banking sectors, and state that they are based in general on the NIST Cybersecurity Framework [2]. Their "Respond" section, under "Incident Management", requires [2]:
- An incident management framework whose aim is to restore normal IT services as quickly as possible with the least possible impact, with defined staff roles for recording, analysing, handling and monitoring incidents (clause 1.1).
- Appropriate incident severity levels, documented criteria for assessing them, and training for technical support staff to recognise high-severity incidents (clause 1.2).
- Escalation and resolution procedures, with resolution time frames proportionate to severity (clause 1.3).
- Periodic testing of the predefined escalation and response plan for security incidents (clause 1.4).
- An IT emergency response team of the institution’s own staff with the necessary technical and operational skills (clause 1.5).
- Keeping senior management informed as major incidents develop, and notifying the Central Bank of Iraq as soon as possible in the event of any disaster (clause 1.6).
- Keeping customers informed of any major incident (clause 1.7).
- Root-cause and impact analysis of incidents that disrupt IT services, and corrective action to prevent recurrence (clauses 1.8 and 1.9).
For organisations outside the financial sector, such as telecoms and retail, this guide does not cover sector-specific reporting duties; check your licence conditions, your regulator’s instructions and your legal adviser. The NIST steps, however, apply to any organisation: the Community Profile is intended for most organisations regardless of sector or size [1].
The steps of cyber incident response at a glance
Many people know the four phases made familiar by Revision 2. Revision 3 maps each of them to CSF 2.0 Functions as follows [1]:
| Phase in the previous model | Corresponding CSF 2.0 Functions |
|---|---|
| Preparation | Govern, Identify (all Categories), Protect |
| Detection and analysis | Detect, Identify (Improvement Category) |
| Containment, eradication and recovery | Respond, Recover, Identify (Improvement Category) |
| Post-incident activity | Identify (Improvement Category) |
NIST treats Govern, Identify and Protect as preparation activities broader than incident response itself; incident response in the direct sense is Detect, Respond and Recover, and continuous improvement feeds lessons learned at any time back into every Function [1]. The CBI controls use almost the same terms (identify, protect, detect, respond, recover) [2], though recovery sits inside their Respond section rather than in a section of its own, so one plan can speak to both frameworks.
Roles and contacts
Who does what
NIST stresses that successful response today depends on many parties inside and outside the organisation, not on the incident handling team alone [1]. Its examples include [1]:
- Leadership: oversees response, allocates funding, and may hold decision-making authority on high-impact actions such as shutting down or rebuilding a critical service.
- Incident handlers: verify that an incident has occurred, collect and analyse data and evidence, prioritise, and limit damage. They may be on staff, on contract, or available when needed.
- Technology professionals: security, network, system and cloud engineers, and software developers.
- Legal: reviews the plan and contracts, and is consulted when an incident may have legal consequences.
- Public affairs and media relations, human resources, physical security and facilities, and asset owners, who know the recovery priorities for their systems and data.
NIST recommends documenting all incident response roles in policy and giving those who hold them the authority they need [1], and suggests considering an incident lead for each incident [1]. Where a service provider performs part of the response, it notes that the contract should define responsibilities, information flows and the authority to act on the organisation’s behalf, and that the response team should know them [1]. The CBI controls require the roles and responsibilities of staff involved in incident management to be defined, and an IT emergency response team to be formed, as above [2].
The contact list
The plan needs a current list of response team members and their deputies, senior management, legal, media relations, and the external parties NIST mentions in the response context: your incident response service provider if you have one, internet and cloud service providers, regulators and law enforcement [1]. The CBI controls require the business continuity plan to include emergency contacts and the addresses and phone numbers of staff, vendors and agencies, and its documents to be kept in a secure place away from the main site as well as at the main site, with a copy in the office for reference [2].
Our practical advice: keep a copy of the list outside the systems an incident could take down, because email or the internal directory may fail during the incident.
Preparation: what to have in place before any incident
- An incident response policy. NIST lists elements most policies share: a statement of management commitment, purpose, scope, definitions of event and incident, roles and authorities (including who may confiscate, disconnect or shut down a device), guidelines for prioritisation, severity and initiating recovery, and performance measures [1].
- Written criteria. The CBI controls require documented criteria for assessing severity levels [2], and NIST recommends defined criteria for declaring an incident and for initiating recovery [1].
- Playbooks. NIST recommends documenting procedures for the most common incident types, and for important processes that may be needed urgently, such as redeploying the primary authentication platform [1].
- Central logging. NIST recommends transferring log data from its sources to a small number of log servers and using event correlation technology [1]. The CBI controls require system administrators' activity on servers to be logged [2].
- Restorable backups. The controls require a data backup and restore policy, encryption of backups holding sensitive information before they leave the site, and a documented restore process [2].
- Role-based training. NIST recommends that role-based training include each role’s incident responsibilities [1].
- A register of obligations. NIST recommends that an organisation’s cybersecurity requirements include everything related to incident notification and data breach reporting [1].
Detection and analysis
NIST recommends continuous log monitoring with tools such as security information and event management (SIEM) and security orchestration, automation and response (SOAR), correlating information from multiple sources, estimating the impact and scope of adverse events, and declaring an incident when it meets the predefined criteria [1].
Triage follows: a preliminary review to verify that an incident has actually occurred and to estimate its severity and urgency [1], then categorisation by type (for example a data breach, ransomware or an account takeover) and prioritisation by scope, likely impact, time-critical nature and available resources [1]. NIST warns against handling incidents first come, first served, and lists risk factors such as asset criticality, functional impact, data impact, the stage of observed activity, threat actor characterisation and recoverability [1].
The guidance separates "escalation", meaning more resources or longer time frames, from "elevation", meaning involving a higher level of management [1]; this corresponds to the CBI’s escalation procedures with time frames proportionate to severity [2]. NIST also asks for an incident’s magnitude to be estimated and validated by looking for indicators of compromise and evidence of persistence, since skipping this step can leave an incident running on other targets without the organisation knowing [1].
Containment, eradication and recovery
Containment
NIST defines containment as preventing an incident from expanding, and most incidents need some form of it [1]. Every choice has a cost: watching an attacker to gather more evidence can conflict with the need to return quickly to normal operations [1], which is why NIST recommends discussing any plan to redirect an attacker to a sandbox with the legal department before doing it [1]. The plan should settle in advance who may isolate systems, and consider authorising internet and cloud service providers to take certain containment actions on the organisation’s behalf, as with large-scale denial-of-service attacks [1].
Eradication
Eradication removes the incident’s effects: deleting malware, disabling breached accounts and fixing every exploited vulnerability, once all affected systems and services have been identified [1].
Recovery
NIST recommends [1]:
- Verifying the integrity of backups before using them to restore.
- Restoring essential services in the appropriate order, with system owners confirming successful restoration.
- Checking restored assets for indicators of compromise, and fixing root causes before returning them to production.
- Declaring the end of recovery against defined criteria, and preparing an after-action report.
The CBI controls connect this to the disaster recovery plan: senior management is kept informed so that the decision to activate that plan can be taken in time [2]. The controls also require recovery time objectives (RTO) and recovery point objectives (RPO) to be set for IT systems and applications, and information security to be maintained throughout recovery [2].
The root-cause and impact report
The CBI controls set out what the root-cause and impact analysis report covers [2]: when, where, why and how the incident happened, how often a similar incident has occurred, and the lessons learned; the incident’s scope in systems, resources and affected customers, and its size, including losses, costs, the number of affected customers and the effect on reputation and trust, plus any breach of regulatory requirements; then immediate corrective action, with customers' concerns given priority, and measures to address the root cause and prevent recurrence.
Communications and reporting, including regulators
NIST divides incident communications into four kinds: coordination among those with response roles; formal notification of those affected, such as customers, employees, partners and regulators; public and media communication; and voluntary sharing of threat information with others [1]. It recommends established procedures that say what is reported, to whom and when, from initial notification to regular status updates [1]; notifying regulators and law enforcement according to the plan’s criteria and with management approval, by designated individuals [1]; regular updates to senior leadership on major incidents; and written procedures for dealing with the media [1].
In the financial and banking sector, the CBI controls provide that [2]:
- The Central Bank of Iraq is notified as soon as possible in the event of any disaster (Respond, clause 1.6).
- Customers are kept informed of any major incident, because keeping their trust during a crisis matters for the institution’s reputation and soundness (clause 1.7).
- Leaks of classified information are reported. In the table of handling requirements by classification level (Identify, Data Classification): when classified information is disclosed, or suspected to have been leaked, disclosed, stolen or published, the CBI is informed directly by official letter or email setting out the facts and type of the incident; for "top secret" (سري للغاية) information, an urgent and confidential notice is sent together with a letter to the CBI stating what type of information was leaked.
These clauses do not set a deadline in hours; they use the phrases "as soon as possible" and "urgent notice" [2]. Your plan should therefore name who decides that an incident has reached the reporting threshold, who signs the letter and who follows up, and you should watch for any later CBI instructions.
Evidence preservation
NIST treats data collected about an incident as evidence even when formal chain-of-custody procedures are not followed, and recommends collecting and retaining it under the organisation’s evidence preservation procedures and data retention policies, taking into account the possibility of prosecution and the cost of retention [1]. It also recommends recording what is discovered and what actions are taken during the investigation, protecting the confidentiality and integrity of those records, and limiting access to authorised personnel [1].
NIST’s Guide to Integrating Forensic Techniques into Incident Response (SP 800-86) adds three practical rules [4]:
- Volatile data, in many cases first. This is data lost when a device is powered down, with the passage of time, or through other actions on the system.
- Verify copies. Compute the message digest of the original and the copied data and compare them.
- A clear chain of custody when needed. If evidence may be used in legal or disciplinary proceedings, keep a log of everyone who had custody of it, what they did and when, and store it securely. Make this decision before data collection starts, in line with the organisation’s policies and its legal advisers.
In practice: name in the plan who decides whether affected machines are powered down or reinstalled, because doing so can destroy volatile data for good [4].
Testing the plan: tabletop exercises
An untested plan is a written assumption. The CBI controls require the predefined escalation and response plan for security incidents to be tested periodically [2], the business continuity and disaster recovery plans to be tested and reviewed at least once a year [2], and disaster recovery test documentation to include at least the scope, plan and test results [2].
NIST treats exercises and tests as a source of improvement and points to its SP 800-84 [1]. That publication defines a tabletop exercise as discussion-based: a facilitator presents a scenario and asks questions, and participants discuss their roles, responsibilities, coordination and decisions, without deploying any equipment or resources [3]. Straight after the discussion comes a short debrief, the "hotwash", in which participants are asked where they did well, where they need more training and which parts of the plan need updating; observations and recommendations then go into an after-action report, and named people may be assigned to update the plan [3]. The publication distinguishes this from a "functional exercise", in which staff perform their roles as they would in a real emergency, but in a simulated environment [3].
For your first exercise, choose a realistic scenario for your sector, such as ransomware stopping branch systems or a leak of customer data, invite the people who would actually handle it, including legal and media relations, and ask: did everyone find the plan? Did they know who decides on reporting, and who signs it?
Keeping the plan current
NIST recommends [1]:
- Synchronising the incident response plan with the business continuity plan, since incidents can undermine business resilience.
- Reviewing and updating plans periodically, or whenever a need for significant improvement is identified.
- Basing each plan on the organisation’s own requirements, mission, size, structure and functions.
- Having each plan identify the resources and management support needed to carry it out.
It also recommends evaluating incident response performance periodically, through self-assessment, third-party assessment or independent audit [1], and holding "lessons learned" meetings as recovery concludes, especially after major incidents [1]. For their part, the CBI controls require a compliance process run periodically or whenever new regulatory requirements take effect, leading to updates of cybersecurity policy, standards and procedures where needed [2], and require the approved business continuity plan to be circulated to stakeholders whenever it changes [2].
Occasions on which we recommend reviewing the plan: after every major incident, after every exercise, when the holders of key roles change, when a new system or service provider is introduced, and when new regulatory instructions are issued.
Download the incident response plan template
We have prepared a blank template in Arabic and another in English, containing headings and guiding prompts only, with no data or examples from real organisations. It covers document control, scope and definitions, roles and authorities, contacts, severity levels and criteria, escalation, internal reporting, triage and analysis, containment, eradication and recovery, communications and regulatory reporting, evidence preservation, a playbook index, post-incident activity, testing and maintenance.
- Download the English template (plain text)
- تنزيل النموذج بالعربية (نص عادي)
- Open the English template as a printable page
Once filled in, treat the plan as a confidential document: it reveals who is responsible, how to reach them and which of your systems matter most.
How Red Crow by DigiFort can help
DigiFort (الحصن الرقمي) is a software, AI and cybersecurity company for Iraq, and Red Crow by DigiFort is its cybersecurity practice. Its incident response retainer means the paperwork is done before the incident: NDA, contacts, severity matrix, escalation tree and pre-agreed rates. The service includes a severity matrix from S1 to S4, an incident-response plan and playbooks aligned to the CBI’s notification duties, a tabletop exercise, retainer hours at pre-agreed rates, and a post-incident report template for the board and the regulator. The duty to notify the CBI and to inform customers stays with the institution, and we help prepare what it sends.
Frequently asked questions
What is the difference between an incident response plan and a business continuity plan?
The incident response plan runs the handling of the cyber incident itself, from detection to recovery; the business continuity plan keeps critical operations running, or brings them back, after a disaster. NIST counts both among the plans relevant to incident response and recommends synchronising them [1]. In the CBI controls each has its own requirements, and they meet at the decision to activate the disaster recovery plan during major incidents [2].
Do the Central Bank of Iraq’s controls require an incident response plan?
The controls require an incident management framework, severity levels with documented criteria, escalation procedures and an IT emergency response team, and they require the "predefined escalation and response plan for security incidents" to be tested periodically [2]. A written plan is the practical way to show all of this.
When must the Central Bank of Iraq be notified of an incident?
The controls require notification as soon as possible in the event of any disaster, direct notification by official letter or email when classified information leaks, and an urgent, confidential notice for "top secret" information [2]. These clauses give no deadline in hours, so name in your plan who decides to report and who signs, and watch for later instructions.
Are the four incident response phases still valid after NIST’s Revision 3?
Yes, as a shared language. Revision 3, published in April 2025, maps each phase to CSF 2.0 Functions and leaves each organisation free to choose the model that suits it [1].
How often should we test the plan?
The CBI controls require the escalation and response plan to be tested periodically, and the business continuity and disaster recovery plans to be tested at least once a year [2]. It makes sense to schedule a tabletop exercise in the same cycle, and to repeat it after any major change in systems or people.
We need systems back quickly. How do we preserve evidence?
Is the template free, and does it contain any data?
The template is free and completely blank: headings and guiding prompts only, with no data or examples from any organisation.
Sources
CBI clause numbers are as printed in the document (which sometimes writes them with a comma, for example "1,6").
- 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
- Central Bank of Iraq, Information Technology and Payments Department, «ضوابط الصمود السيبراني للقطاع المالي والمصرفي في العراق» (Cyber Resilience Controls for the Financial and Banking Sector in Iraq; English title is our unofficial translation). https://cbi.iq/news/view/2607 (document: https://cbi.iq/static/uploads/up/file-171939700326129.pdf)
- NIST, SP 800-84: Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities, September 2006. https://csrc.nist.gov/pubs/sp/800/84/final
- NIST, SP 800-86: Guide to Integrating Forensic Techniques into Incident Response, August 2006. https://csrc.nist.gov/pubs/sp/800/86/final
Related
Talk to us
A senior practitioner replies.