Vulnerabilities / Threats
1/27/2012
08:09 PM
Connect Directly
LinkedIn
Twitter
Google+
RSS
E-Mail
50%
50%

Google, Microsoft Say DMARC Spec Stops Phishing

New email authentication framework called DMARC, backed by major email and security tool providers, aims to make spoofed domains in messages a thing of the past.

Leading free email providers AOL, Google, Microsoft, and Yahoo have banded together with financial, social media, and message security companies to make it easier to verify the authenticity of email messages.

Together, the companies on Monday announced the formation of DMARC.org, an organization that aspires to make email more trustworthy and phishing more difficult. DMARC.org will promote the DMARC specification, which describes how email senders should authenticate messages, how they should communicate their authentication practices, and how message recipients can discover and implement sender policies.

The acronym stands for domain-based message authentication, reporting, and conformance. Think of it as a set of rules that can make email more secure.

"It's a specification that the DMARC.org group has worked on over the last 18 months to produce," said Google product manager Adam Dawes in a phone interview. "It's a proposed mechanism by which senders and receivers can work together to fight phishing, and to lock down and prevent abuse of domains in the email channel."

[ Find out how the cloud can help security. Read Stolen iPhone Saved By iCloud. ]

Malicious email senders can easily make their messages appear to come from someone else's Internet domain, and such messages often are used for phishing--attempts to dupe message recipients into providing sensitive information under false pretenses or through malware.

According to the Anti-Phishing Working Group, there are presently about 20,000 to 25,000 unique phishing campaigns every month, each targeting hundreds of thousands to millions of email users. And thousands of fake phishing websites are set up every day.

Those involved in DMARC have a stake in making email a better experience. Dawes said that being duped by a phishing message often leads to compromises at multiple online services, because people tend to use the same password across different websites. Losing control of one's account, he said, "is one of the worst experiences that a user can have. If that happens because someone received a phishing message in his or her Gmail inbox, that's a terrible Google experience. Users rely on us to protect them against those threats."

In addition to AOL, Google, Microsoft, and Yahoo, other organizations participating in the DMARC group include financial companies Bank of America, Fidelity Investments, and PayPal; social media companies American Greetings, Facebook, and LinkedIn; and email security companies Agari, Cloudmark, eCert, Return Path, and Trusted Domain Project.

To fight phishing, various forms of email authentication are available, such as SPF, DKIM, and Sender ID. But there's no common standard. As a result, companies that authenticate their email have to coordinate with email providers to make sure that everyone is on the same page when it comes to which messages should be discarded for lack of authentication. PayPal began doing this with email providers in 2007, but approaching each email provider individually isn't ideal. DMARC isn't intended to replace existing specifications, but rather to tie them together.

"We view this as adding significant value to SPF and DKIM," said Microsoft engineer Paul Midgen.

The DMARC framework offers a way to formalize and automate message authentication processes and reporting so that security scales.

"What DMARC now allows is for any domain owner to have control over unauthenticated messages in the Gmail inbox," said Dawes. And the same holds true for inboxes operated by other email providers.

Agari, an email security provider, implemented DMARC last year and subsequently partnered with AOL, Google, Microsoft, and Yahoo. The company's Email Trust Fabric adds value to DMARC by turning raw DMARC data into actionable reports, to help companies understand their email infrastructure and message deliverability. Agari claims it has rejected approximately 4 billion threat messages since the technology was initially deployed in January 2011.

"For me, Monday is going to be one of the most auspicious days in the history of Internet security," said Agari founder and CEO Patrick Peterson in a phone interview in advance of DMARC's launch. "People will be able to send a message and recipients will be able to know where it came from."

Find out how to create and implement a security program that will defend against malicious and inadvertent internal incidents and satisfy government and industry mandates in our Compliance From The Inside Out report. (Free registration required.)

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Bprince
50%
50%
Bprince,
User Rank: Ninja
1/31/2012 | 12:49:01 AM
re: Google, Microsoft Say DMARC Spec Stops Phishing
This is a great step. The key will be the extent of adoption. There is still though the issue of people using similar domain names.
Brian Prince, InformationWeek/Dark Reading Comment Moderator
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Must Reads - September 25, 2014
Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-5485
Published: 2014-09-30
registerConfiglet.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via unspecified vectors, related to the admin interface.

CVE-2012-5486
Published: 2014-09-30
ZPublisher.HTTPRequest._scrubHeader in Zope 2 before 2.13.19, as used in Plone before 4.3 beta 1, allows remote attackers to inject arbitrary HTTP headers via a linefeed (LF) character.

CVE-2012-5487
Published: 2014-09-30
The sandbox whitelisting function (allowmodule.py) in Plone before 4.2.3 and 4.3 before beta 1 allows remote authenticated users with certain privileges to bypass the Python sandbox restriction and execute arbitrary Python code via vectors related to importing.

CVE-2012-5488
Published: 2014-09-30
python_scripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via a crafted URL, related to createObject.

CVE-2012-5489
Published: 2014-09-30
The App.Undo.UndoSupport.get_request_var_or_attr function in Zope before 2.12.21 and 3.13.x before 2.13.11, as used in Plone before 4.2.3 and 4.3 before beta 1, allows remote authenticated users to gain access to restricted attributes via unspecified vectors.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
In our next Dark Reading Radio broadcast, we’ll take a close look at some of the latest research and practices in application security.