Perimeter
Guest Blog // Selected Security Content Provided By Sophos
What's This?
5/16/2011
08:49 PM
Dark Reading
Dark Reading
Security Insights
Connect Directly
RSS
E-Mail
50%
50%

Lessons Learned From Sony

Harsh lessons Sony was taught, and recommendations on how to keep your company out of the headlines

It has been one month since Sony noticed something was wrong on its PlayStation Network service. Have we learned from the mistakes that led to such an enormous amount of lost data, goodwill, and money? Are we doomed to continue repeating Sony's mistakes?

Let's step back, take a look at the situation as it has played out, and determine what lessons we should take away from this incident.

First, criminals broke into Sony's PlayStation Network systems and went snooping around for data. Unfortunately, the information the criminals were able to access contained people's names, addresses, email addresses, passwords, birth dates, and encrypted credit card numbers. Sony investigated to determine the extent of the breach; a week later, it shut down the network and notified the public.

One week later, Sony announced round two of the compromise, affecting Sony Online Entertainment. This time another production database was dumped, as well as a decommissioned database from 2007 that contained unencrypted credit, debit, and direct debit information.

It didn't stop there. Sony then reported an "attack" in which it claimed a list of sweepstakes winners from 2001 had their names and postal codes stolen. It turned out that no one had to break in to access the data: An insecure Web server contained a world-readable Excel spreadsheet with contestants' PII.

The first lesson for us has to do with messaging, which has not been Sony's strong point. Where people's identities and personal information are concerned, notify them immediately with full details. Sony only waited about a week in the PlayStation incident, but at that point still did not release enough information to assure their customers that their credit cards were safe or to clarify whether their passwords were stored insecurely. The second breach was actually part of the same attack as the first one, but this was also not clearly stated. As it stands, the details of the attacks are still not particularly clear or trustworthy.

Second, we need to track the locations where we store sensitive data, not just to ensure it is encrypted, but to know all of the diverse places we could be storing that data.

We asset-tag our laptops, monitors, and other equipment to know where our physical items are located. It is high time we started tracking where data is located as well. More often than not, data is far more valuable than the "asset" it is stored on.

Third, auditing your public-facing websites for accidental disclosure is good practice. Using version-control tools to ensure the data that is available matches the data you intended to publish can go a long way toward preventing this type of accidental disclosure.

Worst case, some clever Google searches of your Web assets can be an enlightening experience. If you don't do it, then someone else will -- and you might not like the results.

Chester Wisniewski is a senior security adviser at Sophos Canada.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Must Reads - September 25, 2014
Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
Flash Poll
Title Partner’s Role in Perimeter Security
Title Partner’s Role in Perimeter Security
Considering how prevalent third-party attacks are, we need to ask hard questions about how partners and suppliers are safeguarding systems and data.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2003-1598
Published: 2014-10-01
SQL injection vulnerability in log.header.php in WordPress 0.7 and earlier allows remote attackers to execute arbitrary SQL commands via the posts variable.

CVE-2011-4624
Published: 2014-10-01
Cross-site scripting (XSS) vulnerability in facebook.php in the GRAND FlAGallery plugin (flash-album-gallery) before 1.57 for WordPress allows remote attackers to inject arbitrary web script or HTML via the i parameter.

CVE-2012-0811
Published: 2014-10-01
Multiple SQL injection vulnerabilities in Postfix Admin (aka postfixadmin) before 2.3.5 allow remote authenticated users to execute arbitrary SQL commands via (1) the pw parameter to the pacrypt function, when mysql_encrypt is configured, or (2) unspecified vectors that are used in backup files gene...

CVE-2014-2640
Published: 2014-10-01
Cross-site scripting (XSS) vulnerability in HP System Management Homepage (SMH) before 7.4 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.

CVE-2014-2641
Published: 2014-10-01
Cross-site request forgery (CSRF) vulnerability in HP System Management Homepage (SMH) before 7.4 allows remote authenticated users to hijack the authentication of unspecified victims via unknown vectors.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Chris Hadnagy, who hosts the annual Social Engineering Capture the Flag Contest at DEF CON, will discuss the latest trends attackers are using.