3 ms·
The January 2016 thing was them finally acknowledging the attack that had happened many months prior, after WPEngine gave Linode the opportunity to announce the
by TheSwordsman 5y ago
The January 2016 thing was them finally acknowledging the attack that had happened many months prior, after WPEngine gave Linode the opportunity to announce they were hacked after they were also compromised using the same vector that hit PagerDuty. If Linode had declined, WPEngine was going to do it on their behalf. I couldn't convince the powers that be to make the same demand months prior, even though I was confident, so if WPEngine hadn't pushed the issue I don't know that Linode would have ever disclosed.
But that doesn't matter anymore. This was nearly a generation ago in tech companies, and they are now part of a bigger one.
- tempnow987 5y agoYeah, this key issue. https://wptavern.com/wp-engine-identifies-cloud-infrastructure-providers-as-entry-point-for-recent-security-breach https://wptavern.com/wp-engine-identifies-cloud-infrastructu... How do you sit on breaches like this for months and cause all this downline pain to your customers is crazy.