12 ms·
You are assuming Sony really cared about MPAA's advise. My bet is that while Sony was forcing other vendors to follow draconian security measure, they themselv
by dba7dba 12y ago
You are assuming Sony really cared about MPAA's advise.
My bet is that while Sony was forcing other vendors to follow draconian security measure, they themselves had very lax security. Keeping SSN of 3000+ employees in a non-encrypted excel file?
That alone tells me Sony didn't have tight enough security, hence hack by outside (teenagers or N Korea) is more likely.
Things like this happen all the time, where a big company/org tells vendors to follow some rules while they themselves ignore them. All the time.
- KaiserPro 12y agoNaa, Sony couldn't give a shit about security, it was a cost that they thought wasn't worth bearing. Its the same as any other company. The problem is that a lot of the first release stuff came from HR. As we all know HR types rarely understand computers, let alone security. Even if they had a password repo that was super secure, it would be easier for them to share a spreadsheet, so they'll do that instead. For all we know, Sony could have had fairly tight security. From my understanding there were hefty ACLs to stop various sides of the business talking to each other. Yet these were still breached, for a long time and lots of data seeped across. The way the malware was written, and the actions of the hacker(s) leads me to suggest that this was an inside job. It is very had to sneak out large amounts of data, and fiddling with change control whilst not being detected is very difficult. Unless you know how to imitate the normal ebb and flow of work life. The problem SPE have now is that they'll have to throw away everything and start from scratch. All previous data will have to be quarantined, all infrastructure from the server, switches, printers to the workstations will have to be disposed of. Why? because there is no way of proving that there isn't any malware still embedded.