Triaging a Phishing Alert, Step by Step
a calm, repeatable routine for the most common alert in the queue
Phishing alerts arrive constantly: reported by users, flagged by filters, or found by a hunt. A reliable routine keeps you fast, consistent and safe. Work in a safe environment and never click links or open attachments on your normal workstation.[1]
1. Collect and secure the sample
Get the original message (as an attachment or in full source form), not a screenshot or forward that strips headers. Note who reported it, when they received it and what they did with it. Record the ticket details.
2. Check the sender and delivery
- Compare From, Reply-To and Return-Path.
- Read the authentication results: SPF, DKIM and DMARC. Remember a pass does not mean safe.
- Look at the first trusted hop in the Received lines.
- Is the domain new, a look-alike, or a compromised legitimate account? Internal "from a colleague" mail may mean an account takeover.
3. Analyze the content safely
- Links: extract the real destinations without clicking. Check reputation and what they redirect to, using a URL analysis service or a sandbox. Watch for shorteners, QR codes and redirects through legitimate sites.
- Attachments: do not open them. Get the file hash, look it up, and detonate it in a sandbox. Be wary of archives, Office files asking to "enable content", HTML files and disk images.
- Language and requests: urgency, payment changes, credential prompts, gift cards.
4. Scope the campaign
- Search the mail system for the same sender, subject, link or file across all mailboxes. How many received it?
- Check who opened, clicked or replied, using proxy, DNS and email logs.
- Check endpoints that handled the file or visited the URL, using EDR telemetry.
5. Decide
Classify it: malicious, spam or marketing, benign/false positive, or needs escalation. Use the evidence, not gut feeling, and write the reason.
6. Contain and remediate
- Remove the messages from all mailboxes.
- Block the sender, domain, URL and file hash where appropriate.
- If anyone entered credentials: reset passwords, revoke sessions and tokens, check MFA registrations and mailbox rules (attackers often add forwarding rules).
- If anyone ran an attachment: isolate the machine and escalate to incident response.
7. Communicate and record
Tell the reporter what happened (and thank them: reporting should always feel safe). Document findings, indicators and actions. Share indicators with the team and feed lessons into filter rules, awareness training and detection tuning.
A closing thought
Speed matters, but accuracy matters more. A short, consistent checklist beats improvisation at 3 a.m.
Sources
Test yourself
My notes
Private — saved only on this device, never sent anywhere.