Phishing prevention works best when employees have a simple way to pause, verify, and report suspicious messages. This practical checklist covers common email red flags, safe verification steps, reporting workflows, and training routines for small businesses.
Overview
Phishing is an attempt to persuade someone to reveal information, open a harmful file, transfer money, or take another unsafe action. The message may arrive by email, text, collaboration platform, or social media. In business email compromise, an attacker may impersonate an executive, supplier, customer, or attorney and use a plausible request rather than an obvious scam.
No single tool can eliminate the risk. Effective phishing prevention for businesses combines email security controls, multifactor authentication, payment procedures, employee training, and a reporting process that people will actually use. The goal is not to expect employees to identify every attack perfectly. The goal is to make suspicious requests easier to question and mistakes faster to contain.
Use the following baseline as an email security checklist for a small business:
- Require multifactor authentication for email, financial, administrative, and other high-value accounts.
- Use a password manager and unique passwords for business accounts.
- Enable available spam, phishing, malicious-link, and attachment protections in your email platform.
- Define a reporting button, mailbox, or chat channel for suspicious messages.
- Require a second verification method for payment changes, urgent transfers, and sensitive data requests.
- Train employees before they need to make a high-pressure decision, then reinforce the process regularly.
For related access controls, see the MFA and password policy checklist. Phishing readiness should also be part of your broader small business incident response plan.
Checklist by scenario
Email red flags: pause before clicking
Teach employees to treat combinations of warning signs as reasons to stop and verify. A single unusual detail may have an innocent explanation, but urgency plus a payment request or unfamiliar link deserves extra scrutiny.
| Red flag | What to check | Safe response |
|---|---|---|
| Unexpected urgency | The sender demands immediate action, secrecy, or a response outside normal hours. | Pause. Contact the requester through a known channel rather than replying. |
| Look-alike sender | The display name looks familiar, but the address or domain contains a small change. | Inspect the full address and compare it with a trusted record. |
| Unexpected link | The visible text does not match the destination, or the link uses a shortened or unfamiliar address. | Do not click. Open the service from a saved bookmark or type its address manually. |
| Unexpected attachment | The file is unsolicited, password-protected, or uses a format you do not normally receive. | Confirm the file with the sender using a separate channel before opening it. |
| Credential request | The message asks for a password, verification code, recovery phrase, or sign-in through an email link. | Do not provide the information. Navigate directly to the service if an account check is needed. |
| Payment or bank change | Invoice details, payment instructions, or account information have changed unexpectedly. | Verify the change using a known telephone number or established contact process. |
| Unusual tone or context | The writing, signature, request, or conversation does not fit the sender or business relationship. | Treat the mismatch as a signal to verify, even if the address appears familiar. |
Credential theft: if someone clicked or entered information
- Tell the employee to stop interacting with the message and report it immediately. Do not delete the message before the security or IT contact can review it, unless your process says otherwise.
- From a trusted device or a manually entered service address, change the affected password. Change it anywhere else it was reused.
- End active sessions, review recent sign-ins, and remove unfamiliar recovery methods, forwarding rules, applications, or delegated access.
- Confirm that multifactor authentication is still enabled and that its registered devices or methods are recognized.
- Check whether the account sent messages or shared files while compromised. Warn affected contacts using a separate communication method.
- Record what happened, when it happened, what information was entered, and which systems may be affected.
If malware may have been downloaded, disconnect the device from networks without destroying evidence, then follow your incident response plan or contact your designated technical support.
Invoice fraud and business email compromise
Payment requests deserve a process, not a judgment call. Before approving a new supplier, changed bank details, urgent wire, gift card request, or unusual refund:
- Compare the request with the purchase order, contract, invoice history, and normal payment pattern.
- Call a known number from your records, not a number supplied in the suspicious message.
- Require approval from a second person who is not part of the original email thread.
- Do not rely on a familiar display name, copied signature, or apparently authentic email thread.
- Document who verified the request and which source confirmed the details.
If funds were sent in response to a suspected scam, contact the financial institution immediately and preserve the messages, payment records, and timeline. Prompt reporting may help the institution assess available recovery or protective actions.
How to report phishing at work
Give employees one clear route: a built-in “report phishing” control, a dedicated mailbox, or a security channel monitored by a named person. The workflow should be:
- Report: Forward or flag the message using the approved method. Include a short note about whether anyone clicked, replied, opened an attachment, or shared information.
- Preserve: Keep the original message and relevant headers when your email system supports them. Avoid forwarding suspicious content to broad groups.
- Escalate: Immediately notify the responsible person about credential entry, payment activity, malware, exposed personal data, or executive impersonation.
- Contain: The responsible person can isolate affected accounts or devices, block known indicators, and warn recipients if necessary.
- Learn: Record the type of attack, the control that worked or failed, and one improvement to make.
Make clear that reporting a mistake is safer than hiding it. A fast report gives the business more options.
What to double-check
Before acting on a sensitive request
- Is the request consistent with the sender’s role, normal timing, and previous instructions?
- Am I using contact information from a trusted record rather than the message?
- Does the request involve money, credentials, personal information, confidential documents, or unusual secrecy?
- Can a second person review the decision before it becomes irreversible?
- Would it be safer to open the service directly instead of using the message link?
For administrators and owners
- Are former employees’ accounts, sessions, forwarding rules, and delegated permissions removed promptly?
- Are administrator, finance, and mailbox accounts protected by multifactor authentication?
- Can employees report messages without complicated technical steps?
- Are email protections, domain authentication settings, and alerting configured according to your provider’s current guidance?
- Do payment and customer-data workflows include independent verification?
- Are backups protected and tested so a phishing-related compromise does not become a wider operational crisis? Review the small business backup strategy for a related checklist.
A practical training plan
Start with a short onboarding lesson covering red flags, reporting, password safety, and the payment-verification rule. Reinforce it with a brief monthly reminder that uses a current example from your business context. Each quarter, run a short discussion or exercise: present a suspicious request, ask employees how they would verify it, and rehearse the reporting path. Keep exercises educational rather than punitive, and avoid collecting unnecessary personal information about participants.
Track useful operational measures: how many employees know the reporting route, how quickly reports reach the right person, whether verification was completed before payment, and whether repeated problems point to a process or technical control that needs attention.
Common mistakes
- Relying on grammar alone: Polished messages can be fraudulent, and legitimate messages can contain errors. Verify the request and destination.
- Trusting internal-looking email: A familiar name, logo, signature, or compromised mailbox is not independent proof.
- Using the suspicious message to verify it: Replying to the same thread or calling its supplied number may connect you to the attacker.
- Making employees guess what to do: A vague instruction to “tell IT” delays reporting. Name the channel and backup contact.
- Treating training as a one-time event: Staff, tools, vendors, and attack patterns change. Short recurring practice is easier to maintain.
- Deleting evidence: Preserve the message and timeline according to your internal process so the incident can be investigated.
- Skipping recovery checks: Changing a password is not enough if an attacker added a forwarding rule, recovery method, session, or third-party application.
When to revisit
Review this phishing prevention checklist monthly as a quick operational check and run a focused training exercise at least quarterly. Revisit it immediately when your email provider, payment workflow, customer-data process, or remote-work tools change. It also deserves a review before seasonal planning cycles, hiring surges, major launches, periods of increased invoicing, and any change in executive or finance responsibilities.
At each review, update the examples employees see, confirm the reporting route works, test a payment-verification scenario, and check whether email-security features or account controls have changed. Review your phishing prevention program alongside your incident response plan. If sensitive documents are commonly exchanged by email, compare the workflow with guidance on secure document sharing for business.
Next action: Choose one reporting channel, write the exact payment-verification rule in a short internal policy, and spend 15 minutes this week practicing the workflow with your team. A clear pause-and-verify habit is one of the most practical foundations of cybersecurity for small business.