2011 PlayStation Network outage

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
PlayStation Network logo.png

The 2011 PlayStation Network outage was the result of an "external intrusion" on Sony's PlayStation Network and Qriocity services, in which personal details from approximately 77 million accounts were compromised and prevented users of PlayStation 3 and PlayStation Portable consoles from accessing the service.[1][2][3][4] The attack occurred between April 17 and April 19, 2011,[1] forcing Sony to turn off the PlayStation Network on April 20. On May 4 Sony confirmed that personally identifiable information from each of the 77 million accounts had been exposed.[5] The outage lasted 23 days.[6]

At the time of the outage, with a count of 77 million registered PlayStation Network accounts,[7] it was one of the largest data security breaches in history.[8][9] It surpassed the 2007 TJX hack which affected 45 million customers.[10] Government officials in various countries voiced concern over the theft and Sony's one-week delay before warning its users.

Sony stated on April 26 that it was attempting to get online services running "within a week."[11] On May 14, Sony released PlayStation 3 firmware version 3.61 as a security patch. The firmware required users to change their password upon signing in. At the time the firmware was released, the network was still offline.[12] Regional restoration was announced by Kazuo Hirai in a video from Sony.[13] A map of regional restoration and the network within the United States was shared as the service was coming back online.[14]

Timeline of the outage

On April 20, 2011, Sony acknowledged that on the official PlayStation Blog that they were "aware certain functions of the PlayStation Network" were down. Upon attempting to sign in via the PlayStation 3, users received a message indicating that the network was "undergoing maintenance".[15][16] The following day, Sony asked its customers for patience while the cause of outage was investigated and stated that it may take "a full day or two" to get the service fully functional again.[17]

The company later announced an "external intrusion" had affected the PlayStation Network and Qriocity services.[18] This intrusion occurred between April 17 and April 19. On April 20, Sony suspended all PlayStation Network and Qriocity services worldwide.[19] Sony expressed their regrets for the downtime and called the task of repairing the system "time-consuming" but would lead to a stronger network infrastructure and additional security.[20] On April 25, Sony spokesman Patrick Seybold reiterated on the PlayStation Blog that fixing and enhancing the network was a "time intensive" process with no estimated time of completion.[21] However, the next day Sony stated that there was a "clear path to have PlayStation Network and Qriocity systems back online", with some services expected to be restored within a week. Furthermore, Sony acknowledged the "compromise of personal information as a result of an illegal intrusion on our systems."[22]

On May 1 Sony announced a "Welcome Back" program for customers affected by the outage. The company also confirmed that some PSN and Qriocity services would be available during the first week of May.[23][24] The list of services expected to become available included:[25]

<templatestyles src="Template:Blockquote/styles.css" />

  • Restoration of Online game-play across the PlayStation 3 (PS3) and PSP (PlayStation Portable) systems
  • This includes titles requiring online verification and downloaded games
  • Access to Music Unlimited powered by Qriocity for PS3/PSP for existing subscribers
  • Access to account management and password reset
  • Access to download un-expired Movie Rentals on PS3, PSP and MediaGo
  • PlayStation Home
  • Friends List
  • Chat Functionality

On May 2 Sony issued a press release, according to which the Sony Online Entertainment (SOE) services had been taken offline for maintenance due to potentially related activities during the initial criminal hack. Over 12,000 credit card numbers, albeit in encrypted form, from non-U.S. cardholders and additional information from 24.7 million SOE accounts may have been accessed.[26][27]

During the week, Sony sent a letter to the US House of Representatives, answering questions and concerns about the event.[28] In the letter Sony announced that they would be providing Identity Theft insurance policies in the amount of $1 million USD per user of the PlayStation Network and Qriocity services, despite no reports of credit card fraud being indicated. This was later confirmed on the PlayStation Blog, where it was announced that the service, AllClear ID Plus powered by Debix, would be available to users in the United States free for 12 months, and would include Internet surveillance, complete identity repair in the event of theft and a $1 million identity theft insurance policy for each user.[29][30]

On May 6 Sony stated they had begun "final stages of internal testing" for the PlayStation Network, which had been rebuilt.[31] However, the following day Sony reported that they would not be able to bring services back online within the one-week timeframe given on May 1, because "the extent of the attack on Sony Online Entertainment servers" had not been known at the time.[32] SOE confirmed on their Twitter account that their games would not be available until sometime after the weekend.[33]

Reuters began reporting the event as "the biggest Internet security break-in ever".[34] A Sony spokesperson said:[35]

  • Sony had removed the personal details of 2,500 people stolen by hackers and posted on a website
  • The data included names and some addresses, which were in a database created in 2001
  • No date had been fixed for the restart

On May 14 various services began coming back online on a country-by-country basis, starting with North America.[36] These services included: sign-in for PSN and Qriocity services (including password resetting), online game-play on PS3 and PSP, playback of rental video content, Music Unlimited service (PS3 and PC), access to third party services (such as Netflix, Hulu, Vudu and MLB.tv), friends list, chat functionality and PlayStation Home.[36] The actions came with a firmware update for the PS3, version 3.61.[37] As of May 15 service in Japan and East Asia had not yet been approved.[38]

On May 18 SOE shut down the password reset page on their site following the discovery of another exploit[39] that allowed users to reset other users' passwords, using the other user's email address and date of birth.[40] Sign-in using PSN details to various other Sony websites was also disabled, but console sign-ins were not affected.[39]

On May 23 Sony stated that the outage costs were $171 million.[41]

Sony response

US House of Representatives

Sony reported on May 4 to the PlayStation Blog[42] that:

<templatestyles src="Template:Blockquote/styles.css" />

Kazuo Hirai, Chairman of the Board of Directors of Sony Computer Entertainment America, submitted written answers to questions posed by the United States House subcommittee about the large-scale, criminal cyber-attack we have experienced.

Sony relayed via the letter that:

<templatestyles src="Template:Blockquote/styles.css" />

In summary, we told the subcommittee that in dealing with this cyber attack we followed four key principles:

  1. Act with care and caution.
  2. Provide relevant information to the public when it has been verified.
  3. Take responsibility for our obligations to our customers.
  4. Work with law enforcement authorities.


We also informed the subcommittee of the following:

  • Sony has been the victim of a very carefully planned, very professional, highly sophisticated criminal cyber attack.
  • We discovered that the intruders had planted a file on one of our Sony Online Entertainment servers named “Anonymous” with the words “We are Legion.”
  • By April 25, forensic teams were able to confirm the scope of the personal data they believed had been taken, and could not rule out whether credit card information had been accessed. On April 26, we notified customers of those facts.
  • As of today, the major credit card companies have not reported any fraudulent transactions that they believe are the direct result of this cyber attack.
  • Protecting individuals’ personal data is the highest priority and ensuring that the Internet can be made secure for commerce is also essential. Worldwide, countries and businesses will have to come together to ensure the safety of commerce over the Internet and find ways to combat cybercrime and cyber terrorism.
  • We are taking a number of steps to prevent future breaches, including enhanced levels of data protection and encryption; enhanced ability to detect software intrusions, unauthorized access and unusual activity patterns; additional firewalls; establishment of a new data center in an undisclosed location with increased security; and the naming of a new Chief Information Security Officer.

Explanation of delays

On April 26, 2011 Sony explained on the PlayStation Blog why it took so long to inform PSN users of the data theft:[43]

<templatestyles src="Template:Blockquote/styles.css" />

There’s a difference in timing between when we identified there was an intrusion and when we learned of consumers’ data being compromised. We learned there was an intrusion April 19th and subsequently shut the services down. We then brought in outside experts to help us learn how the intrusion occurred and to conduct an investigation to determine the nature and scope of the incident. It was necessary to conduct several days of forensic analysis, and it took our experts until yesterday to understand the scope of the breach. We then shared that information with our consumers and announced it publicly this afternoon.

Sony investigation

Possible data theft led Sony to provide an update in regards to a criminal investigation in a blog posted on April 27: "We are currently working with law enforcement on this matter as well as a recognized technology security firm to conduct a complete investigation. This malicious attack against our system and against our customers is a criminal act and we are proceeding aggressively to find those responsible."[44]

On May 3 Sony Computer Entertainment CEO Kazuo Hirai reiterated this and said the "external intrusion" which had caused them to shut down the PlayStation Network constituted a "criminal cyber attack".[45] Hirai expanded further, claiming that Sony systems had been under attack prior to the outage "for the past month and half", suggesting a concerted attempt to target Sony.[46]

On May 4 Sony announced that it was adding Data Forte to the investigation team of Guidance Software and Protiviti in analysing the attacks. Legal aspects of the case were handled by Baker & McKenzie.[47] Sony stated their belief that Anonymous, or some portion thereof, may have performed the attack.[48] Anonymous denied any involvement.[49]

Upon learning that a breach had occurred, Sony launched an internal investigation. Sony reported, in its letter to the United States Congress:

<templatestyles src="Template:Blockquote/styles.css" />

One of our first calls was to the FBI, and this is an active, on-going investigation.

Have you identified how the breach occurred?

Yes, we believe so. Sony Network Entertainment America is continuing its investigation into this criminal intrusion, and more detailed information could be discovered during this process. We are reluctant to make full details publicly available because the information is the subject of an on-going criminal investigation and also the information could be used to exploit vulnerabilities in systems other than Sony's that have similar architecture to the PlayStation Network.[50]

Inability to use PlayStation 3 content

While most games remained playable in their offline modes, the PlayStation 3 was unable to play certain Capcom titles in any form.[51] Streaming video providers throughout different regions such as Hulu, Vudu, Netflix and LoveFilm displayed the same maintenance message. Some users claimed to be able to use Netflix's streaming service[52] but others were unable.[53]

Criticism of Sony

Delayed warning of possible data theft

Original PlayStation 3 model

On April 26 nearly a week after the outage, Sony confirmed that it "cannot rule out the possibility"[54] that personally identifiable information such as PlayStation Network account username, password, home address, and email address had been compromised. Sony also mentioned the possibility that credit card data was taken—after claiming that encryption had been placed on the databases, which would partially satisfy PCI Compliance for storing credit card information on a server. Subsequent to the announcement on both the official blog and by e-mail, users were asked to safeguard credit card transactions by checking bank statements. This warning came nearly a week after the initial "external intrusion" and while the Network was turned off.[55]

Some disputed this explanation and queried that if Sony deemed the situation so severe that they had to turn off the network, Sony should have warned users of possible data theft sooner than on April 26.[56] Concerns have been raised over violations of PCI Compliance and the failure to immediately notify users. US Senator Richard Blumenthal wrote to Sony Computer Entertainment America CEO Jack Tretton questioning the delay.[57]

Sony replied in a letter to the subcommittee:

<templatestyles src="Template:Blockquote/styles.css" />

Your statement indicated you have no evidence at this time that credit card information was obtained, yet you cannot rule out this possibility. Please explain why you do not believe credit card information was obtained and why you cannot determine if the data was in fact taken. As stated above, Sony Network Entertainment America has not been able to conclude with certainty through the forensic analysis done to date that credit card information was not transferred from the PlayStation Network system. We know that for other personal information contained in the account database, the hacker made queries to the database, and the external forensics teams have seen large amounts of data transferred in response to those queries. Our forensics teams have not seen the queries and corresponding data transfers of the credit card information.

Unencrypted personal details

Credit card data was encrypted, but Sony admitted that other user information was not encrypted at the time of the intrusion.[44][58] The Daily Telegraph reported that "If the provider stores passwords unencrypted, then it's very easy for somebody else – not just an external attacker, but members of staff or contractors working on Sony's site – to get access and discover those passwords, potentially using them for nefarious means."[59] On May 2, Sony clarified the "unencrypted" status of users' passwords, stating that:[60]

<templatestyles src="Template:Blockquote/styles.css" />

While the passwords that were stored were not “encrypted,” they were transformed using a cryptographic hash function. There is a difference between these two types of security measures which is why we said the passwords had not been encrypted. But I want to be very clear that the passwords were not stored in our database in cleartext form.

British Information Commissioners Office

Following a formal investigation of Sony for breaches of the UK's Data Protection Act 1998, the Information Commissioners' Office issued a statement highly critical of the security Sony had in place:

<templatestyles src="Template:Blockquote/styles.css" />

If you are responsible for so many payment card details and log-in details then keeping that personal data secure has to be your priority. In this case that just didn't happen, and when the database was targeted – albeit in a determined criminal attack – the security measures in place were simply not good enough. There's no disguising that this is a business that should have known better. It is a company that trades on its technical expertise, and there's no doubt in my mind that they had access to both the technical knowledge and the resources to keep this information safe.[61]

Sony was fined £250,000 ($395k) for security measures so poor they did not comply with the British law.

Sony Online Entertainment outage

On May 3 Sony stated in a press release that there may be a correlation between the attack that had occurred on April 16 towards the PlayStation Network and one that compromised Sony Online Entertainment on May 2.[26] This portion of the attack resulted in the theft of information on 24.6 million Sony Online Entertainment account holders. The database contained 12,700 credit card numbers, particularly those of non-U.S. residents, and had not been in use since 2007 as much of the data applied to expired cards and deleted accounts. Sony updated this information the following day by stating that only 900 cards on the database were still valid.[62] The attack resulted in the suspension of SOE servers and Facebook games. SOE granted 30 days of free time, plus one day for each day the server was down, to users of Clone Wars Adventures, DC Universe Online, EverQuest, EverQuest II, EverQuest Online Adventures, Free Realms, Pirates of the Burning Sea, PlanetSide, Poxnora, Star Wars Galaxies and Vanguard: Saga of Heroes, as well as other forms of compensation for all other Sony Online games.

Security experts Eugene Lapidous of AnchorFree, Chester Wisniewski of Sophos Canada and Avner Levin of Ryerson University criticized Sony, questioning its methods of securing user data. Lapidous called the breach "difficult to excuse" and Wisniewski called it "an act of hubris or simply gross incompetence".[63][64][65][66]

Reaction

Compensation to users

Sony hosted special events after the PlayStation Network returned to service. Sony stated that they had plans for PS3 versions of DC Universe Online and Free Realms to help alleviate some of their losses.[67] In a press conference in Tokyo on May 1, Sony announced a "Welcome Back" program. As well as "selected PlayStation entertainment content" the program promised to include 30 days free membership of PlayStation Plus for all PSN members, while existing PlayStation Plus members received an additional 30 days on their subscription. Qriocity subscribers received 30 days. Sony promised other content and services over the coming weeks.[24] Sony offered one year free identity theft protection to all users with details forthcoming.

Hulu compensated PlayStation 3 users for the inability to use their service during the outage by offering one week of free service to Hulu Plus members.[68]

On May 16, 2011, Sony announced that two PlayStation 3 games and two PSP games would be offered for free from lists of five and four (respectively).[69][70] The games available varied by region[69][70] and were only available in countries which had access to the PlayStation Store prior to the outage.[70] On May 27, 2011, Sony announced the "welcome back" package for Japan[71] and the Asia region (Hong Kong, Singapore, Malaysia, Thailand and Indonesia).[72] In the Asia region, a theme - Dokodemo Issyo Spring Theme - was offered for free in addition to the games available in the "welcome back" package.[72]

^† 5 PSP games are offered in the Japanese market.[71]

PS3 games available by region
Game North America[69] Europe (non-Germany)[70] Germany[70] Asia[72] Japan[71]
Wipeout HD/Fury Yes Yes Yes Yes Yes
LittleBigPlanet Yes Yes Yes No No
InFamous Yes Yes No No No
Dead Nation Yes Yes No No No
Super Stardust HD Yes No Yes No No
Ratchet & Clank: Quest for Booty No Yes Yes No No
Hustle Kings No No Yes Yes Yes
The Last Guy No No No Yes Yes
Trashbox No No No Yes No
Come on, LocoRoco!! BuuBuu Cocoreccho No No No Yes Yes
Echochrome: Overture No No No No Yes
PSP games available by region
Game North America[69] Europe (non-Germany)[70] Germany[70] Asia[72] Japan[71]
LittleBigPlanet Yes Yes Yes Yes Yes
ModNation Racers Yes Yes Yes Yes No
Pursuit Force Yes Yes No No No
Killzone Liberation Yes Yes No No No
Everybody's Golf 2 No No Yes No No
Buzz Junior Jungle Party No No Yes No No
Everybody's Stress Buster No No No Yes Yes
Locoroco Midnight Carnival No No No Yes Yes
Patapon 2 No No No No Yes
What Did I Do to Deserve This, My Lord? No No No No Yes

^‡ Version of Killzone Liberation offered does not offer online gameplay functionality.[70]

Government reaction

The data theft concerned authorities around the world. Graham Cluley, senior technology consultant at Sophos, said the breach "certainly ranks as one of the biggest data losses ever to affect individuals".[73]

The British Information Commissioner's Office stated that Sony would be questioned,[74] and that an investigation would take place to discover whether Sony had taken adequate precautions to protect customer details.[75] Under the UK's Data Protection Act, Sony was fined £250,000 for the breach.[76]

Privacy Commissioner of Canada Jennifer Stoddart confirmed that the Canadian authorities would investigate. The Commissioner's office conveyed their concern as to why the authorities in Canada weren't informed of a security breach earlier.[77]

US Senator Richard Blumenthal of Connecticut demanded answers from Sony about the data breach[78] by emailing SECA CEO Jack Tretton arguing about the delay in informing its customers and insisting that Sony do more for its customers than just offer free credit reporting services. Blumenthal later called for an investigation by the US Department of Justice to find the person or persons responsible and to determine if Sony was liable for the way that it handled the situation.[79]

Congresswoman Mary Bono Mack and Congressman G. K. Butterfield sent a letter to Sony, demanding information on when the breach was discovered and how the crisis would be handled.[80]

Sony had been asked to testify before a congressional hearing on security and to answer questions about the breach of security on May 2, but sent a written response instead.

Legal action against Sony

A lawsuit was posted on April 27 by Kristopher Johns from Birmingham, Alabama on behalf of all PlayStation users alleging Sony "failed to encrypt data and establish adequate firewalls to handle a server intrusion contingency, failed to provide prompt and adequate warnings of security breaches, and unreasonably delayed in bringing the PSN service back online."[81][82] According to the complaint filed in the lawsuit, Sony failed to notify members of a possible security breach and storing members' credit card information,[83] a violation of PCI Compliance—the digital security standard for the Payment Card Industry.

A Canadian lawsuit against Sony USA, Sony Canada and Sony Japan claimed damages up to C$1 billion including free credit monitoring and identity theft insurance.[84] The plaintiff was quoted as saying, "If you can't trust a huge multi-national corporation like Sony to protect your private information, who can you trust? It appears to me that Sony focuses more on protecting its games than its PlayStation users".[85]

In October 2012 a Californian judge dismissed a lawsuit against Sony over the PSN security breach, ruling that Sony had not violated Californian consumer-protection laws, citing "there is no such thing as perfect security".[86]

In 2013 United Kingdom Information Commissioner's Office charged Sony with a £250,000 penalty for putting a large amount of personal and financial data of PSN clients at risk.[87]

Credit card fraud

As of May 2011, there were no verifiable reports of credit card fraud related to the outage. There were reports on the Internet that some PlayStation users experienced credit card fraud;[88][89][90] however, they were yet to be linked to the incident. Users who registered a credit card for use only with Sony also reported credit card fraud.[91] Sony said that the CSC codes requested by their services were not stored,[92] but hackers may have been able to decrypt or record credit card details while inside Sony's network.[88]

Sony stated in their letter to the subcommittee:

<templatestyles src="Template:Blockquote/styles.css" />

How many PlayStation Network account holders provided credit card information to Sony Computer Entertainment?

Globally, approximately 12.3 million account holders had credit card information on file on the PlayStation Network system. In the United States, approximately 5.6 million account holders had credit card information on file on the system. These numbers include active and expired credit cards.

As of today, the major credit card companies have not reported that they have seen any increase in the number of fraudulent credit card transactions as a result of the attack, and they have not reported to us any fraudulent transactions that they believe are a direct result of the intrusions described above.

On May 5, a letter from Sony Corporation of America CEO and President Sir Howard Stringer emphasized that there had been no evidence of credit card fraud and that a $1 million identity theft insurance policy would be available to PSN and Qriocity users:[30]

<templatestyles src="Template:Blockquote/styles.css" />

To date, there is no confirmed evidence any credit card or personal information has been misused, and we continue to monitor the situation closely. We are also moving ahead with plans to help protect our customers from identity theft around the world. A program for U.S. PlayStation Network and Qriocity customers that includes a $1 million identity theft insurance policy per user was launched earlier today and announcements for other regions will be coming soon.

Change to terms and conditions

It has been suggested that a change to the PSN terms and conditions announced on September 15, 2011, was motivated by the large damages being claimed by class action suits against Sony, in an effort to minimise the company's losses. The new agreement required users to agree to give up their right (to join together as a group in a class action) to sue Sony over any future security breach, without first trying to resolve legal issues with an arbitrator.[93][94] This included any ongoing class action suits initiated prior to the August 20, 2011.

Another clause, which removed a user's right to trial by jury should the user opt out of the clause (by sending a letter to Sony), says:

<templatestyles src="Template:Blockquote/styles.css" />

If the Class Action Waiver clause is found to be illegal or unenforceable, this entire Section 15 will be unenforceable, and the dispute will be decided by a court and you and the Sony Entity you have a dispute with each agree to waive in that instance, to the fullest extent allowed by law, any trial by jury.

Sony guaranteed that a court of law in the respective country, in this case the US, would hold jurisdiction in regards to any rules or changes in the Sony PSN ToS:[95]

<templatestyles src="Template:Blockquote/styles.css" />

These Terms of Service and all questions relating to the performance, interpretation, breach or enforcement of these Terms of Service, or the rights, obligations and liabilities of you and us under them are governed by the laws of the State of California. You agree that all disputes, claims or litigation arising from or related in any way to these Terms of Service and our relationship with you will be litigated only in a court of competent jurisdiction located in San Mateo County, State of California. You agree to be subject to personal jurisdiction and venue in that location.

References

  1. 1.0 1.1 Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. 24.0 24.1 Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. 26.0 26.1 Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. 30.0 30.1 Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. 36.0 36.1 Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. 39.0 39.1 Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. Lua error in package.lua at line 80: module 'strict' not found.
  43. Lua error in package.lua at line 80: module 'strict' not found.
  44. 44.0 44.1 Lua error in package.lua at line 80: module 'strict' not found.
  45. Lua error in package.lua at line 80: module 'strict' not found.
  46. Lua error in package.lua at line 80: module 'strict' not found.
  47. Lua error in package.lua at line 80: module 'strict' not found.
  48. Lua error in package.lua at line 80: module 'strict' not found.
  49. Lua error in package.lua at line 80: module 'strict' not found.
  50. Lua error in package.lua at line 80: module 'strict' not found.
  51. Lua error in package.lua at line 80: module 'strict' not found.
  52. Lua error in package.lua at line 80: module 'strict' not found.
  53. Lua error in package.lua at line 80: module 'strict' not found.
  54. Lua error in package.lua at line 80: module 'strict' not found.
  55. Lua error in package.lua at line 80: module 'strict' not found.
  56. Lua error in package.lua at line 80: module 'strict' not found.
  57. Lua error in package.lua at line 80: module 'strict' not found.
  58. Lua error in package.lua at line 80: module 'strict' not found.
  59. Lua error in package.lua at line 80: module 'strict' not found.
  60. Lua error in package.lua at line 80: module 'strict' not found.
  61. http://www.theregister.co.uk/2013/01/24/sony_psn_breach_fine/
  62. Lua error in package.lua at line 80: module 'strict' not found.
  63. Lua error in package.lua at line 80: module 'strict' not found.
  64. Lua error in package.lua at line 80: module 'strict' not found.
  65. Lua error in package.lua at line 80: module 'strict' not found.
  66. Lua error in package.lua at line 80: module 'strict' not found.
  67. Lua error in package.lua at line 80: module 'strict' not found.
  68. Lua error in package.lua at line 80: module 'strict' not found.
  69. 69.0 69.1 69.2 69.3 Lua error in package.lua at line 80: module 'strict' not found.
  70. 70.0 70.1 70.2 70.3 70.4 70.5 70.6 70.7 Lua error in package.lua at line 80: module 'strict' not found.
  71. 71.0 71.1 71.2 71.3 Lua error in package.lua at line 80: module 'strict' not found.
  72. 72.0 72.1 72.2 72.3 Lua error in package.lua at line 80: module 'strict' not found.
  73. Lua error in package.lua at line 80: module 'strict' not found.
  74. Lua error in package.lua at line 80: module 'strict' not found.
  75. Lua error in package.lua at line 80: module 'strict' not found.
  76. Lua error in package.lua at line 80: module 'strict' not found.
  77. Lua error in package.lua at line 80: module 'strict' not found.
  78. Lua error in package.lua at line 80: module 'strict' not found.
  79. Lua error in package.lua at line 80: module 'strict' not found.
  80. Lua error in package.lua at line 80: module 'strict' not found.
  81. Lua error in package.lua at line 80: module 'strict' not found.
  82. Lua error in package.lua at line 80: module 'strict' not found.
  83. Lua error in package.lua at line 80: module 'strict' not found.
  84. Lua error in package.lua at line 80: module 'strict' not found.
  85. Lua error in package.lua at line 80: module 'strict' not found.
  86. http://news.cnet.com/8301-1023_3-57538716-93/sony-psn-hacking-lawsuit-dismissed-by-judge/
  87. Sony Monetary Penalty Notice, ICO, 2013
  88. 88.0 88.1 Lua error in package.lua at line 80: module 'strict' not found.
  89. Lua error in package.lua at line 80: module 'strict' not found.
  90. Lua error in package.lua at line 80: module 'strict' not found.
  91. Lua error in package.lua at line 80: module 'strict' not found.
  92. Lua error in package.lua at line 80: module 'strict' not found.
  93. Lua error in package.lua at line 80: module 'strict' not found.
  94. Lua error in package.lua at line 80: module 'strict' not found.
  95. Lua error in package.lua at line 80: module 'strict' not found.

da:PlayStation Network#PlayStation Networks nedbrud 2011