NIS2 email security checklist

NIS2 asks for cyber hygiene, secured communications and encryption. For email that means SPF, DKIM, an enforced DMARC policy and encrypted delivery.

Applies to
Essential and important entities in the EU, in sectors from energy and health to digital services and manufacturing.
In force
In force in Belgium since 18 October 2024; other EU countries are at different stages.

Check your domain against this list

We only read public DNS records. The domains you check are not stored.

The email checklist

  1. SPF record Art. 21(2)(g)

    Lists the servers that may send as your domain.

    Our check verifies this. How to set it up

  2. DKIM signing Art. 21(2)(g)

    Signs your mail so receivers can verify it came from you and was not changed.

    Our check verifies this. How to set it up

  3. DMARC policy that blocks spoofing Art. 21(2)(g)

    Quarantine or reject stops mail that fakes your domain. Aim for reject.

    Our check verifies this. How to set it up

  4. Subdomains protected Art. 21(2)(g)

    An enforced subdomain policy stops attackers from using made-up subdomains of yours.

    Our check verifies this. How to set it up

  5. DMARC reports monitored Art. 21(2)(b)

    Reports show who sends as your domain, so you notice abuse and misconfigured services.

    Our check verifies this. How to set it up

  6. Encrypted delivery to you (MTA-STS) Recommended Art. 21(2)(h)

    Makes other servers use an encrypted, verified connection when they deliver mail to you.

    Our check verifies this. How to set it up

  7. Reports on failed encryption (TLS-RPT) Recommended Art. 21(2)(h)

    Tells you when other servers could not deliver to you securely.

    Our check verifies this. How to set it up

  8. Staff trained to recognise phishing Art. 21(2)(g)

    Basic cyber hygiene and cybersecurity training are explicit NIS2 measures.

    Not visible from outside: check it yourself.

  9. Evidence for audits

    Keep proof that the measures are in place, such as your DMARC policy history and pass rates.

    Not visible from outside: check it yourself.

What NIS2 asks

Article 21 of the NIS2 directive requires essential and important entities to take appropriate security measures. Three of them concern email directly: basic cyber hygiene and training, the use of cryptography and encryption, and secured communications. NIS2 doesn't name SPF, DKIM or DMARC, but they are the standard hygiene for email, and phishing is how most incidents start.

You are also affected if you are not in scope yourself: NIS2 entities have to manage the security of their suppliers, so their security questionnaires ask about your email too.

NIS2 in Belgium

Belgium transposed NIS2 with the law of 26 April 2024, which applies since 18 October 2024. The Centre for Cybersecurity Belgium (CCB) supervises it and recommends that organisations protect their domains with SPF, DKIM and DMARC. The CCB's CyberFundamentals framework is the usual way for Belgian organisations to show they meet NIS2.

Where to start

  1. Publish SPF and turn on DKIM for every service that sends as your domain.
  2. Publish DMARC with p=none and read the reports until all your real mail passes.
  3. Move to p=reject, with a subdomain policy that is enforced too. How to do it safely.
  4. Add MTA-STS and TLS-RPT, so mail sent to you travels encrypted and you hear about it when it doesn't.
  5. Protect domains that don't send email at all. How.
  6. Keep evidence: your record history and DMARC results show a supervisor or customer that the measures work.

Check it, then keep it that way

A record that is right today can break tomorrow: a new tool gets connected, a DNS migration drops a line, a provider rotates its keys. Check your domain now, and let MailWatch check it every day, so you hear about problems before a receiver or an auditor does.

This checklist covers email only, in our own words. It is not legal advice and not a full list of what the rules ask.