4 ms·
Thing about a data breach is once the data is out there - source code in this case - it’s out there for good and you have absolutely no control over who gets it
by mmaunder 3y ago
Thing about a data breach is once the data is out there - source code in this case - it’s out there for good and you have absolutely no control over who gets it. You can do as much post incident hardening as you want, and talk about it as much as you want, but the thing you’re trying to protect against, and blogging about how good you’re getting at preventing, has already happened. Can’t unscramble those eggs.
- arp242 3y agoThe source code next year is not the same as source code this year. The customer data next year is not the same as the customer data this year.
- burnished 3y agoWhats your point?
- mmaunder 3y agoThat this is messaged and received as a net win. It’s not.
- malwrar 3y agoAre they just supposed to be invincible? Next best thing is an incident response with this level of quality and transparency. Thats definitely a win in my book, I want to know the provider of a core part of my infra is able to competently and maturely respond to a security incident and this post strongly communicates that.
- BandButcher 3y agoagreed, to me this is a big deal for CF. especially coupled with confluence documentation which most likely includes future plans and designs, org charts, meeting minutes... you could also find other easter eggs in any legacy code, almost all companies have undocumented backdoors obviously a customer data breach would be worse but this is really no bueno