This chapter has been written by a marketer whose been lucky enough to have worked at multiple cybersecurity companies. From these roles, I have learned from some of the best in the business how to effectively partner with your security team on any initiative. 

Given the introduction of Google and Yahoo’s bulk sender requirements, it seemed like the perfect opportunity to share what I’ve learned so your business is ready.

Before I worked in security, I always thought of it as the far away department that told me to stop using the software I liked.

I can confidently confirm that that is not true. 

I can promise that they are busy (security teams everywhere are facing major understaffing challenges), they have a bunch of priorities that are not related to your marketing efforts, and this is just one of the urgent asks they will receive this week. 

But, every security leader I have met is focused on doing what is best for the business. And if you can help your team understand this is a requirement for your business, and not just a nice to have, you will have an ally to help you achieve what you need.

The easiest way to see if you need any help from the security team is to use a tool to examine your current email security configuration and see if you meet the requirements. 

At Red Sift, we are biased towards Red Sift Investigate – the only free tool on the market that can see if your email-sending infrastructure meets the new requirements from Google and Yahoo. 

All you have to do is send a test email from your bulk sending tool (like Hubspot, Mailchimp, or Customer.io) to Red Sift Investigate. From there you will get results that you can share with your security team about what you need to do specific to Google and Yahoo compliance.

Your results will be shown with green check marks for things that are compliant and red x’s for things that will need to be addressed. 

If you are willing to get into the weeds a bit more, there are other tools. Check out chapter 4 for our tooling guide.

With your Red Sift Investigates results in hand, you are in the perfect position to get clear on what you need to do to authenticate your domain. 

If you are confused about the errors you are seeing – or just want to make it super clear for your security team – check out our matrix that gives you more details on why you might be seeing errors. 

From there you are well positioned to put forth an ask to your security team. 

For example, if your Red Sift Investigate results look like this:

And you see in the matrix that this means “A DMARC record is required.” 

You can go to your security team and show them both, and ask how you can work together to make sure you can get the proper record in place. 

📢Don’t forget – you need to test all of your email-sending services. Just because your Hubspot test email passes, doesn’t mean your Mailchimp email will.

Like I mentioned earlier, your security team has a long, long priority list. And this may not be at the top of the list right now. But, it’s important to communicate with your team why now is the time to start taking action. 

Some quick digging can help you build your case. 

Ask yourself questions like: 

• How did I use email to drive revenue last year? 
• How many of my net new opportunities or new customers had email as a last touch? 
• What would the cost of poor deliverability be for my business? 
• What percentage of my database would stop hearing from me if I didn’t meet these new requirements? 

If you can put your ask in the context of the business problems to be solved, your security team will have a clear idea of why it’s so critical to meet these requirements quickly.