Business & Strategy
Security Incident First-Hour Playbook: Who to Tell, What to Stop, and What to Keep
Intermediate | 4 whiteboard pages · Task board: 5 columns (4 parent tasks, 12 subtasks)
Intermediate: Method names appear, but the whiteboard explains the key points. Use the examples as a guide and fill it in, thinking it through for your own situation.
A security incident playbook tells whoever notices something odd who to tell first, what to disconnect, what to keep, and who to call in during the first hour. Staff who see a strange screen, files that will not open, or a locked account often try to fix it alone or stay quiet for fear of being scolded. This template turns each situation into first-hour steps you can hand out, with 5W1H for reports and three promises (report at once, leave things as they are, no blame). Restarting, deleting, or powering off destroys clues, hesitating lets it spread, and stale numbers stay on the contact list, so staff report without touching anything and the list is checked regularly. Whether to disconnect is judged on impact and spread. Check how to handle power against the latest official guidance, then read the playbook aloud once and practice sending a report. The whiteboard has four pages and 15 frames; the task board has five columns, 4 parent tasks, and 12 subtasks.
Once you have a free account, you can copy this template from the marketplace
Whiteboard preview
Read the whiteboard text as plain text
Security Incident: The First Hour
How to use (4 pages): ① Page 1, write the goal and list the situations (sections①–③) → ② Page 2, decide what to report and the promises (sections④–⑦) → ③ Page 3, check the pitfalls, decide when to disconnect, and why power stays on (sections⑧–⑫) → ④ Page 4, build the contact list, hand out and practice (sections⑬–⑮)
1/4 Pick the warning signs
① Purpose of the playbook (start here)
- What this playbook should protect e.g. whoever notices tells someone without hesitating, and the damage stops at one device
- Who to tell first right now (a draft is fine) e.g. Dana in admin, ext. 200. If she is away, the CEO
- People and devices covered e.g. 12 staff, plus company computers, phones, and the shared folder
② The 5 steps of the first hour (move in this order)
- Notice Notice something different e.g. files will not open. Do not retry, stop what you are doing
- Tell Tell the contact right away e.g. call within 5 minutes of noticing and give the six points of ④
- Disconnect Disconnect from the network, keep power on e.g. turn off wireless or unplug the cable. When unsure, follow the contact's instructions
- Keep Keep what you saw and what you did e.g. photograph the screen with a phone and write the time and your actions on paper
- Escalate Pass it to a manager and an outside expert e.g. the contact tells a manager and calls the maintenance vendor in ⑮
③ When people notice (fill in the four situations)
| What they see | Trouble it causes | Who notices first | |
|---|---|---|---|
| Unfamiliar display | e.g. an unknown notice fills the screen and will not go away | e.g. work cannot continue. Even if a phone number is shown, do not call it. Tell the contact instead | e.g. the person using that device |
| Files will not open | e.g. file names in the shared folder changed to an unfamiliar form | e.g. cannot send a quote | e.g. people who use the shared folder every day |
| Cannot sign in | e.g. the usual password fails, and a notice arrived about a change you do not remember making | e.g. email and calendar are unusable | e.g. the account owner |
| Unknown message | e.g. a client replies to an email nobody remembers sending | e.g. it causes trouble for clients | e.g. the account owner, or sales who heard from a client |
2/4 Set what to report
④ What to report (give the situation from ③ using 5W1H)
- What to report
- What what is wrong e.g. the quote in the shared folder will not open and the file name has changed
- Why why it is odd e.g. what differs from usual. It opened fine yesterday
- Who who noticed e.g. Tom in sales noticed. The device is one sales laptop
- When when noticed e.g. noticed around 9:10 a.m. today. Last worked normally at 6 p.m. yesterday
- Where where it happened e.g. head office, 2nd floor. Still on the office wireless
- How what you did e.g. what you did after noticing. Pressed nothing and photographed the screen
⑤ Promise 1 Report at once
- A doubt is enough to report
- e.g. even if it is probably a mistake, tell the contact within 5 minutes
- e.g. if the contact cannot be reached, use the backup in ⑬
- Who to tell at night or on days off: ____
⑥ Promise 2 Leave it as it is
- Do not try to fix it, and write down everything you touched
- e.g. photograph the screen with a phone
- e.g. write down files you deleted or buttons you pressed, without hiding them
- e.g. send it briefly in the order of the six points in ④
⑦ Promise 3 No blame
- A manager promises first that nobody who reports will be blamed
- e.g. the first reply is "Thanks for telling us so quickly"
- Finding the cause comes later, and the first hour goes to stopping the spread
- e.g. the CEO reads this promise aloud in front of everyone
3/4 Set what to stop
⑧ Pitfall 1 Fixing it yourself (check against promise ⑥)
- [What happens] e.g. restarting or deleting files wipes out clues about what happened
- [How to check] e.g. see whether the report in ④ has a place for what you did after noticing
- [The move to prevent it] e.g. write 'Do not fix, do not delete, tell right away' on line 1 of the playbook
- e.g. promise ⑥, leave it as it is, prevents this
⑨ Pitfall 2 Powering off (check against the 5 steps in ②)
- [What happens] e.g. clues about the running state vanish and investigators struggle
- [How to check] e.g. see whether the playbook says to keep power on and disconnect from the network
- [The move to prevent it] e.g. write how to disconnect each device in ⑫
- e.g. for a device you do not know how to disconnect, wait for the contact's instructions
⑩ Pitfall 3 Hesitating to report (check against promise ⑦)
- [What happens] e.g. while someone stays quiet fearing a scolding, it spreads to other devices
- [How to check] e.g. talk with a manager about whether small reports were blamed before
- [The move to prevent it] e.g. add a manager's name to promise ⑦ and print it beside the contact list
- e.g. decide to thank people even for reports that turn out to be mistakes
⑪ When to disconnect (place the situations from ③ by impact and spread)
Vertical axis: Impact on work (higher = bigger) / Horizontal axis: Spread (further right = more devices)
- Work stops on 1 device e.g. files will not open on the accounting computer only → disconnect that one device from the network and tell the contact and a manager
- Work stops on many devices e.g. shared folder files will not open from any device → the contact decides how far to disconnect, and an outside expert is called in right away
- 1 device, feels off e.g. an unfamiliar display appeared once and vanished → keep a photo and ask the contact whether to disconnect
- Many devices, feels off e.g. an unknown message reached 3 people → do not click the link, tell the contact together, and check whether anyone else got it
⑫ Why power stays on, and how to disconnect
- Why power stays on e.g. write in the playbook: "Cut only the network. Powering off erases what is on screen and how things were running, so there is nothing left to investigate."
- How to disconnect each device e.g. for a laptop, turn off wireless and unplug the cable. If it will not disconnect or you are unsure, follow the contact's instructions
- What to check e.g. check how to handle power against the latest official guidance and write down the name of the source
4/4 Hand out the playbook
⑬ Contact list (put the escalation contacts set in ⑪ into a table)
| Name | Contact | Backup | Date checked | |
|---|---|---|---|---|
| Reporting contact | e.g. Dana in admin | e.g. ext. 200 and mobile | e.g. Lee in admin | e.g. Monday of week 1 |
| Decision maker | e.g. the CEO | e.g. mobile | e.g. the deputy CEO | e.g. Monday of week 1 |
| Device expert | e.g. Priya in sales | e.g. mobile and chat | e.g. the vendor's contact person | e.g. Tuesday of week 1 |
| Outside expert | e.g. the vendor's contact person | e.g. vendor phone and night number | e.g. another person at the vendor | e.g. Tuesday of week 1 |
⑭ Hand out the playbook and practice
- Compile Turn ①–⑬ into one sheet e.g. put the 5 steps of ② on the front and the contact list of ⑬ on the back
- Hand out Put it in everyone's hands and in plain view e.g. give a paper copy to every desk and post one near the contact. Make sure it can be read even when a computer will not open
- Practice Read it aloud and practice a report e.g. at the morning meeting, read one situation from ③ and try sending a report to the contact in 10 minutes
- Review [Pitfall] The contact list is out of date [What happens] e.g. you lose time phoning someone who has moved [How to check] e.g. call everyone in ⑬ once [The move to prevent it] e.g. rewrite the date checked in ⑬ in any week people join or leave
⑮ Outside places to ask
- The vendor that maintains your systems e.g. company name, contact person, phone, and whether they can be reached at night or on days off
- Public advice services e.g. check the advice services in your country or region in the latest notice and write them down
- Insurance and notifying clients e.g. check whether you have insurance and who is in charge of telling clients
Task board contents
Not started 16 items
Pick warning signs
On page 1, write the purpose of the playbook and the first person to tell, then decide four situations where staff notice something odd. Once these are set, the later pages can match what to report and what to stop to each situation. Press Ctrl+F (⌘F on Mac) and type 3/4 to jump to page 3.
Pick first contact
Open your company contact list or chat member list, pick one person to tell first, and write the name and phone number under "Who to tell first right now" in section ①. It takes about 15 minutes, and even before the playbook is done you can start by telling this one person.
Assign the 5 steps
Read the 5 steps in section ② and add a sticky note naming who does each step in your company. Done when all 5 steps have a name.
Fill in the table
In section ③, fill in what is seen, what trouble it causes, and who notices first for each of the four situations. Replace any situation that is unlikely at your company with one that is likely.
Set what to report
On page 2, decide what a report contains and the promises around reporting. How fast the first hour goes depends on whether the person who notices can report briefly without hesitating.
Apply the 5W1H
Take one situation from section ③ and write an example for each of the six questions in section ④. Done when all six have an example.
Write the promises
In sections ⑤ to ⑦, write the promises to report at once, leave things as they are, and not blame, in your company's own words. Done when a manager reads promise ⑦ and agrees.
Draft report format
Make one report format that lists the six questions of section ④ in order, and write it on a sticky note in section ⑥. Done when anyone can write a report in the same order.
Set what to stop
On page 3, check the pitfalls and decide when to disconnect from the network and why power stays on. This shapes how far the damage spreads, so it gets the most time.
Check the pitfalls
For each pitfall in sections ⑧ to ⑩, rewrite what happens, how to check, and the move that prevents it using your own examples. Done when all three frames have a preventing move.
Map isolation calls
In section ⑪, place the situations from section ③ on the two axes of impact on work and spread, and write who decides to disconnect for each of the four areas.
Why keep power on
In section ⑫, write why power stays on and how to disconnect each kind of device. Check how to handle power against the latest official guidance. Done when the name of the source you checked is on a sticky note.
Hand out playbook
On page 4, build the contact list, hand out the playbook and practice with it, and write down the outside places to ask. The job is done once it is handed out and practiced once, tracked in the Practiced column of the task board.
Build contact table
In section ⑬, write each role's name, contact, backup, and the date checked. Done when all 4 rows have a backup.
Hand out and drill
Compile the playbook and hand it out following the 4 steps of section ⑭, then read it aloud and practice a report once. Done when places where people hesitated in practice are added to the playbook.
List outside help
In section ⑮, write the maintenance vendor, public advice services, and who to contact about insurance and clients. Check each service's contact details in the latest notice.