ISO 27001 email security controls: where SPF, DKIM and DMARC fit

If you are building or auditing an ISO 27001 management system, you may be asked how you stop criminals sending email that pretends to be you. The honest answer is that ISO/IEC 27001:2022 and its guidance standard, ISO/IEC 27002:2022, never name SPF, DKIM, DMARC or MTA-STS. The standards are written to be technology-neutral. They describe outcomes, and you choose the controls that achieve them.

That means email authentication is something you map to Annex A, not something Annex A asks for by name. This guide suggests a reasonable mapping and explains how to evidence it.

A note on sources. The ISO texts are paid documents. The control summaries below come from published explanations of the 2022 controls, not from the standard itself. Check the wording against your licensed copy before you quote it in your Statement of Applicability.

The controls that fit best

5.14 Information transfer

This is the closest match. The control covers rules and agreements for transferring information by any means, including electronic messaging. Published guidance on it calls for stronger authentication when information is sent over public networks. It also gives examples such as limiting automatic forwarding [1].

SPF, DKIM and DMARC are the standard way to authenticate email between organisations on the public internet. MTA-STS and TLS-RPT protect messages in transit. All of these sit naturally under 5.14.

There is a useful precedent here. The Dutch government's information security baseline, the BIO, added DMARC, DKIM and SPF as measure 5.14.01 in 2026. The measure number sits under 5.14, the same number as the ISO information transfer control [6]. Dutch rules also require DMARC, on a comply-or-explain basis, on government domains, including domains that are not used for email [6].

8.21 Security of network services

Email is named as an example of a network service in published guidance on this control. The control asks you to set out and monitor security features such as authentication and encryption for those services [2]. Requiring TLS for mail (MTA-STS) and making sure your email provider signs outgoing mail (DKIM) fit here.

8.9 Configuration management

This control asks you to define, document and review security configurations [4]. DNS records are configuration. Keeping your SPF, DKIM and DMARC records as a controlled baseline, with an owner and a change process, is a straightforward way to show that this control covers email.

8.16 Monitoring activities

Guidance on this control expects monitoring of inbound and outbound traffic and of key services such as DNS servers [3]. DMARC aggregate reports and TLS-RPT reports are a monitoring feed. They show who is sending email as your domain and whether mail to you is arriving securely. If you collect the reports, someone needs to read them.

5.7 Threat intelligence

This control asks you to collect and analyse information about threats [5]. DMARC reports often reveal spoofing campaigns that use your name, which is threat intelligence about your own brand.

What an auditor may ask

Because the standard doesn't name the records, an auditor will look for consistency with your own risk assessment. Useful evidence includes:

The NCSC's email security guidance explains each record and the order in which to set them up [7]. The GOV.UK email security standard is a well-documented benchmark if you want a recognised target. It requires SPF, DKIM, DMARC, MTA-STS and TLS-RPT for public sector email domains [8].

Don't over-claim

Two cautions are worth noting in your documents:

The upside is that email authentication is unusually easy to evidence. The records are public, so anyone, including an auditor or a customer's procurement team, can check them in seconds.

Check your domain free

You can check your domain for free at faultypacket.co.uk. It reads your public SPF, DKIM, DMARC, MTA-STS, TLS-RPT, DNSSEC and CAA records and explains what it finds in plain English, which makes a useful snapshot for your evidence file. If something needs fixing, the £24 Fix Pack gives you the exact records to add, in a safe order, and re-checks each one live once you've added it.

DNS on Cloudflare? Fix it for me adds your SPF and DMARC records in one click (£49 plus VAT, Fix Pack included). To hear if anything changes later, monitoring checks your domain every day from £4 a month.

Sources

  1. ISMS.online, "ISO 27001:2022 Annex A Control 5.14 – Information Transfer": https://www.isms.online/iso-27001/annex-a-2022/5-14-information-transfer-2022/
  2. ISMS.online, "ISO 27001:2022 Annex A Control 8.21 – Security of Network Services": https://www.isms.online/iso-27001/annex-a-2022/8-21-security-of-network-services-2022/
  3. ISMS.online, "ISO 27001:2022 Annex A Control 8.16 – Monitoring Activities": https://www.isms.online/iso-27001/annex-a-2022/8-16-monitoring-activities-2022/
  4. ISMS.online, "ISO 27001:2022 Annex A Control 8.9 – Configuration Management": https://www.isms.online/iso-27001/annex-a-2022/8-9-configuration-management-2022/
  5. ISMS.online, "ISO 27001:2022 Annex A Control 5.7 – Threat Intelligence": https://www.isms.online/iso-27001/annex-a-2022/5-7-threat-intelligence-2022/
  6. Forum Standaardisatie, "DMARC" (update 1 Apr 2026): https://www.forumstandaardisatie.nl/open-standaarden/dmarc
  7. NCSC, "Email security and anti-spoofing": https://www.ncsc.gov.uk/collection/email-security-and-anti-spoofing
  8. GOV.UK, "Securing government email": https://www.gov.uk/guidance/securing-government-email