AICI · Free practical security guides · 8 min read
Suspicious email at work: a first-response playbook for small teams
What to do before clicking, after clicking and after credential exposure — with role-specific decisions and an evidence checklist.
A suspicious email becomes an incident only after evidence and context are assessed. Sending every unusual message to every colleague can spread risk; deleting everything can destroy useful evidence. This playbook helps a small business triage safely while keeping human judgment and its incident-response policy in control.
Who this guide is for
Employees, team leads, IT administrators and small-business owners without a dedicated security operations center.
1. Before you click: verify outside the message
Treat requests for urgent payment, password reset, MFA codes or file sharing as untrusted until confirmed through an independent channel. A familiar logo, display name or HTTPS padlock does not prove that a sender is legitimate. Do not use a phone number or reply-to address taken from the suspicious email for verification.
- Pause: do not open links, download attachments or approve unexpected MFA prompts.
- Verify the request using a known phone number, company directory or a bookmark entered manually.
- Report the message through the organization's standard phishing-report process, preserving headers where practical.
2. If someone clicked: distinguish exposure from compromise
Opening a link is not automatically the same as surrendering credentials or executing malware. Ask what happened: page opened, password entered, file downloaded, macro enabled, or OAuth consent granted? That distinction changes the response. Avoid running unapproved tools on an employee's device or collecting personal credentials through chat.
- Inform IT/security immediately, state the time and the exact interaction, and preserve the original message.
- If a password was submitted, change it from a trusted session/device and revoke affected sessions as your identity provider permits.
- If a file was run or malware is suspected, follow your organization's isolation and evidence-preservation procedure.
3. Contain, recover and improve without blame
Security staff should check affected accounts and devices within their authorization, review identity-provider sign-in activity, monitor mailbox rules and suspicious forwarding, and notify impacted parties according to legal and organizational requirements. Record a clear timeline and whether any data access is actually confirmed. Do not label an incident a breach without evidence.
- Record sender, timestamp, affected systems, user actions and evidence location with minimum necessary personal data.
- Complete remediation (session revocation, MFA re-enrollment where indicated, endpoint response) and verify normal access.
- Update filters, training examples and escalation instructions based on the actual root cause.
Decision exercise — hypothetical payroll email
An employee receives an urgent message claiming payroll information must be confirmed. They open a link but do not enter a password. Their colleague enters a password and approves an unexpected login prompt.
What the response should show
Both report the message, but the second case needs urgent identity/session containment and sign-in investigation. The first still merits triage and endpoint checks as appropriate. Do not assume a breach in either case before reviewing evidence.
Deliverable: a simple report channel, a time-stamped incident record, clear exposure categories and a recovery checklist. This guide does not replace your organization's incident-response plan.