08 Nov 2026 By CISO Consulting team 34 views 6 min read

DMARC Enforcement p=reject and NCA ECC: A Safe Path

Many organizations publish a DMARC record and never move past monitoring. This article explains SPF, DKIM and DMARC, why third-party senders cause the stall, and the staged path to p=reject.

A security administrator reviewing email authentication reports on a monitor in a quiet office.
In this article
  1. SPF, DKIM and DMARC in plain language
  2. Why most organizations stall at monitoring
  3. The staged path to p=reject
  4. 1. Establish the inventory
  5. 2. Classify each sender
  6. 3. Fix authentication for legitimate senders
  7. 4. Move to quarantine in steps
  8. 5. Move to reject
  9. 6. Keep it maintained
  10. What NCA ECC expects
  11. Why this matters for regulated organizations
  12. How we help
  13. Next step

Many organizations in the Kingdom have published a DMARC record and consider the matter closed. In practice, a record at p=none only reports on spoofing; it does not stop it. This article explains what DMARC enforcement means, how to reach p=reject without blocking legitimate mail, and how the subject relates to NCA ECC, the Essential Cybersecurity Controls issued by the National Cybersecurity Authority. The search phrase that brings most readers here is DMARC enforcement p=reject NCA ECC, and the short answer is that enforcement is a staged operating task, not a single setting.

SPF, DKIM and DMARC in plain language

Email was designed without a reliable way to prove who sent a message. Three records, published in your domain's DNS, close that gap.

  • SPF lists the servers and services that are allowed to send mail for your domain. A receiving server checks whether the sending system is on that list.
  • DKIM adds a cryptographic signature to each message. The receiver checks the signature against a public key in your DNS, which shows the message was authorized by the domain and was not altered in transit.
  • DMARC ties the two together. It tells receivers what to do when a message claiming to be from your domain fails SPF and DKIM in alignment with the visible From address, and it asks them to send you reports.

DMARC has three policies:

  1. p=none: monitor only. Failing mail is delivered as normal, and you receive reports.
  2. p=quarantine: failing mail is treated as suspicious, usually sent to spam.
  3. p=reject: failing mail is refused outright.

Only quarantine and reject protect your name. At p=none, an attacker can still send a convincing message that appears to come from your finance department or your chief executive.

Why most organizations stall at monitoring

The technical change from p=none to p=reject is one line in DNS. The reason it is rarely made is fear of breaking legitimate mail, and that fear is usually justified.

A modern organization sends email from far more places than its main mail platform. Typical examples include:

  • marketing and newsletter platforms
  • customer relationship management and ticketing systems
  • HR, payroll and recruitment tools
  • invoicing and payment notification services
  • survey, event and document-signing services
  • scanners, applications and monitoring systems that send alerts
  • subsidiaries and business units that manage their own domains

Each of these may send mail using your domain. If none of them has been mapped, and none has been configured with SPF inclusion or DKIM signing, their messages will fail DMARC. Moving to reject would then block invoices, password resets or customer notifications. So the policy stays at p=none, reports accumulate, and nobody has the time to read them.

The cause of the stall is therefore not the record. It is the missing inventory of who sends mail on the organization's behalf, and the missing owner to act on what the reports show.

The staged path to p=reject

A safe route treats the reports as evidence and moves in steps.

1. Establish the inventory

Start with the domains you own, including those that never send mail. Identify the current gateway and the mail flow. Then read the aggregate DMARC reports to list every source sending as your domain. Reports show which sources pass, which fail and how much mail each sends.

2. Classify each sender

For every source, decide whether it is legitimate and who owns it. Legitimate senders are brought into compliance; unknown or unauthorized ones are investigated. This step is where business owners must be involved, because only they know why a particular service exists.

3. Fix authentication for legitimate senders

Add or correct SPF entries and enable DKIM signing for each approved service, using aligned domains or subdomains. Watch for the SPF limit on DNS lookups, which large sender lists often exceed, and for third parties that cannot sign with your domain and need a dedicated subdomain instead.

4. Move to quarantine in steps

Raise the policy to quarantine, ideally applying it to a small share of mail first and increasing gradually. Keep reading reports. Any legitimate source that was missed will appear as failures, and can be corrected before the impact grows.

5. Move to reject

When failures from legitimate sources have been resolved and remaining failures are clearly unauthorized, set p=reject. Apply the same discipline to subdomains and to parked domains, which can be set to reject immediately because they should send nothing.

6. Keep it maintained

This is the step most often forgotten. New tools are adopted, vendors change sending infrastructure, DKIM keys need rotation and acquisitions add domains. A policy at reject that is not monitored will eventually block something legitimate, and the usual response is to weaken the policy. Enforcement holds only if someone owns the change process and reviews the reports regularly.

What NCA ECC expects

NCA ECC sets expectations for protecting email as part of an organization's cybersecurity controls, including protecting email services from threats such as phishing and spoofing and applying email authentication. We will not cite a specific control number here; the exact wording and applicability should be checked against the current published framework and your organization's scope. The practical reading is that a DMARC record left permanently at monitoring is hard to present as a mature control, while an enforced policy, with evidence of how it is maintained, is much easier to defend.

For regulated institutions, the same logic applies under sector frameworks such as the SAMA Cyber Security Framework. Assessors tend to look for more than a published record. They look for ownership, a defined process, reporting and proof that the control continues to operate.

Why this matters for regulated organizations

A spoofed message in the name of a bank, insurer or government-linked entity is more than a nuisance. It exposes customers to fraud, damages trust and creates an incident that compliance and fraud teams must then investigate. Enforcement removes the easiest form of impersonation, which is the exact-domain spoof. It does not address look-alike domains or compromised mailboxes, so it belongs alongside filtering, user reporting and awareness rather than in place of them.

How we help

Our Managed Email Security and Anti-Phishing service covers the operation of email protection, authentication records and phishing response. It includes filtering policy, DMARC rollout, user-reported mail triage and incident handling.

The work follows four steps: assess the current gateway, domains and mail flow; tighten policy and authentication to enforcement; respond by triaging and removing reported mail; and report on trends and user risk each month. SPF, DKIM and DMARC rollout to enforcement is one of the named features of the service, and a DMARC progress report is one of the deliverables, alongside an email security baseline, a monthly phishing and blocked-threat report and incident write-ups.

The service runs on 12-month terms and is managed on an ongoing basis, which matches the nature of the task. Supported email platforms include common cloud and on-premises platforms, and the supported list is confirmed during scoping. Reported-mail data can also feed an awareness program, so the two can be paired.

Next step

If your DMARC record has been at p=none for longer than you would like, the first useful step is an inventory of senders and a baseline of your current mail flow. Our Managed Email Security and Anti-Phishing service starts there and carries the work through to enforcement and its ongoing upkeep. Contact us to discuss your domains and scope.

Tags: DMARC Email Security NCA ECC SPF DKIM Anti-Phishing
Readiness self-check

How ready are you? Find out in two minutes

Answer a few questions for your framework. You get a score, your biggest gaps and — if you want it — a detailed assessment from our team.

Ready to talk about your compliance?

Tell us where you stand. We will show you the shortest path to what your regulator expects.

Regulatory updates in your inbox

SAMA, NCA and SDAIA changes and what they mean for your institution — once a month.

E-mails in

We confirm by e-mail; unsubscribe any time. Manage your subscription · Past issues

Schedule a Free Assessment