Security
DMARC: THE SECURITY VULNERABILITY AND REVENUE OPPORTUNITY
Angus Shaw, CTO of EMEA at Brigantia reveals why DMARC matters now.
I
t can be challenging to keep up with the changing landscape of cybersecurity, especially if you’re juggling numerous plates across your business.
Tis is where the distributor plays an important part. One of the most significant topics this year is
DMARC (Domain-based Message Authentication, Reporting & Conformance). If you haven’t started already, it’s time to look at this crucial security area for your customers. We’ve led in this area from the beginning, and I
want to share with you why it matters. DMARC is not only a security vulnerability you need to be aware of but also a revenue opportunity. Let’s get started by understanding DMARC a little more.
Understanding DMARC In short, DMARC is an email security protocol. Before diving into how it works technically, let’s consider why it’s become such a talking point. As of February 2024, Google and Yahoo began a crackdown on
spam. Tey announced plans to impose strict rules on bulk senders. Tese rules include a requirement to have a DMARC policy or risk going straight into spam folders. DMARC is also important for security. Unless the policy is
correctly managed, attackers can easily hijack your domain and impersonate your emails. Tis means they can use your email
24 | July/August 2024
domain in phishing attacks to make them more convincing and more likely to succeed – at the cost of your reputation.
How DMARC works A DMARC policy is a record stored in your DNS that enables recipient mail servers to verify emails from your domain. It combines two earlier protocols published in your
DNS: SPF (Sender Policy Framework) and DKIM (DomainKeys Identified Mail). Here’s how they work:
• SPF is a record of mail servers with permission to send from a domain. Receiving servers automatically check the IP address of the sending server against the SPF records.
• DKIM attaches an encryption signature to every genuine email. Tis prevents them from being intercepted in transit.
So, SPF ensures that emails originate from a legitimate source, while DKIM ensures they are not tampered with aſter sending. DMARC was invented to combine the two. It tells recipient mail servers what to do with emails that fail SPF and DKIM.
What a DMARC policy looks like A DMARC policy is a TXT record in your DNS. Tere are three possible policies: • p=none: if an email fails SPF and DKIM, this tells the recipient
www.pcr-online.biz
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52
