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
- Publish SPF and turn on DKIM for every service that sends as your domain.
- Publish DMARC with
p=noneand read the reports until all your real mail passes. - Move to
p=reject, with a subdomain policy that is enforced too. How to do it safely. - Add MTA-STS and TLS-RPT, so mail sent to you travels encrypted and you hear about it when it doesn't.
- Protect domains that don't send email at all. How.
- 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.