Incident Response Plan and CSIRT: Decision Criteria, Roles, and Outside Experts

Business & Strategy

Incident Response Plan and CSIRT: Decision Criteria, Roles, and Outside Experts

Advanced | 4 whiteboard pages · Task board: 5 columns (4 parent tasks, 12 subtasks)

Advanced: Assumes you know the technical terms and methods, and the steps are only outlined. Work through it on your own, guided by decision criteria and points to check.

An incident response plan sets in advance the criteria executives use to shut systems down, go public, or notify business partners. This template tabulates severity levels with reporting lines and decision makers, assigns CSIRT roles via RACI, and lists peacetime agreements with outside forensics, legal, and PR experts. Left to staff, delays are common, such as hesitating to shut down, missing the decision maker's number on a Saturday night, or seeking a forensics firm after the breach. The board pairs each delay with a check and a fix, and the statement splits the known from the unknown so you never rule out a leak before the investigation ends. See NIST SP 800-61 Rev. 3 and, in Japan, IPA's ransomware handbook for executives (check the latest editions). First check whether your contact tree and outage runbook list who can order a shutdown and their after-hours number. The whiteboard has four pages; the task board has five columns, 4 parent tasks, and 12 subtasks.

0 Likes 0 Copies Author: WeProcess
Incident response CSIRT Security measures RACI Business continuity
Sign up free and use this template

Once you have a free account, you can copy this template from the marketplace

Whiteboard preview

Read the whiteboard text as plain text

Incident Response Plan and CSIRT Board

How to use (4 pages): ① Page 1 sets purpose, severity levels, and stop, disclose, notify criteria (boards①-⑤) → ② Page 2 sets RACI roles and outside expert deals (boards⑥-⑨) → ③ Page 3 sorts audiences, checks pitfalls, and drafts the statement (boards⑩-⑭) → ④ Page 4 plans a year of drills, fixes, and the leadership report (boards⑮-⑰)

1/4 Set the decision criteria

① Purpose and scope of the plan (start here)

  • Purpose of the plan e.g. When an incident hits, executives can decide to stop, disclose, or notify without hesitation
  • Scope e.g. Internal systems, cloud services in use, and data held by contractors
  • Current state e.g. The procedure lives only in IT's heads. The executive's after-hours number is not on the contact tree

② Severity table (example, reporting line, and decision maker per level)

Example Reported to Decision maker Report within
Level 1 Minor e.g. A suspicious message appears on one PC e.g. IT staff e.g. IT staff e.g. Same day
Level 2 Caution e.g. A shared folder in one department will not open e.g. CSIRT lead e.g. CSIRT lead e.g. Within 1 hour
Level 3 Serious e.g. Suspicious traffic logged on a server holding customer data e.g. Executive and the whole CSIRT e.g. Executive e.g. Within 30 minutes
Level 4 Crisis e.g. The core system is down and business cannot continue e.g. Executive and outside experts e.g. Executive (deputy if absent) e.g. Immediately (nights and holidays too)

③ Criteria for stopping

  • e.g. At level 3 or above, stop if damage may spread
  • Impact on business if stopped: e.g. orders halt for half a day
  • Decision maker: e.g. The executive. If unreachable for 30 minutes, the CSIRT lead decides

④ Criteria for disclosing

  • e.g. When customer or partner information may be affected
  • Check with legal and the latest official guidance whether the law requires a report or notice
  • Timing: e.g. Issue a first report as soon as a possible impact is known, separating what is known from what is not, then follow up

⑤ Criteria for notifying partners

  • e.g. When systems that link to partners (ordering, shared files) may be affected
  • Contractual deadline: e.g. Check the incident-notification clause in the contract
  • Order: e.g. Closest partners first, by phone from the account manager

2/4 Assign the roles

⑥ RACI: assign the decision makers from ② to response tasks (R = does, A = accountable, C = consulted, I = informed)

Executive CSIRT lead IT staff PR and legal
Detection and first response e.g. I (informed at level 3 or above) e.g. A (sets the level) e.g. R (first check and logging) e.g. I
Stop and contain e.g. A (decides to stop under the criteria in ③) e.g. R (directs the stop procedure) e.g. R (disconnect from the network per procedure, without powering off, to keep records) e.g. I
Investigate and recover e.g. I e.g. A (sets the scope of investigation) e.g. R (recovers with outside experts) e.g. C (advises on preserving records)
Disclose and notify e.g. A (decides to disclose under ④ and ⑤) e.g. C (supplies the facts) e.g. C (explains the extent of impact) e.g. R (prepares the statement and notices)
Prevent recurrence e.g. C (consulted on budget and priorities) e.g. A (compiles the prevention plan) e.g. R (fixes settings and procedures) e.g. I

⑦ Agreement with the investigation expert

  • Candidates: e.g. The maintenance vendor, plus one firm that specializes in investigations
  • After-hours contact: e.g. Check before signing whether they take calls 24 hours a day
  • Scope: e.g. Root-cause investigation, preserving records, recovery advice
  • Procedure to set: e.g. Who approves the quote and the order

⑧ Agreement with legal (lawyer)

  • Who: e.g. A retained lawyer, or a firm experienced with data incidents
  • What to ask: e.g. Reporting and notice duties, contractual deadlines
  • How to reach them: e.g. Put an emergency mobile number on the contact tree
  • Cost: e.g. Check what the retainer covers

⑨ Agreement with PR

  • Owner: e.g. The in-house PR person, or an outside PR firm if there is none
  • To prepare: e.g. The statement format from ⑭ and a draft plan for the inquiry desk
  • Taking inquiries: e.g. Phone and email desks, and who answers
  • Procedure to set: e.g. Who checks and releases the statement

3/4 Narrow the audience

⑩ Sort who to tell under the Disclose and notify role in ⑥ (stakeholder map, influence x interest)

Vertical axis: Influence low → high / Horizontal axis: Interest low → high

  • Keep satisfied e.g. Shareholders and banks. The executive briefs them individually on the key points
  • Manage closely e.g. Major partners and regulators who require reports. Contact them directly and early, and promise follow-ups
  • Monitor e.g. Industry bodies and local contacts. Answer inquiries with the public statement
  • Keep informed e.g. Employees and affected customers. Give the same content in the statement and an FAQ

⑪ Pitfall: leaving decisions to the front line causes delay

  • What happens: e.g. Staff hesitate to stop and check with their managers while damage spreads
  • How to check: e.g. Do ② and ③ name the decision maker and a maximum wait time?
  • Prevention: e.g. Add the rule from ③ (a deputy decides if there is no answer for 30 minutes) to ④ and ⑤ as well
  • Check result: e.g. △ ④ and ⑤ have no maximum wait time or deputy

⑫ Pitfall: after-hours contact does not get through

  • What happens: e.g. Noticed on Saturday night, but without the decision maker's number nothing is stopped until Monday
  • How to check: e.g. Does the contact tree list night numbers and deputies? Once a year, call them to confirm they actually connect
  • Prevention: e.g. Name up to two deputies per decision maker and keep a printed contact tree at hand
  • Check result: e.g. × The executive's after-hours number is missing

⑬ Pitfall: looking for outside experts after the incident

  • What happens: e.g. No firm can be found to investigate, and quotes and contracts take days
  • How to check: e.g. Are the contacts, desks, and procedures in ⑦ to ⑨ filled in?
  • Prevention: e.g. Agree on contacts and procedures in peacetime and put the desk numbers on the contact tree
  • Check result: e.g. ○ Maintenance vendor chosen for investigation. Legal undecided

⑭ Statement format (pitfall: claiming too early that nothing leaked)

  • What is known e.g. What is unavailable and since when, and the response under way Check: did you write only facts confirmed by investigation?
  • What is not yet known What happens: e.g. Saying "no leak" before the investigation ends, then correcting it later Prevention: e.g. Write "whether data leaked is under investigation; we will report as soon as we know" and do not rule it out
  • Next report and contact point e.g. When the next update is expected, and the inquiry desk

4/4 Drill and fix

⑮ Plan a year of drills and reviews from the check results in ⑪ to ⑬

  1. Months 1-3 Check the contact tree e.g. Call the contacts on ⑥ and ⑦ to ⑨ and confirm the after-hours desk connects
  2. Months 4-6 Run a tabletop exercise e.g. Assume the core system is down and walk through the decisions in ② to ⑤ with the executive (60 minutes)
  3. Months 7-8 Gather what you found e.g. Add hesitant decisions and failed contacts to the check results in ⑪ to ⑬
  4. Months 9-10 Revise the plan e.g. Give each fix in ⑯ an owner and a deadline, and rewrite ② to ⑨
  5. Months 11-12 Report to leadership e.g. Report the year's results and next year's schedule in the format of ⑰

⑯ Fixes, owners, deadlines (findings from checks and drills)

Fix Owner Deadline
Contact tree e.g. Add the executive's after-hours number and two deputies e.g. General affairs staff e.g. By the week after the drill
Decision criteria e.g. Add the 30-minute deputy rule to ④ and ⑤ as well e.g. CSIRT lead e.g. By the next board meeting
Outside agreements e.g. Choose a legal firm and write its desk in ⑧ e.g. General affairs manager e.g. Within 2 months
Statement format e.g. Add the expected timing of follow-ups to ⑭ e.g. PR staff e.g. Within 1 month

⑰ How to report to leadership

  • How often e.g. Once a year (months 11-12 of ⑮) and after any level 3 or higher incident, 15 minutes at the board meeting
  • What to include e.g. Decisions that caused hesitation in drills, and the fixes in ⑯ that are done and still open
  • What leadership decides e.g. Budget for outside expert contracts, and who stands in for the level 4 decision

Task board contents

Not started 16 items

Set the criteria

On page 1, write the plan's purpose and the severity levels, then set the criteria for stopping, disclosing, and notifying. Roles and contacts cannot be decided until these are, so start here. Press Ctrl+F (⌘F on Mac) and type 3/4 to jump to page 3.

Open contact tree

Open the emergency contact tree and the current outage runbook (or, if there is none, notes from asking IT) and check whether they name who can order a shutdown and an after-hours number. It takes about 15 minutes. Done when the result is on the Current state note on board ①.

Draft severity table

On board ②, write for levels 1 to 4 an example, who gets the report, who decides, and the target time to report. Done when all four rows name a decision maker or role.

Write the 3 criteria

On boards ③ to ⑤, write the criteria for stopping, disclosing, and notifying partners, plus what applies when the decision maker cannot be reached. Done when an executive reads and approves them.

Assign the roles

On page 2, set roles for each response task in a RACI matrix and confirm the agreements to make in peacetime with outside forensics, legal, and PR experts. This turns the decision makers from page 1 into a team that can act.

Set roles in RACI

On board ⑥, put exactly one A (accountable) on each of the five tasks and fill in R, C, and I. Done when no row has two As or a blank.

Confirm outside help

Fill in each note on boards ⑦ to ⑨ (who to call, contact point, scope, procedure and cost) by checking contracts and asking vendors and firms, including whether they reach you at night and on holidays. Write TBD for open items and carry them to page 4.

Name backups

For each A and R on board ⑥, name one or two backups for when they cannot be reached. For stop, disclose, and notify decisions, reuse the backups set on ③ to ⑤. Done when each backup has been told.

Narrow the audience

On page 3, sort who to tell by influence and interest, check the plan for pitfalls, and draft the statement format. This turns the disclose and notify role from page 2 into who hears what.

Sort into 4 groups

On the stakeholder map on board ⑩, place partners, shareholders, employees, customers, and others, and write how to reach each quadrant. Done when every major party sits in a quadrant.

Check the pitfalls

For each pitfall on boards ⑪ to ⑬, review the plan using the check and mark the result as ○, △, or ×. Move the △ and × items to board ⑯ on page 4.

Draft the statement

Using the three notes on board ⑭, draft a statement that separates what is known, what is not yet known, and the next report and contact point. Have PR and legal review it.

Drill and fix

On page 4, schedule a year of drills and reviews, give each fix an owner and a deadline, and decide how to report to leadership. This keeps the plan usable every year instead of leaving it as written.

Schedule the drills

For each of the five steps on board ⑮, set the month and participants and add them to the company calendar. Done when the tabletop exercise is on the executive's calendar.

List the fixes

On board ⑯, write the fixes found in checks and drills with an owner and a deadline. Done when every row has both.

Plan exec reporting

On board ⑰, write how often to report, what to include, and what leadership must decide, then put it on the board meeting agenda.

Drafting 0 items

Awaiting exec sign-off 0 items

Testing in drills 0 items

Reflected in plan 0 items

← Back to templates

Preview mode Incident Response Plan and CSIRT: Decision Criteria, Roles, and Outside Experts

Whiteboard preview

① Purpose and scope of the plan (star... ② Severity table (example, reporting ... ③ Criteria for stopping ④ Criteria for disclosing ⑤ Criteria for notifying partners ⑥ RACI: assign the decision makers fr... ⑦ Agreement with the investigation ex... ⑧ Agreement with legal (lawyer) ⑨ Agreement with PR ⑩ Sort who to tell under the Disclose... Keep satisfied Manage closely Monitor Keep informed ⑪ Pitfall: leaving decisions to the f... ⑫ Pitfall: after-hours contact does n... ⑬ Pitfall: looking for outside expert... ⑭ Statement format (pitfall: claiming... ⑮ Plan a year of drills and reviews f... ⑯ Fixes, owners, deadlines (findings ... ⑰ How to report to leadership Incident Response... How to use (4 pag... Goals and executi... Criteria, procedu... Pitfalls and caus... Current state and... 1/4 Set the decision ... Ctrl+F / ⌘F : 2/4... → 2/4 2/4 Assign the roles ↙ 3/4 Purpose of the plane.g. When an incident hits, executives can decide to stop, disclose, or notify without hesitation Scopee.g. Internal systems, cloud services in use, and data held by contractors Current statee.g. The procedure lives only in IT's heads. The executive's after-hours number is not on the contact tree Example Reported to Decision maker Report within Level 1 Minor e.g. A suspicious message appears on one PC e.g. IT staff e.g. IT staff e.g. Same day Level 2 Caution e.g. A shared folder in one department will not open e.g. CSIRT lead e.g. CSIRT lead e.g. Within 1 hour Level 3 Serious e.g. Suspicious traffic logged on a server holding customer data e.g. Executive and the whole CSIRT e.g. Executive e.g. Within 30 minutes Level 4 Crisis e.g. The core system is down and business cannot continue e.g. Executive and outside experts e.g. Executive (deputy if absent) e.g. Immediately (nights and holidays too) e.g. At level 3 or above, stop if damage may spread Impact on business if stopped: e.g. orders halt for half a day Decision maker: e.g. The executive. If unreachable for 30 minutes, the CSIRT lead decides e.g. When customer or partner information may be affected Check with legal and the latest official guidance whether the law requires a report or notice Timing: e.g. Issue a first report as soon as a possible impact is known, separating what is known from what is not, then follow up e.g. When systems that link to partners (ordering, shared files) may be affected Contractual deadline: e.g. Check the incident-notification clause in the contract Order: e.g. Closest partners first, by phone from the account manager Executive CSIRT lead IT staff PR and legal Detection and fir... e.g. I (informed at level 3 or above) e.g. A (sets the level) e.g. R (first check and logging) e.g. I Stop and contain e.g. A (decides to stop under the criteria in ③) e.g. R (directs the stop procedure) e.g. R (disconnect from the network per procedure, without powering off, to keep records) e.g. I Investigate and r... e.g. I e.g. A (sets the scope of investigation) e.g. R (recovers with outside experts) e.g. C (advises on preserving records) Disclose and notify e.g. A (decides to disclose under ④ and ⑤) e.g. C (supplies the facts) e.g. C (explains the extent of impact) e.g. R (prepares the statement and notices) Prevent recurrence e.g. C (consulted on budget and priorities) e.g. A (compiles the prevention plan) e.g. R (fixes settings and procedures) e.g. I Candidates: e.g. The maintenance vendor, plus one firm that specializes in investigations After-hours contact: e.g. Check before signing whether they take calls 24 hours a day Scope: e.g. Root-cause investigation, preserving records, recovery advice Procedure to set: e.g. Who approves the quote and the order Who: e.g. A retained lawyer, or a firm experienced with data incidents What to ask: e.g. Reporting and notice duties, contractual deadlines How to reach them: e.g. Put an emergency mobile number on the contact tree Cost: e.g. Check what the retainer covers Owner: e.g. The in-house PR person, or an outside PR firm if there is none To prepare: e.g. The statement format from ⑭ and a draft plan for the inquiry desk Taking inquiries: e.g. Phone and email desks, and who answers Procedure to set: e.g. Who checks and releases the statement 3/4 Narrow the audience → 4/4 4/4 Drill and fix Vertical axis: In... e.g. Shareholders and banks. The executive briefs them individually on the key points e.g. Major partners and regulators who require reports. Contact them directly and early, and promise follow-ups e.g. Industry bodies and local contacts. Answer inquiries with the public statement e.g. Employees and affected customers. Give the same content in the statement and an FAQ What happens: e.g. Staff hesitate to stop and check with their managers while damage spreads How to check: e.g. Do ② and ③ name the decision maker and a maximum wait time? Prevention: e.g. Add the rule from ③ (a deputy decides if there is no answer for 30 minutes) to ④ and ⑤ as well Check result: e.g. △ ④ and ⑤ have no maximum wait time or deputy What happens: e.g. Noticed on Saturday night, but without the decision maker's number nothing is stopped until Monday How to check: e.g. Does the contact tree list night numbers and deputies? Once a year, call them to confirm they actually connect Prevention: e.g. Name up to two deputies per decision maker and keep a printed contact tree at hand Check result: e.g. × The executive's after-hours number is missing What happens: e.g. No firm can be found to investigate, and quotes and contracts take days How to check: e.g. Are the contacts, desks, and procedures in ⑦ to ⑨ filled in? Prevention: e.g. Agree on contacts and procedures in peacetime and put the desk numbers on the contact tree Check result: e.g. ○ Maintenance vendor chosen for investigation. Legal undecided What is knowne.g. What is unavailable and since when, and the response under wayCheck: did you write only facts confirmed by investigation? What is not yet knownWhat happens: e.g. Saying "no leak" before the investigation ends, then correcting it laterPrevention: e.g. Write "whether data leaked is under investigation; we will report as soon as we know" and do not rule it out Next report and contact pointe.g. When the next update is expected, and the inquiry desk Months 1-3Check the contact treee.g. Call the contacts on ⑥ and ⑦ to ⑨ and confirm the after-hours desk connects Months 4-6Run a tabletop exercisee.g. Assume the core system is down and walk through the decisions in ② to ⑤ with the executive (60 minutes) Months 7-8Gather what you founde.g. Add hesitant decisions and failed contacts to the check results in ⑪ to ⑬ Months 9-10Revise the plane.g. Give each fix in ⑯ an owner and a deadline, and rewrite ② to ⑨ Months 11-12Report to leadershipe.g. Report the year's results and next year's schedule in the format of ⑰ Fix Owner Deadline Contact tree e.g. Add the executive's after-hours number and two deputies e.g. General affairs staff e.g. By the week after the drill Decision criteria e.g. Add the 30-minute deputy rule to ④ and ⑤ as well e.g. CSIRT lead e.g. By the next board meeting Outside agreements e.g. Choose a legal firm and write its desk in ⑧ e.g. General affairs manager e.g. Within 2 months Statement format e.g. Add the expected timing of follow-ups to ⑭ e.g. PR staff e.g. Within 1 month How oftene.g. Once a year (months 11-12 of ⑮) and after any level 3 or higher incident, 15 minutes at the board meeting What to includee.g. Decisions that caused hesitation in drills, and the fixes in ⑯ that are done and still open What leadership decidese.g. Budget for outside expert contracts, and who stands in for the level 4 decision → 2/4 Assign the roles ↙ 3/4 Narrow the audience → 4/4 Drill and fix
100%

Drag to move, scroll to zoom