VB2014 paper: DMARC - how to use it to improve your email reputation

Posted by   Virus Bulletin on   Nov 6, 2014

Terry Zink presents case study in which he describes setting a DMARC policy for Microsoft.

Over the next few months, we will be sharing VB2014 conference papers as well as video recordings of the presentations. Today, we have added 'DMARC - how to use it to improve your email reputation', by Microsoft's Terry Zink.

Email is a 30-year-old protocol, designed at a time when the Internet was much smaller and you could basically trust anyone. As a consequence, spammers and phishers can easily send email claiming to be someone else.

DMARC, which builds on both SPF and DKIM, attempts to solve that problem, at least partially, by giving senders a way to inform receivers which emails that claim to come from them really did come from them.

Paypal email

In his VB2014 Paper, Terry explains how DMARC works and how it helps to prevent phishers abusing domains that use the standard.

However, he also explains that DMARC is no silver bullet: if PayPal doesn't control the domain 'paypai.com', it can't stop phishers from using it. Moreover, as I wrote when Yahoo! and later AOL felt forced to set a strict DMARC policy, doing so can cause collateral damage.

Perhaps most interesting is the case study Terry presents in setting a DMARC record for Microsoft. The large company has many different business units that each send email, making setting a single DMARC record a far from trivial task. However, DMARC provides a mechanism whereby feedback from receivers can be used to detect incorrect or incomplete records, which in the end helped Terry set a fairly strict DMARC policy for the company.

Using DMARC to detect a misconfiguration

You can read Terry's paper here in HTML-format, or download it here as a PDF (no registration or subscription required). You can download the presentation slides here. We have also uploaded the presentation to our YouTube channel.

For another introduction into DMARC, you can read the VB article John Levine wrote in March 2012, shortly after the standard was launched.



Posted on 06 November 2014 by Martijn Grooten
twitter.png
fb.png
linkedin.png
hackernews.png
reddit.png

 

Latest posts:

VB2018 paper: From Hacking Team to hacked team to…?

Today we publish the VB2018 paper and video by ESET researcher Filip Kafka, who looked at the new malware by Hacking Team, after the company had recovered from the 2015 breach.

The spam that is hardest to block is often the most damaging

We see a lot of spam in the VBSpam test lab, and we also see how well such emails are being blocked by email security products. Worryingly, it is often the emails with a malicious attachment or a phishing link that are most likely to be missed.

Throwback Thursday: We're all doomed

Mydoom turns 15 this month, and is still being seen in email attachments. This Throwback Thursday we look back to March 2004, when Gabor Szappanos tracked the rise of W32/Mydoom.

VB2019 call for papers - now open!

Have you analysed a new online threat? Do you know a new way to defend against such threats? Are you tasked with securing systems and fending off attacks? The call for papers for VB2019 is now open and we want to hear from you!

VB2018 paper: Unpacking the packed unpacker: reversing an Android anti-analysis library

Today, we publish a VB2018 paper by Google researcher Maddie Stone in which she looks at one of the most interesting anti-analysis native libraries in the Android ecosystem. We also release the recording of Maddie's presentation.

We have placed cookies on your device in order to improve the functionality of this site, as outlined in our cookies policy. However, you may delete and block all cookies from this site and your use of the site will be unaffected. By continuing to browse this site, you are agreeing to Virus Bulletin's use of data as outlined in our privacy policy.