Disqus Demonstrates How to Do Breach Disclosure Right

Presently sponsored by: Matchlight by Terbium Labs: Know when your exact data appears on the dark web. Contact us for a demo today.

We all jumped on “the Equifax dumpster fire bandwagon” recently and pointed to all the things that went fundamentally wrong with their disclosure process. But it’s equally important that we acknowledge exemplary handling of data breaches when they occur because that’s behaviour that should be encouraged.

Last week, someone reached out and shared a number of data breaches with me. Breaches I’d never seen before. Some of them were known by the companies who’d previously made public disclosures; ReverbNation, Bitly and Kickstarter. One of them, however, showed no previous evidence of disclosure – Disqus.

I first saw the Disqus data first thing Friday morning my time in Australia. Verification wasn’t difficult because my own record was in there (there’s nothing like finding your own data in a breach to help expedite verification!) I reached out to an existing contact I had at Disqus via email as soon as I had a reasonable degree of confidence that the data was accurate (a couple of hours after I received it). From that moment, the timeline in their public disclosure began which I highlighted in this tweet:

Think about everything that had to happen within this time frame:

  1. I had to get a response and establish communication
  2. I had to get the data to them securely (over Australian internet speeds…)
  3. They had to download and review the data
  4. They had to establish the legitimacy of the data
  5. They had to ensure there was no ongoing risk in their system
  6. They had to invalidate passwords that had been exposed
  7. They had to contact the impacted users in the previous point
  8. They had to prepare the communication in the aforementioned disclosure

On top of all that, the CEO made himself available to personally answer questions from the press. Less than a day earlier, they had absolutely no idea what was coming yet they managed to pull all this together in record time. Consequently – and this is what I really want to highlight here – people responded amazingly well to the incident:

There were many more responses with a consistent theme across them. This was a dark moment for Disqus and there’s no sugar-coating the fact that somehow, somewhere, someone on their end screwed up and they lost control of customer data. But look at the public sentiment after their disclosure; because of the way Disqus handled the situation, it’s resoundingly positive. Compare that to Equifax and the comments I made about their handling of the breach only one month ago:

Here’s the lesson for everyone else who is yet to disclose all the breaches that are still to come: after an incident like this, everyone wants to pile blame on the company involved. They’ll look for any little excuse to vent their anger because they’re quite rightly upset about the whole thing.

Following the Red Cross Blood Service data breach down here almost a year ago, I later wrote about Data Breach Disclosure 101: How to Succeed After You’ve Failed. In there, I highlighted many of the things the Red Cross had done well and indeed many of the things that other organisations had done poorly. When I look at how Disqus handled their incident, they ticked so many of the boxes:

  1. It was easy to report to them (admittedly, my having an existing contact there inevitably made it easier than if I was coming out of the blue)
  2. They applied urgency, more than I can honestly say I’ve seen any company do before under similar circumstances
  3. They disclosed early, earlier than anyone could have reasonably expected (I normally consider 72 hours the “Gold Standard”)
  4. They protected impacted accounts very quickly by resetting the passwords of accounts that had them disclosed
  5. They were entirely transparent; there was never a moment where I thought they were attempting to spin this in their favour at the expense of the truth
  6. They provided details – the passwords were salted SHA1 hashes which is not a pretty story to tell in this day and age, but they told it truthfully regardless
  7. They apologised (it was one of the first things they said); they owned this incident from the outside and didn’t attempt to divert blame elsewhere

I still have multiple other data breaches from the same set that Disqus came in and totalling tens of millions of records. I’m quite sure the companies involved don’t know they were breached and nor do their customers. I’m presently working on the disclosure of these and frankly, I dread the process because it rarely ever goes as smoothly as the one above. But I’ll go through it anyway because it needs to be done; in one of these incidents alone, I have over 31k Have I been pwned subscribers and this is precisely the sort of thing they want to know about. Stay tuned.

Leave a Reply

Your email address will not be published.