π Discover this awesome post from Hacker News π
π **Category**:
π **What Youβll Learn**:
I just received an email about a limited data breach, leaking customer information (no billing info though). Do you guys think Framework is handling this well? The email looked very detailed and transparent to me.
4 Likes
The transparency and especially the expediency of notification is greatly appreciated, Iβd say not only by the Framework team but also by Metabase. A 3 day turnaround by Metabase from initial discovery of the incident to notify business partners is impressive. And the Framework team took only 6 HOURS from receiving Metabaseβs notice before internally confirming and notifying their customers!! That is unheard of!! It seems like most companies wait months (at minimum) before notifying customers (if they do at all) because they think any security issue will cause the public to lose trust in them.
These days, itβs not a matter of when you suffer a security incident. Itβs how quickly and transparently you respond to it and notify your customers. In my opinion, the Framework team far exceeded expectations, and I anticipate any updates will be met with the same level of transparency. Other companies need to take note, this is how you handle a security incident.
2 Likes
Credit card info. Need assurance that was not accessed by the hackers.
Their privacy policy states Stripe is used for handling payments, and it was already stated in the email there was no payment information.
1 Like
Its disappointing another company has chosen to share our personal information with another third party. While at this point I think all of my information has probably already been leaked, I still do not appreciate my data being shared with third party providers. Getting all your personal information leaked because a company you have never heard of or interacted with is getting insanely normalised.
6 Likes
While I appreciate Frameworkβs notice and transparency (moreso than most orgs), I canβt say itβs not frustrating to be part of yet another data breach. Maybe we stop sharing so much data with 3rd parties??
5 Likes
I agree. Communication at this level is appreciated. The fact remains that Framework is benefiting from storing our data with a 3rd party for whatever vague analysis they decide to use it for and we bear the consequences of having certain data exposed when it shouldnβt be.
From Frameworkβs Notice:
What steps have you taken to ensure this doesnβt happen in the future?
We are evaluating the breadth and depth of data shared with business intelligence platforms, and scoping down their access to only the columns required for analysis.
Obviously this is moving in the right direction, but it may reveal that the depth of information previously shared with this platform was excessive to begin with.
1 Like
Appreciate the transparency, but I do not appreciate the wording of the messaging. Calling this a βlimitedβ breach right in the email subject is quite dishonest when basically all the personally identifiable information is there.
Also the email lists all the personally identifiable information and then it says βno other personally identifiable information has been takenβ. Yeah, thatβs all you had! This feels like a dark pattern of communication. You can do better, framework.
Also, does the business side have to have names, emails of the customers? Also, of course it sucks that only now youβre starting to ask these questionsβ¦
1 Like
I got the breach notification today. Earlier this week I got an βAction Requiredβ email asking me to update my payment method before my laptop would ship.
I always handle emails like these by ignoring the button and logging in directly at the relevant website (this time Framework). It worked out well, and the email was clearly legitimate.
But Iβd like to flag the pattern. A phishing email built off the breached data would look almost exactly like the one I received: same sender name, same layout, same urgency, same big button to update payment information.
I understand that Framework likely will not strip the link entirely, as it will make the friction of updating payment info too much for some users. But I would suggest that the email primarily asks the customer to log in through the web site and not through a link.
Most Nordic banks dropped payment links from customer emails years ago for this reason. As far as I know this has not been a problem. Given that Framework customers are now a known list of names and addresses, it seems worth revisiting.
Thanks for disclosing the breach quickly. That was handled very well. As I am now awaiting the delivery of my laptop, I will be even more vigilant than normal if I receive an email on import fees etc. that could be a targeted phishing attempt.
Frustrating that it happened. Appreciate being informed so quickly. Not sure about calling it a βlimitedβ data breach, though, considering what was accessed.
Not sure why I got an email about it, I havenβt made a purchase but I think I signed up for a waitlist.
I appreciate the response, definitely. In some juristictions (states in the US), itβs not required to disclose βminorβ breaches of public info, and many companies choose not to disclose it.
Iβve been around the block for a few decades and what gave me pause was that it was claimed to be a zero-day exploit, but was immediately patched when the hack was discovered. Those two things donβt usually go together and methinks someone dropped the ball on patching.
The way I sometimes interpret βlimitedβ is that they may have gotten all of my info, but perhaps not the entire database of every customer. My idea of βlimitedβ and Frameworkβs idea of βlimitedβ could be two entirely different things.
Iβve been online since the gopher and usenet days and maybe itβs just my weary bones talking, but I live my life with the assumption that regardless of all the precautions Iβve taken, every address, employment record, credit card, checking account, social security number (US), etc. Iβve ever had is out there already. Itβs just that no organized crime syndicate, nor just a two-bit street hustler, is gonna look at a Home Depot card with a $1000 limit and bother with it.
Maybe Framework is handling things well, but everyone who talked publicly about their recent orders should be considered at risk of targeted physical theft due to the current prices.
For this reason Iβd suggest that the βBatch Xβ topics for recent releases get deleted, but maybe some data gathering already happened there.
β‘ **Whatβs your take?**
Share your thoughts in the comments below!
#οΈβ£ **#Framework #Data #Breach #Discussion #General #Topics**
π **Posted on**: 1786085381
π **Want more?** Click here for more info! π
