Skip to content
Incident Response Plan Templates

PlaybookChecked 16 November 2026

Incident response playbook for phishing

Download Word (.docx)Download PDF

Stages

  1. 1When to use this playbook
  2. 2Before you start: prerequisites
  3. 3Workflow
  4. 4Decision points
  5. 5Notices to check
  6. 6Exit criteria and follow-up

The template in full

1 When to use this playbook

Use this playbook when staff report a suspicious message, or when a user clicked a link, opened a file or entered credentials after a message arrived by email, text or chat.

2 Before you start: prerequisites

Complete these before an incident, as part of planning.

  • Mailbox auditing is on for all mailboxes, and message trace logs can be searched.
  • Sign-in logs and endpoint alerts are kept and searchable.
  • At least one identifier (email address or username) is known for each suspected target.
  • Staff know how to report a message with one click or one phone call, and know they will not be blamed.
  • Responders have the accounts and roles needed to search mail, reset sessions and remove messages.

3 Workflow

Work in this order. Record each step and its time in the incident log.

  1. Identify and confirm the phishing message: get the original message and its message identifier.
  2. Scope: find every recipient and whether each message was delivered.
  3. Assess interaction: who opened, clicked or replied, and who entered credentials or ran a file.
  4. Look for follow-on activity: new sign-ins, mailbox rules, forwarding, file downloads, new devices, lateral movement.
  5. Contain: remove the message from all mailboxes; block the sender, link and domain; revoke sessions and reset passwords for exposed accounts; isolate any device that ran a file.
  6. Prevent recurrence: add detections, adjust filters, and send a short note to staff.

4 Decision points

Stop at each of these and record the decision, the decider and the time.

Decision points
DecisionWho decidesInformation needed
Is any account or device compromised?Technical leadSign-in logs, endpoint alerts, user interview
Is data exposed?Technical lead, privacy leadMailbox access logs, downloads, forwarding rules
Is this one message or a campaign?Incident leadRecipient count, similar messages elsewhere
Is a payment request involved?Incident leadIf yes, also open the business email compromise playbook

5 Notices to check

Open section 10 of the plan and confirm whether any of these start a notice clock.

  • If personal data was accessed, start the data breach plan and the clocks in section 10.
  • Report phishing to the national service for your country; CISA asks organizations to report to report@cisa.gov or its 24/7 line, and the FBI IC3 takes complaints.

6 Exit criteria and follow-up

Close the playbook only when all of these are true.

  • No malicious messages remain in any mailbox.
  • Every exposed account is reset and its sessions are revoked.
  • No new suspicious activity for [period].
  • Detections and filters are updated, and staff are told the outcome.

About this playbook

What is the incident response playbook for phishing?

Phishing is one of the most common initial access techniques. Microsoft says a successful phishing attack can lead to credential compromise, malware execution, data exfiltration and lateral movement across identity, email and endpoint environments.

CISA's October 2023 phishing guidance urges organizations to report phishing promptly to CISA at report@cisa.gov or its 24/7 line, and to file with the FBI IC3. The NCSC advises building a culture in which users report phishing without fear of blame, because users who fear reprisals will not report mistakes.

Download the template

Free, no sign-up. Word (.docx, 3 KB): download. PDF (48 KB): download. Both files carry the same text as this page, edition 16 November 2026.

Sources

  1. Microsoft Learn, Phishing investigation playbook
  2. CISA, Phishing Guidance: Stopping the Attack Cycle at Phase One (October 2023)
  3. NCSC, Phishing guidance for organizations

Last reviewed 16 November 2026. Each source above was read that day.