The Impact of the Salesloft Drift Breach on Cloudflare and Our Customers
Posted4 months agoActive4 months ago
blog.cloudflare.comTechstory
calmmixed
Debate
40/100
SecurityData BreachCloudflare
Key topics
Security
Data Breach
Cloudflare
Cloudflare discusses the impact of the Salesloft Drift breach on their customers and their response to it, with commenters raising concerns and questions about the breach and its aftermath.
Snapshot generated from the HN discussion
Discussion Activity
Moderate engagementFirst comment
3h
Peak period
6
4-6h
Avg / period
1.9
Comment distribution15 data points
Loading chart...
Based on 15 loaded comments
Key moments
- 01Story posted
Sep 2, 2025 at 1:33 PM EDT
4 months ago
Step 01 - 02First comment
Sep 2, 2025 at 4:39 PM EDT
3h after posting
Step 02 - 03Peak activity
6 comments in 4-6h
Hottest window of the conversation
Step 03 - 04Latest activity
Sep 3, 2025 at 3:46 PM EDT
4 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45106340Type: storyLast synced: 11/20/2025, 5:28:51 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
Have other free users also received this email?
check https://dash.cloudflare.com/?to=/:account/my-activities
I did find an email from Cloudflare in April 2011 (seven months after CF started to offer services) which was a response to a support request. I guess that things have changed in the intervening years so that the original link to keep track of my support request no longer works!!
I'll give them a break on this!
I actually do have a support case history with them, and I’d like to review what data has been lost. I’ve been a customer for over a decade. I have no clue what was in that history because I’ve filed numerous tickets over the years. They have made that impossible without paying them, even if you’ve paid them in the past.
They clearly failed to test their process on each account type.
I guess we could send individual data subject requests to their DPO, but that is probably more costly for them.
Important to remember that security practitioners and vendors are actually on the same team when it comes to criminal behavior, and maybe it’s better to treat others with grace.
1: https://blog.cloudflare.com/how-cloudflare-mitigated-yet-ano...
Does anyone have an action plan yet?
Given that Salesforce support case data contains the contents of support tickets with Cloudflare, any information that a customer may have shared with Cloudflare in our support system—including logs, tokens or passwords—should be considered compromised, and we strongly urge you to rotate any credentials that you may have shared with us through this channel.
Great response
> We are responsible for the choice of tools we use in support of our business. This breach has let our customers down. For that, we sincerely apologize. The rest of this blog gives a detailed timeline and detailed information on how we investigated this breach.
And a mea culpa for their 3rd party vendor choices (impressive)