easm.chUnderstanding your external attack surface

E-mail security

SPF, DKIM and DMARC prevent fraudsters from sending e-mails in your name. STARTTLS and MTA-STS protect the transport.

1 min read · in plain words and for experts

Diagram
  1. Forged e-mail
  2. Recipient checks SPF and DKIM
  3. DMARC decides
  4. Rejected

The forged sender

The sender of an e-mail is as easy to forge as the sender on an envelope. Fraudsters exploit this: an invoice “from you” to your customers, a payment instruction “from the boss” to accounting. Without protection, such e-mails often get through.

Three protection mechanisms

  • SPF is the list of post boxes your mail may come from.
  • DKIM is a seal on every e-mail that only your mail server can apply.
  • DMARC tells recipients what to do with e-mails without a valid post box and without a seal: monitor, move to spam or reject.
Only with DMARC set to “reject” (p=reject) is your domain really locked against forgery. “Monitor” (p=none) is the first step, not the goal.

Locked in transit

Between mail servers, an e-mail should travel encrypted (STARTTLS). With MTA-STS you also specify that your mail is only accepted when encrypted.

What you can do

Introduce DMARC in monitoring mode first, evaluate the reports, add all legitimate senders (newsletter, accounting, CRM) to SPF and DKIM and then tighten step by step. Domains that send no e-mail at all should also be locked.

Inbox Guard Switzerland explains the path to p=reject in detail: igs.ch/wissen.

In short

  • Without DMARC anyone can forge e-mails with your domain.
  • SPF names the permitted servers, DKIM signs, DMARC decides.
  • The goal is p=reject – step by step, after evaluating the reports.
  • STARTTLS and MTA-STS protect the transport.

Learn more: E-mail protocols (mail.eam.ch) – SMTP, IMAP, SPF, DKIM, DMARC: how e-mail works and where it is heading.