8 votes

The true cost of a hack: The Rackspace Special

4 comments

  1. [2]
    g33kphr33k
    (edited )
    Link
    Most of us will remember that joy of finding out just how bad Rackspace was hit not all that long ago. Part of the business we had bought had refused to merge some of their mailboxes across to...

    Most of us will remember that joy of finding out just how bad Rackspace was hit not all that long ago. Part of the business we had bought had refused to merge some of their mailboxes across to M364 when this happened and I had the biggest hidden grin going when the news was released.

    A year on, this article gives some in-depth impact analysis. Rackspaces' legal bill is eye-watering and the class actions are not even finished being built against them yet. I don't know how they're going to survive this unless their insurance is rock solid.

    Root cause that allowed all to happen, a missing patch, that's all it takes in this modern age.

    6 votes
  2. [2]
    mantrid
    Link
    If the vulnerability had been patched by Microsoft a month before the attack, how is that a "zero-day exploit?"

    If the vulnerability had been patched by Microsoft a month before the attack, how is that a "zero-day exploit?"

    1 vote
    1. g33kphr33k
      Link Parent
      I do love content writers. Was probably a zero day on the day it was written and used, then MS patched it. Natural progression means it's no longer a zero day, but some people do not understand that.

      I do love content writers. Was probably a zero day on the day it was written and used, then MS patched it.

      Natural progression means it's no longer a zero day, but some people do not understand that.

      1 vote