Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Vulnerabilities / Threats

2/5/2013
06:23 PM
Connect Directly
LinkedIn
Twitter
RSS
E-Mail
50%
50%

Fake Email Dies Under DMARC Regime

Authentication and cooperation, made possible by the DMARC framework, cut down on email domain abuse.

A year ago, some of the world's largest email services began ordering the quarantine or deletion of messages sent in their names. The result of this mass execution is being hailed as a resounding success.

On Wednesday, DMARC, an industry group founded by leading technology, financial service, social and media companies in early 2012 to fight email fraud, announced that its message authentication technology now protects almost 2 billion of the world's 3.3 billion consumer inboxes and 80% of the consumer inboxes in the United States.

Some of the companies that have implemented DMARC's technology include Amazon, American Greetings, Apple, Bank of America, Blizzard Entertainment, Booking.com, eBay, Facebook, FedEx, Fidelity Investments, Google, Groupon, JP Morgan Chase, LinkedIn, LivingSocial, Microsoft, Netflix, PayPal, Tagged, Twitter, Western Union, Yelp, YouTube and Zynga.

[ Want new ideas on securing customer information? Read 6 Steps To Better Customer Data Protection. ]

DMARC stands for domain-based message authentication, reporting and conformance. Supported by email security providers Agari, Cloudmark, Return Path and Trusted Domain Project, it is a framework by which email senders can authenticate legitimate messages and can exchange information with receiving entities about how to handle unauthenticated messages -- monitor them, quarantine them or delete them.

In just the last two months of 2012, 325 million messages were rejected by mailbox providers for being unauthenticated. Such messages are often spam, phishing attacks or other forms of brand or domain spoofing -- in this case, 49 million of the rejected messages were from highly phished domains. Some of these messages may come from within an organization, via unsecured mail servers, while others may carry forged header information or come from confusingly similar domains.

"What brands are doing is shutting down these avenues of large-scale, orchestrated attacks," said Trent Adams, chair of DMARC.org and senior policy advisor at PayPal, in a phone interview. "The mailbox providers finally have a way to take definitive action on fraudulent mail."

Though based on authentication technologies, like SPF and DKIM, DMARC's value comes from combining message security with collaboration and business intelligence. Email senders that publish DMARC policies receive feedback reports from DMARC-compliant message recipients about unauthenticated messages purporting to come from any of the sending organization's domains.

These reports provide visibility into an organization's email stream and allow the organization to take enforcement action if necessary, explained Adams.

Such data matters to businesses because it's often a surprise. Reviewing a case study provided by Message Bus, Adams described how an unnamed, large, international conglomerate decided to test whether its domains were being spoofed. The company deployed a DMARC monitor record to gather information about unauthenticated email messages that people were receiving from its domains. It found that only 36% of messages that purported to come from the company actually originated from company servers. About 61% of the messages were from unknown and possibly malicious senders, while 3% was forwarded, through discussion lists or other mechanisms.

"That kind of business intelligence is a wakeup call to any organization," said Adams. "This is not an edge case. We hear this time and time again. Companies put out a monitor policy to see what the waters look like and they find they have a much larger problem."

Adams also cited the example of an unnamed, large, online auction company that saw a 32% decrease in phishing attempts and 62% less unauthorized account access following DMARC deployment. Coincidentally, eBay was an early DMARC adopter.

Krish Vitaldevara, principal group program manager for Microsoft's Outlook.com, said that the need for the security DMARC provides is reflected in how rapidly email senders and receivers are adopting the framework.

While 100% adoption and an end to domain spoofing may be too much to hope for, Adams likens DMARC to an inoculation campaign. If you can get a large enough percentage of the population inoculated, then everyone will be protected, he said.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
PJS880
50%
50%
PJS880,
User Rank: Ninja
2/15/2013 | 3:39:07 PM
re: Fake Email Dies Under DMARC Regime
That is an incredibly large user base and an extremely large percentage of the market as well. What is not shocking is the amount of spam, phishing, and just junk emails; I would have thought this number too much higher. Adams hit the nail on the head with this being a wake-up call, that the snooze button continues to get hit on, even with shattering results and information that companies are supplied with. It is nice that DMARC exists for companies to get specific statistics about their organization, as well better protect themselves.

Paul Sprague
InformationWeek Contributor
COVID-19: Latest Security News & Commentary
Dark Reading Staff 10/30/2020
'Act of War' Clause Could Nix Cyber Insurance Payouts
Robert Lemos, Contributing Writer,  10/29/2020
6 Ways Passwords Fail Basic Security Tests
Curtis Franklin Jr., Senior Editor at Dark Reading,  10/28/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How to Measure and Reduce Cybersecurity Risk in Your Organization
In this Tech Digest, we examine the difficult practice of measuring cyber-risk that has long been an elusive target for enterprises. Download it today!
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15703
PUBLISHED: 2020-10-31
There is no input validation on the Locale property in an apt transaction. An unprivileged user can supply a full path to a writable directory, which lets aptd read a file as root. Having a symlink in place results in an error message if the file exists, and no error otherwise. This way an unprivile...
CVE-2020-5991
PUBLISHED: 2020-10-30
NVIDIA CUDA Toolkit, all versions prior to 11.1.1, contains a vulnerability in the NVJPEG library in which an out-of-bounds read or write operation may lead to code execution, denial of service, or information disclosure.
CVE-2020-15273
PUBLISHED: 2020-10-30
baserCMS before version 4.4.1 is vulnerable to Cross-Site Scripting. The issue affects the following components: Edit feed settings, Edit widget area, Sub site new registration, New category registration. Arbitrary JavaScript may be executed by entering specific characters in the account that can ac...
CVE-2020-15276
PUBLISHED: 2020-10-30
baserCMS before version 4.4.1 is vulnerable to Cross-Site Scripting. Arbitrary JavaScript may be executed by entering a crafted nickname in blog comments. The issue affects the blog comment component. It is fixed in version 4.4.1.
CVE-2020-15277
PUBLISHED: 2020-10-30
baserCMS before version 4.4.1 is affected by Remote Code Execution (RCE). Code may be executed by logging in as a system administrator and uploading an executable script file such as a PHP file. The Edit template component is vulnerable. The issue is fixed in version 4.4.1.