Join our Newsletter — 33% off our NHI Course

Could DMARC p=reject close the FTSE 250 spoofing gap?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20210
Topic starter  

TL;DR: 98 FTSE 250 companies still have not reached DMARC enforcement at p=reject, leaving spoofed email possible across 39.2% of the index, according to Red Sift. DMARC governance now depends on clean sender inventory, alignment, and ownership, not just the presence of a record.

Editorial analysis by NHI Mgmt Group, based on content published by Red Sift: “FTSE 250 DMARC report: 39% of the UK's top companies still don't block spoofed email”.

By the numbers:

  • 152 of 250 FTSE 250 organisations (60.8%) have reached DMARC enforcement at p=reject
  • 47 organisations (18.8%) run p=none policies that monitor traffic but take no action against spoofed email
  • 33 organisations (13.2%) sit at p=quarantine, sending suspicious messages to spam rather than blocking them outright

Key questions

Q: Why do partial DMARC deployments still leave phishing risk?

A: Partial deployment leaves a trust gap because receivers may still deliver unauthenticated mail, especially when policies stop at none or quarantine.

Q: What do security teams get wrong about SPF, DKIM, and DMARC?

A: They often deploy them as isolated email settings instead of treating them as enforcement controls for domain identity.

Q: What breaks when DMARC is not enforced for brand email?

A: Without DMARC enforcement, mailbox providers can still deliver or partially trust spoofed mail that appears to come from your domain.

Practitioner guidance

  • Audit every mail source that uses your domain Use DMARC aggregate reports to inventory marketing, payroll, HR, CRM, support, and third-party services sending on your behalf.
  • Move from visibility to enforcement in stages Tighten alignment, fix authentication failures, then move from p=none to p=quarantine and finally p=reject.
  • Treat unowned senders as an identity governance problem Any system that can send email as your brand is effectively operating under your domain identity.

Bottom line: DMARC reduces spoofing only when policy moves from monitoring to enforcement across every authorised sender.

Glossary terms: DMARC, p=reject, p=quarantine, p=none

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 2 weeks ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20698
 

DMARC enforcement is the real control boundary, not DMARC publication. Publishing a record without moving to p=reject creates an observability layer, not a protective one. That distinction matters because attackers care about delivery, not policy intent. For practitioners, the governance question is whether email authentication has actually become enforceable across every sender, not whether the domain has started the project.

A question worth separating out:

Q: How do security teams know whether DMARC enforcement is actually working?

A: Look for fewer authentication failures from legitimate senders, stable alignment for critical mail flows, and reporting that clearly shows why a message passed or failed. If failures cannot be explained quickly, the programme is not ready for stricter enforcement. Working DMARC is visible, reproducible, and backed by clean sender inventory.

👉 Read our full editorial: FTSE 250 DMARC enforcement still leaves a spoofing gap


This post was modified 2 weeks ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.