Email Security Fundamentals: The Business Guide
Every business using email needs to understand four fundamentals: authentication protocols to prevent spoofing, content filtering to block malicious messages, encryption for sensitive data, and user training to catch what technology misses.
Nathan Hill-Haimes
Technical Director
Most businesses have *something* in place — a spam filter, a Microsoft 365 subscription, the default settings their IT provider switched on years ago. The problem is the distance between "something" and a properly configured posture. That distance is exactly where successful attacks land. Email remains the number one delivery route for cyber attacks, and phishing is the most common breach vector reported by UK organisations (NCSC). If you want a practitioner's view of how these controls fit a wider defence, our managed cybersecurity approach treats email as the front door — because attackers do.
This guide gives you the framework to assess where you are and what you still need. It is the four pillars, in the order we deploy them for clients.
What are the four pillars of email security?
The four pillars are authentication, filtering, encryption and user training. Authentication proves your email is genuinely yours and stops criminals spoofing your domain. Filtering blocks malicious inbound content. Encryption protects message contents. Training equips staff to catch what slips through. No single pillar is sufficient on its own — they work as a layered system.
Think of it as defence in depth applied to one channel. Authentication and filtering are the technical perimeter; encryption protects the payload; training is the human backstop. Skip any one and you leave a predictable hole. The sections below cover each pillar, what good looks like, and the mistakes we see most often when auditing UK SME email setups.
Pillar 1: How does email authentication stop spoofing?
Email authentication uses three DNS-published protocols — SPF, DKIM and DMARC — to prove a message genuinely came from your domain. Email was designed without any sender verification, so anyone could claim to send from your address. These three records close that gap and stop your domain being used in phishing campaigns against your own customers.
The protocols build on each other, so deploy them in order. Here is what each one does:
| Protocol | What it does | Common mistake |
|---|---|---|
| SPF (Sender Policy Framework) | Publishes a DNS list of mail servers authorised to send for your domain; receivers reject mail from anywhere else | Not listing every legitimate sender (CRM, helpdesk, transactional email), or exceeding the DNS lookup limit of 10 |
| DKIM (DomainKeys Identified Mail) | Adds a cryptographic signature to every outbound message, verified against a public key in your DNS, proving the message was not altered | Enabling it on the primary domain only, leaving subdomains and secondary sending domains unsigned |
| DMARC (Domain-based Message Authentication, Reporting and Conformance) | The policy layer: tells receivers what to do when SPF or DKIM fail (`p=none`, `p=quarantine`, `p=reject`) and sends you reports | Leaving the policy at `p=none` forever and never advancing to enforcement |
The correct progression is deliberate: deploy DMARC at `p=none` to monitor, use the aggregate reports to find every legitimate sending source, confirm they all pass SPF and DKIM, then move to `p=quarantine` and finally `p=reject`. A policy of `p=reject` gives the strongest protection against your domain being impersonated. If you want the deep dive on the policy layer, our explainer on what DMARC is walks through each tag. The NCSC publishes a free anti-spoofing service and guidance for UK organisations getting these records right (NCSC).
Pillar 2: How does email filtering block malicious content?
Authentication stops fraud *from* your domain, but does nothing about malicious mail arriving *into* it. That is the filtering pillar. A secure email gateway inspects every inbound message against threat intelligence and multiple detection techniques, quarantining or stripping anything dangerous before it reaches a mailbox.
Modern gateways layer several methods, because no single technique catches everything:
- Signature-based detection — matches known malware and malicious URLs against threat databases
- Heuristic analysis — flags suspicious characteristics in new, unknown threats based on patterns resembling known attacks
- Sandboxing — detonates attachments in an isolated environment to watch their behaviour before delivery
- Machine learning — spots anomalous content, headers and metadata that indicate phishing, even with no matching signature
Microsoft 365 includes Exchange Online Protection on all plans and Microsoft Defender for Office 365 on Business Premium and above (Microsoft). For higher-risk environments, AMVIA layers the Barracuda email security suite on top for deeper filtering and attachment defence. Other gateways from vendors such as Mimecast and Proofpoint occupy the same market space. Whatever the tool, filtering pairs naturally with active phishing protection — the gateway blocks the volume, and your wider controls handle what gets through.
Pillar 3: What encryption does business email need?
Filtering protects your inbox; encryption protects the contents of messages you send and receive. There are three levels, and most UK SMEs need the first two: TLS for everyday transit and message-level encryption for sensitive external mail. End-to-end encryption is reserved for defined high-trust relationships.
| Encryption level | What it protects | When to use it |
|---|---|---|
| TLS (Transport Layer Security) | Email in transit between mail servers; automatic between major providers | Always-on baseline; does not protect stored messages |
| Message-level (e.g. Microsoft 365 Message Encryption) | Message content so only the intended recipient can open it | Sending sensitive data to external recipients without certificates |
| S/MIME or PGP | End-to-end content using certificates or key pairs | Defined partner relationships where both sides hold the infrastructure |
For most businesses, enabling TLS enforcement and configuring Microsoft 365 Message Encryption for sensitive mail covers the practical requirement. Pushing S/MIME across a whole workforce is rarely worth the operational cost. Encryption choices also sit inside your wider Microsoft 365 security configuration, which is where AMVIA usually tunes these settings for clients.
Pillar 4: Why does user training still matter?
Technical controls cut the volume and impact of threats but never reach zero. The human layer — staff who recognise a suspicious email and know how to report it — catches the small percentage that defeats filtering. Effective training is a continuous programme, not a once-a-year slideshow, and the reporting culture matters as much as the content.
A programme that actually changes behaviour includes:
- Regular awareness sessions covering current phishing and business email compromise tactics
- Simulated phishing with immediate, contextual feedback when someone clicks
- A clear, fast reporting route so staff can escalate suspicious mail
- A culture where reporting a suspected phish is normal and praised, never embarrassing
The NCSC's Cyber Essentials scheme — which AMVIA supports clients to achieve, and holds the Cyber Essentials Plus certification ourselves — sets the foundational technical controls (secure configuration, access control, malware protection) that complement this four-pillar approach (Cyber Essentials, gov.uk). Training plus certification is the combination that holds up under a real attack.
What does AMVIA actually recommend?
If we audit a typical UK SME, the priority order is consistent: turn on MFA and fix SPF first, get DMARC into monitoring, layer Defender for Office 365 (and Barracuda where the risk justifies it), enable message encryption for sensitive mail, then run continuous phishing training. Most of the wins are configuration, not new spend.
The single most common finding is an SPF record that has not kept up with the business — new sending services bolted on over the years, never added to the record, so legitimate mail is at risk while the domain is still spoofable. The second is a DMARC policy stuck at `p=none` indefinitely. Both are fixable in an afternoon. For a managed approach across endpoints and mail, Microsoft Defender for Business gives smaller teams enterprise-grade protection without a dedicated security hire. One provider, security-first, Microsoft-certified.
Do Your Email Authentication Records Pass?
Many businesses have incomplete or misconfigured SPF, DKIM and DMARC records. AMVIA can check your DNS configuration and correct any issues that leave your domain vulnerable to spoofing.
Frequently Asked Questions
If you have nothing in place, MFA on email accounts and a correctly configured SPF record are the highest-priority starting points. MFA prevents account takeover if credentials are phished; SPF stops your domain being spoofed in outbound phishing aimed at others. Both are quick to implement and cost nothing in licensing.
Free DNS lookup tools let you view your domain's SPF record and check for common errors, including syntax mistakes, exceeding the DNS lookup limit of 10, and missing legitimate sending sources. Your email provider can confirm which IP addresses or includes need to be present. Recheck it whenever you add a new system that sends mail on your behalf.
A DMARC policy of `p=quarantine` tells receiving servers to send failing emails to the spam or junk folder. A policy of `p=reject` tells them to refuse delivery entirely. Reject gives stronger protection but requires confidence that every legitimate sending source is correctly authenticated first, or you risk blocking your own mail.
Signature-based filtering cannot detect zero-day threats by definition, because they have no known signature. Modern gateways address this with behavioural sandboxing — detonating attachments to observe what they do — and machine-learning models that flag suspicious patterns without a signature match. These methods improve detection significantly but are not infallible, which is why training remains essential.
UK GDPR does not mandate specific encryption standards but requires appropriate technical measures to protect personal data. Sending personal data — particularly special category data — by unencrypted email to external recipients may be judged inadequate under the accountability principle. Encrypted email or a secure file-sharing portal is the appropriate control (ICO).
Retention varies by sector and communication type. HMRC generally expects business records to be kept for at least 6 years. Financial services firms under FCA rules may have obligations of 5-7 years for specific communication types. Legal firms may hold longer professional-liability considerations. Your IT and legal advisors should define a retention policy that meets your specific obligations.
Related Reading
Email Protection: Layers of Defence Explained
A deeper look at how the layers of email protection work together to defend against modern threats.
What Is DMARC?
DMARC explained in plain language: how the protocol works and how to implement it for your business domain.
Business Email Security
A complete guide to protecting your business email from phishing, spoofing, BEC and malware.
Protect your business → Get Cybersecurity Assessment