Cookies help us display personalized product recommendations and ensure you have great shopping experience.

By using this site, you agree to the Privacy Policy and Terms of Use.
Accept
SmartData CollectiveSmartData Collective
  • Analytics
    AnalyticsShow More
    image fx (67)
    Improving LinkedIn Ad Strategies with Data Analytics
    9 Min Read
    big data and remote work
    Data Helps Speech-Language Pathologists Deliver Better Results
    6 Min Read
    data driven insights
    How Data-Driven Insights Are Addressing Gaps in Patient Communication and Equity
    8 Min Read
    pexels pavel danilyuk 8112119
    Data Analytics Is Revolutionizing Medical Credentialing
    8 Min Read
    data and seo
    Maximize SEO Success with Powerful Data Analytics Insights
    8 Min Read
  • Big Data
  • BI
  • Exclusive
  • IT
  • Marketing
  • Software
Search
© 2008-25 SmartData Collective. All Rights Reserved.
Reading: ESPC Sets Deadline to Require MD5 Hash Encryption
Share
Notification
Font ResizerAa
SmartData CollectiveSmartData Collective
Font ResizerAa
Search
  • About
  • Help
  • Privacy
Follow US
© 2008-23 SmartData Collective. All Rights Reserved.
SmartData Collective > Uncategorized > ESPC Sets Deadline to Require MD5 Hash Encryption
Uncategorized

ESPC Sets Deadline to Require MD5 Hash Encryption

CariBirkner
CariBirkner
3 Min Read
SHARE

As of September 1, 2009, MD5 hash suppression file encryption will be required for all ESPC members. Stolen suppression files and lingering cases of suppression list abuse have long plagued marketers, who are required by CAN-SPAM to share suppression lists with affiliates and these sometimes end up in the hands of third parties. In the past, these lists have been shared in plain text formats, which has allowed for future mailing and abuse.

MD5 is a one-way encryption tool that has long been used for password encryption to secure login info and protect against corrupted files. It is particularly useful for suppression list management because encrypted files cannot be transmitted back into original email addressess. However, because each address will have a dedicated line of hash, publishers and affiliates can still use the files for compliance when scrubbing send files against suppression lists.

Although MD5 is a needed improvement in the standard for protecting suppression files, it has become somewhat outdated and is vulnerable to decryption and hacking.  According to the ESPC Be…

More Read

New Book – The Data Governance Imperative
Synthesis
Is CRM the New Membership Management for NFPs?
Practical Change Management: The Top Ten Countdown – No. 9
My Interview with Ajay Ohri

As of September 1, 2009, MD5 hash suppression file encryption will be required for all ESPC members. Stolen suppression files and lingering cases of suppression list abuse have long plagued marketers, who are required by CAN-SPAM to share suppression lists with affiliates and these sometimes end up in the hands of third parties. In the past, these lists have been shared in plain text formats, which has allowed for future mailing and abuse.

MD5 is a one-way encryption tool that has long been used for password encryption to secure login info and protect against corrupted files. It is particularly useful for suppression list management because encrypted files cannot be transmitted back into original email addressess. However, because each address will have a dedicated line of hash, publishers and affiliates can still use the files for compliance when scrubbing send files against suppression lists.

Although MD5 is a needed improvement in the standard for protecting suppression files, it has become somewhat outdated and is vulnerable to decryption and hacking.  According to the ESPC Best Practice Guideline for ESPs,  newer hashing methods such as SHA-256 provide much greater levels of security and require far more time and resources to hack. A brute force attack is another way to gain information about hashed email addresses. This is where a person gathers a list of email addresses, hashes them, and compares them to the hash of an email list. The hacker would not gain new email addresses, but would be able to find out more info about the email addresses that match their list.

Additional precautions should be taken along with hashing, especially during data transfer in order to secure your lists. For example, storing a list on an FTP site that allows anonymous login could be insufficient security for data transfer (ESPC 2008).

Link to original post

TAGGED:email marketing
Share This Article
Facebook Pinterest LinkedIn
Share

Follow us on Facebook

Latest News

image fx (2)
Monitoring Data Without Turning into Big Brother
Big Data Exclusive
image fx (71)
The Power of AI for Personalization in Email
Artificial Intelligence Exclusive Marketing
image fx (67)
Improving LinkedIn Ad Strategies with Data Analytics
Analytics Big Data Exclusive Software
big data and remote work
Data Helps Speech-Language Pathologists Deliver Better Results
Analytics Big Data Exclusive

Stay Connected

1.2kFollowersLike
33.7kFollowersFollow
222FollowersPin

You Might also Like

eEvolution

4 Min Read

Facebook Blocks Spammers with Restraining Order

4 Min Read

Embracing Email Authentication a Must

3 Min Read
data analytics for better email marketing
Analytics

Email Marketers Use Data Analytics for Optimal Customer Segmentation

12 Min Read

SmartData Collective is one of the largest & trusted community covering technical content about Big Data, BI, Cloud, Analytics, Artificial Intelligence, IoT & more.

ai is improving the safety of cars
From Bolts to Bots: How AI Is Fortifying the Automotive Industry
Artificial Intelligence
AI chatbots
AI Chatbots Can Help Retailers Convert Live Broadcast Viewers into Sales!
Chatbots

Quick Link

  • About
  • Contact
  • Privacy
Follow US
© 2008-25 SmartData Collective. All Rights Reserved.
Go to mobile version
Welcome Back!

Sign in to your account

Username or Email Address
Password

Lost your password?