Article

Five ways to solve the email security problem

Email reaches everyone and is easy to fake, so it remains the most common route for phishing, malware and payment fraud. Five layers reduce the risk significantly.

The short answer

No single product solves it. Attackers steal passwords, deliver malware, impersonate executives and redirect payments, so combine technology and process in five layers:

  1. Authenticate your domainSPF, DKIM and DMARC, so others cannot easily send as you.
  2. Protect accountsMFA, preferably phishing-resistant.
  3. Filter and inspectIncoming mail, links and attachments.
  4. Prepare your peopleTraining, simulations and easy reporting.
  5. Verify paymentsPayment and account changes confirmed through a separate channel.

1. Authenticate your email domain

Without it, anyone can send mail that appears to come from your address to customers, suppliers or staff.

StandardWhat it does
SPF (Sender Policy Framework)Lists the servers allowed to send for your domain
DKIM (DomainKeys Identified Mail)Signs messages to prove they were not altered
DMARC (Domain-based Message Authentication, Reporting and Conformance)Tells receivers what to do with failures, and reports to you

The Canadian Centre for Cyber Security says complete protection requires all three, set to tell recipients to reject inauthentic messages. Move DMARC gradually from "none" (monitoring) through "quarantine" to "reject", and protect domains you do not use for email (Cyber Centre). Monitoring reports often reveal forgotten senders (a newsletter tool, billing system or website form) to add before you enforce.

2. Protect accounts with strong MFA

Most compromises start with a stolen password. MFA stops many, but the Cyber Centre notes attackers defeat common methods through MFA fatigue (repeated push prompts), token theft and machine-in-the-middle phishing. It strongly recommends FIDO-based, phishing-resistant options such as security keys and passkeys (Cyber Centre).

More detail: MFA steps
  • Require MFA on every mailbox, with no exceptions for executives.
  • Use phishing-resistant methods for administrators and finance staff first.
  • Block legacy email protocols that bypass MFA.
  • Enable number matching or similar protections if you use push approvals.

3. Filter and inspect incoming mail

Built into Microsoft 365 or Google Workspace or added separately, filtering should:

Sandbox attachments

And block risky file types.

Check links when clicked

Not only on delivery.

Flag outsiders

External senders and look-alike domains.

Spot impersonation

Of executives and known suppliers.

Block known bad

Malicious domains and IP addresses, as the Cyber Centre recommends.

Filtering reduces volume; it never catches everything (Cyber Centre).

4. Prepare your people

Staff are not the weakest link; they are the last line of defence when filters miss. The Cyber Centre recommends phishing simulations, awareness training and clear procedures to verify and report suspicious messages. Give everyone a one-click report button, thank reporters (false alarms included) and never punish reporting a mistake.

More detail: training that works

5. Verify payments and account changes out of band

Business email compromise (fake requests to change banking details, pay urgent invoices or buy gift cards) often involves no malware, sometimes from a real, compromised supplier mailbox.

  • Call a known number (not one in the email) before changing any banking details.
  • Two people approve payments above a set amount.
  • Urgency, secrecy and new payment instructions are warning signs.
  • Your incident plan covers phishing and payment fraud, including money already moved.

Email security checklist

  • SPF published and accurate for all sending services
  • DKIM signing enabled for our domain
  • DMARC in place, with a plan to move from "none" to "reject"
  • Unused domains protected against spoofing
  • MFA on every mailbox; phishing-resistant MFA for admins and finance
  • Legacy authentication blocked
  • Attachment sandboxing and time-of-click link checks enabled
  • External sender warnings turned on
  • One-click phishing report button available to all staff
  • Callback verification required for banking changes
  • Incident plan covers compromised mailboxes and payment fraud

Limitations

These measures reduce risk, not remove it: DMARC does not stop look-alike domains, and training fades without reinforcement. Review controls yearly and whenever a new service sends email for you. Our email security service sets up domain authentication, filtering and account protection; cybersecurity awareness training prepares staff. On Microsoft 365, see our security baseline.

Sources and further reading

Product capabilities and guidance change. These are the primary sources this article relies on, checked on the review date above.

  1. Don't take the bait: Recognize and avoid phishing attacks (ITSAP.00.101), Canadian Centre for Cyber Security
  2. Implementation guidance: email domain protection (ITSP.40.065), Canadian Centre for Cyber Security
  3. Secure your accounts and devices with multi-factor authentication (ITSAP.30.030), Canadian Centre for Cyber Security

This article is general information, not legal, accounting or security advice for your specific situation. Examples are hypothetical unless stated otherwise.

Talk to Promatics

Get a straight answer for your situation

General advice only goes so far. Tell us about your environment and we will tell you what we would do, what it would cost and what to watch out for.

  • A named specialist who owns the outcome, not a chat window
  • Advice checked against your actual systems, contracts and risks
  • Written scope and costs in CAD before any work starts