Guide Email Security

Email Security Guide: SPF, DKIM, DMARC and Beyond

Email remains one of the most common entry points for attacks: phishing, business email compromise, and malware delivery often start here. This guide covers the technical controls, configuration steps, and process changes that reduce your exposure.

21 August 2026
Updated 18 November 2026
7 min read
Key takeaways
  • Email is one of the most common initial attack vectors. Phishing, business email compromise, and malware delivery often start with a message in someone’s inbox.
  • SPF, DKIM, and DMARC are DNS records that together make direct spoofing of your domain much harder. DMARC at p=reject is the end state; many organisations sit at p=none for years longer than they should.
  • MFA on email accounts is not optional. Credential phishing is one of the most common ways attackers access mailboxes; without MFA, a single stolen password hands them the account. For administrators and higher-risk accounts, use phishing-resistant methods such as FIDO2 security keys and passkeys.
  • Business email compromise causes more financial loss than any other email threat. The critical defence is a process: no payment change instruction is acted on without out-of-band verification.
  • Email filtering reduces the volume of malicious messages reaching users but does not eliminate it. Staff training closes the gap.

Why email is still the biggest attack surface

Every employee has a mailbox. Attackers know this. Email carries links, attachments, and requests for action, which is exactly what credential phishing, BEC, and malware delivery need to work.

Three attack types account for most of the damage:

  • Phishing: messages designed to trick recipients into clicking a malicious link, handing over credentials, or downloading malware. Spear phishing targets specific individuals with personalised content.
  • Business email compromise (BEC): attackers impersonate a supplier, colleague, or executive to redirect payments or extract sensitive data. No malware involved, just a convincing email and a process that does not verify.
  • Malware delivery: attachments or links that install ransomware, remote access tools, or information stealers when opened.

SPF, DKIM, and DMARC: the authentication stack

SPF, DKIM, and DMARC authenticate outbound email and tell receiving servers what to do when a message fails that check. Configure them in order.

SPF (Sender Policy Framework)

An SPF record lists the IP addresses and mail servers authorised to send email from your domain. A basic SPF record for a Microsoft 365 organisation:

v=spf1 include:spf.protection.outlook.com -all

The -all at the end signals a hard fail for any server not on this list. The receiving server decides what actually happens to the message, usually by combining the SPF result with DMARC and its own filtering. Common legitimate sending sources beyond your primary mail provider include marketing platforms (Mailchimp, HubSpot), CRM systems, and transactional email services (SendGrid, Postmark). Include all of them before moving to -all.

DKIM (DomainKeys Identified Mail)

DKIM adds a cryptographic signature to outbound email. The sending server signs each message with a private key; the corresponding public key is published in your DNS. Receiving servers verify the signature to confirm the message genuinely came from your domain and has not been tampered with in transit.

In Microsoft 365, enable DKIM in the Microsoft Defender portal under Email & collaboration > Policies & rules > Threat policies > Email authentication settings, on the DKIM tab. Microsoft generates and manages the key pair; publish two CNAME records in your DNS pointing to Microsoft’s infrastructure.

DMARC (Domain-based Message Authentication, Reporting and Conformance)

DMARC checks that a message passed SPF or DKIM with a domain that aligns with the visible From address, tells receiving servers what to do when that check fails, and asks them to send reports back to you. Start at monitoring stage:

v=DMARC1; p=none; rua=mailto:[email protected]

Once you are confident your SPF and DKIM capture all legitimate sources, move to quarantine and then reject:

v=DMARC1; p=reject; rua=mailto:[email protected]

p=reject is the end state. It asks receiving servers to reject messages that fail the applicable authentication and alignment checks. How effective it is depends on receivers enforcing that policy. DMARC reduces direct spoofing of your domain, but it does not stop look-alike domains, compromised legitimate accounts, or display-name impersonation.

Many organisations are stuck at p=none

DMARC adoption has grown but many organisations publish a monitoring record and never progress to enforcement. The gap is usually legitimate email sources not captured in SPF: a marketing platform, a CRM, an old newsletter system. Work through your DMARC reports to identify and authorise legitimate senders, then move to quarantine and reject. At p=none, receivers get no instruction to block messages that spoof your domain.

MFA on email accounts

Credential phishing hands attackers a valid username and password. Without MFA, that is enough to access the mailbox, read email, set forwarding rules, and move to the next target.

MFA significantly reduces the risk of access with stolen passwords, but some methods can still be bypassed by adversary-in-the-middle phishing, session token theft, or weak account recovery processes. For administrators and higher-risk accounts, prioritise phishing-resistant methods such as FIDO2 security keys and passkeys, and protect sessions and devices as well.

For Microsoft 365, enable MFA through Conditional Access policies or Security Defaults. Require MFA for all users, including non-administrators. Authenticator apps with number matching (such as Microsoft Authenticator) are stronger than SMS codes, but they are not phishing-resistant. FIDO2 security keys and passkeys go further by binding authentication to the legitimate site, so they will not authenticate against a phishing page.

Email filtering and threat protection

ControlWhat it doesMicrosoft 365
Anti-spam filteringBlocks bulk email and known spam patternsExchange Online Protection (EOP)
Anti-phishing policiesDetects impersonation of users and domains; adds safety tipsEOP + Defender for Office 365 Plan 1
Safe LinksRewrites URLs and checks them at click time against threat intelligenceDefender for Office 365 Plan 1
Safe AttachmentsOpens attachments in a sandbox before delivering to the userDefender for Office 365 Plan 1
Attack simulation trainingSends simulated phishing campaigns to users; tracks who clicksDefender for Office 365 Plan 2

For most UK businesses on Microsoft 365, Defender for Office 365 Plan 1 (included in Business Premium) provides a meaningful uplift over EOP defaults. Enable Safe Links and Safe Attachments with real-time scanning rather than time-of-delivery scanning only.

Business email compromise: the process problem

Business email compromise is the attack that causes the most financial loss because it bypasses technical controls. The attacker sends a well-crafted email requesting a payment change or transfer. By the time the fraud is identified, the money has moved.

Technical controls that reduce BEC exposure: DMARC at p=reject makes direct spoofing of your domain much harder; anti-impersonation policies flag emails from look-alike domains; external email banners flag messages from outside your organisation; blocking auto-forwarding rules to external addresses.

The control that blocks most BEC attempts has nothing to do with technology: no payment change instruction received by email gets acted on without a phone call to a number you already have on file. Not the number in the email.

Train for BEC specifically

Standard phishing training focuses on suspicious links and attachments. BEC emails have neither. They look like normal messages from known contacts. Add BEC scenarios to your simulation programme: fake invoice changes, fake CEO payment requests, fake HR benefit updates.

Email security baseline checklist

ControlStatus to achieve
SPF record publishedAll legitimate sending sources included; -all qualifier
DKIM enabledEnabled for all sending domains
DMARC record publishedp=reject; rua reporting configured
MFA on all mailboxesEnabled for all users; phishing-resistant methods for administrators and higher-risk accounts
Email filteringSafe Links and Safe Attachments enabled; real-time scanning
Anti-impersonation policiesKey executives and domains protected
External sender labellingBanners on external email enabled
Auto-forward blockingOutbound forwarding to external addresses blocked by policy
BEC process controlsOut-of-band verification required for payment changes
Phishing simulation programmeRunning quarterly at minimum; click-to-report trend tracked
About the author
Ryland Deakin
Lead Consultant, Cyvra · CISM · CompTIA Security+ · MCP

Ryland has delivered cybersecurity, compliance, and IT management programmes for regulated organisations across the UK and the Netherlands for over 20 years. View full profile

Frequently asked questions

What is the difference between SPF, DKIM, and DMARC?

SPF specifies which mail servers are authorised to send email on behalf of your domain. DKIM adds a cryptographic signature to outbound messages that receiving servers can verify. DMARC requires SPF or DKIM to pass with a domain aligned to the From address, tells receiving servers what to do with messages that fail, and requests reports. All three work together; DMARC relies on SPF and DKIM being configured correctly so that legitimate email is not blocked.

What is business email compromise and how do you prevent it?

Business email compromise (BEC) is an attack where fraudsters impersonate a trusted contact to redirect payments or extract sensitive information. Prevention combines technical controls (DMARC enforcement, email filtering) with process controls (out-of-band verification for financial requests) and staff training to recognise impersonation attempts.

Does Cyber Essentials cover email security?

Cyber Essentials covers malware protection and access control, which includes some email security controls. It does not specifically mandate SPF, DKIM, or DMARC configuration, but those records are expected as part of a reasonable security baseline for any organisation sending email.

Email Security

Need help hardening your email security?

We configure email authentication records, review Microsoft 365 or Google Workspace security policies, and run phishing simulation programmes for UK businesses.

Disclaimer: This article is for general informational purposes only and does not constitute legal, regulatory, or professional advice. Cyvra makes no warranty as to the accuracy or completeness of this content, which may not reflect the most current regulatory developments. Readers should seek independent legal and regulatory advice appropriate to their specific circumstances. Cyvra accepts no liability for any loss arising from reliance on this content.