4 ms·
> But the whole thing is too ridiculous to be plausible. This is my take as well. State sponsored attacks, or at least the attacks that have allegedly been sta
by uxp 12y ago
> But the whole thing is too ridiculous to be plausible.
This is my take as well. State sponsored attacks, or at least the attacks that have allegedly been state sponsored up until now, have been quiet little things that go on for months or years so far under the radar that they only get revealed months afterwards by accident. They aren't filled with green-on-black text and pixelated skeleton images. Something just doesn't feel right about blaming North Korea for this. Maybe it came from the DPRK, but if so it had about as much to do with them as 9/11 did with the Saudis.
Does anyone also feel that the media is the only one that really linked the DPRK to this? I don't recall hearing about North Korea until after the "whodunnit" questions started coming out and speculation between the DPRK's denouncement months ago about The Interview and the very weak correlation between Chinese IPs being frequently involved in attacks and the DPRK's relationship with China, and the recycled malware that has some loose ties to Korea were thrown in a pot and mixed together. Once that started rolling, it seemed that the hackers started playing the Korean card, more for lulz than anything tangible. And now, long after the media has shifted from Poor Sony to Damned Korea (with even the President stepping in with his opinions), we're really heard very little from the attackers. It honestly feels like a bunch of guys in a basement collectively said to themselves "Oh shit, the President of the United States is talking about shit I did, time to cool off". From what I've read about the abysmal security at SPE, it wouldn't be surprising in the least that it didn't take a state sponsored group to do as much damage as they did. Blaming the DPRK only helps Sony sound less like a failure.
The only facts I can be sure of is that Sony did everything wrong in response. Every CIO should learn from this as what _not_ to do when hacked.