What PCI DSS asks
Requirement 5.4.1 of PCI DSS 4.0 (and 4.0.1) asks for processes and automated mechanisms that detect phishing attacks and protect your staff against them. It was a best practice until 31 March 2025 and has been mandatory since.
The standard doesn't order you to publish DMARC. Its guidance for 5.4.1 does name anti-spoofing controls such as SPF, DKIM and DMARC as examples, next to link scanning and malware filtering. In practice, an enforced DMARC policy is the usual way to show that nobody can send phishing mail in your name, and assessors ask about it.
Why p=none is not enough
With p=none receivers only report on mail that fails DMARC; they still deliver it. That is fine as a first step, but it doesn't
stop anyone from sending a fake invoice from your domain. Move to quarantine or, better, reject once all your real mail passes.
How to get there without blocking your own mail.
What to show your assessor
- Your published SPF, DKIM and DMARC records, and since when the DMARC policy has been enforced.
- That someone receives and reviews the DMARC reports, and acts on what they show.
- Your inbound mail filtering settings, and records of phishing awareness training (requirement 12.6.3.1).
MailWatch keeps the history of your DNS records and DMARC results, and turns it into an evidence PDF you can hand over.
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.