Expert: Sony Negligent In PSN Security

An expert has given testimony to the US House of Representatives Subcomittee on Commerce, Manufacturing, and Trade during its commencement on hearings on the “unauthorized intrusion” on Sony’s PlayStation Network and Qrocity service, stating Sony knew that their security software was dated and lacked any sort of firewall against hacking.

Cybersecurity expert Dr. Gene Spafford’s testimony stated that security experts discovered discussions on forums that talked about how the PSN’s security was lacking. The threads revealed that the network was using old versions of the Apache Web server software, which “was unpatched and had no firewall installed.”

Worse, two to three months before the attack, the vulnerability was reported “in an open forum monitored by Sony employees,” but the company took no action to rectify the situation. If the testimony is accurate, Sony could be slapped with a serious criminal negligence charge.

The Sony intrusion alone compromised 100 million accounts both on the PSN and its Qriocity service, according to Spafford. He also cited the total cost of the breach to Sony, credit card companies, and other outfits, at $21 billion. Thieves in credit-card theft forums actually complained that the PSN breach was so great that it was depressing the price of such information by a “factor of five or 10” on the black market.

Spafford didn’t reserve his accusations for Sony, either. He stated that law enforcement is ill-equipped to handle cyberterrorism and cyberthieft. Additionally, most companies are not equipped with enough security measures because “investing in security measures affects the bottom line. They don’t understand the risks involved by not investing in security. … So when they are hit, they pass that cost along to their customers, and to the rest of society.” In other words, a classic case of being penny wise and pound foolish.

Spafford’s proposed solution to future security is to limit the amount of data kept by companies such as Sony and to “age the data” so it expires after a certain time.

C-Span posted the video of the testimony here.

(Thanks, GameSpot.)

0 thoughts on “Expert: Sony Negligent In PSN Security”

  1. One of the better pieces on the PSN fiasco that I’ve read, congrats Jonah!

    I had two jobs as a programmer; in both cases, interacting with the IT department felt more like interacting with Dilbert’s “Information prevention department”, ran by Catbert. They even wanted (and succeeded in one place) to push a “Service Level Agreement”: it’ll take two days to create a new password for this, seven days to do that etc.
    They just don’t put enough heart in it.

    To be fair, my very first job though was … in the IT department of my college! IT work is hard. If you screw up (and we did screw up sometimes), you could kiss your weekend goodbye . Usually, we’d investigate the issue that very evening, then tried to implement it either during the next day, or, at worst, if the computers we’d want to alter were being in use, in the weekend.
    The lessons I learned there is that: (1) you must react quickly and (2) if you put a bit of your heart into your work, you can get surprisingly good results.

    Nice find on the “depressing the price of such information by a “factor of five or 10? on the black market”. I guess the PSN issue is the equivalent of flooding the market with products 🙂

    @” limit the amount of data kept by companies such as Sony and to “age the data””
    This is security basics. If you don’t want to be responsible for safekeeping secret information, then don’t store secret information on your servers. Period.

  2. One of the better pieces on the PSN fiasco that I’ve read, congrats Jonah!

    I had two jobs as a programmer; in both cases, interacting with the IT department felt more like interacting with Dilbert’s “Information prevention department”, ran by Catbert. They even wanted (and succeeded in one place) to push a “Service Level Agreement”: it’ll take two days to create a new password for this, seven days to do that etc.
    They just don’t put enough heart in it.

    To be fair, my very first job though was … in the IT department of my college! IT work is hard. If you screw up (and we did screw up sometimes), you could kiss your weekend goodbye . Usually, we’d investigate the issue that very evening, then tried to implement it either during the next day, or, at worst, if the computers we’d want to alter were being in use, in the weekend.
    The lessons I learned there is that: (1) you must react quickly and (2) if you put a bit of your heart into your work, you can get surprisingly good results.

    Nice find on the “depressing the price of such information by a “factor of five or 10? on the black market”. I guess the PSN issue is the equivalent of flooding the market with products 🙂

    @” limit the amount of data kept by companies such as Sony and to “age the data””
    This is security basics. If you don’t want to be responsible for safekeeping secret information, then don’t store secret information on your servers. Period.

Leave a Reply

Your email address will not be published. Required fields are marked *

Related Post

The PSN FiascoThe PSN Fiasco

It’s now the US government’s turn to question Sony about its online security, which follows the UK government’s scrutiny into the company’s affairs.

In a letter addressed to PlayStation executive deputy Kaz Hirai, the Subcommittee on Commerce, Manufacturing, and Trade has prepared a list of questions related to the intrusion; the list can be downloaded from the New York Times here. The letter asks several questions that Sony has not disclosed to the public, such as:

  • How many PSN users had a credit card on file
  • Why Sony cannot determine if credit card was stolen.
  • What are Sony’s plans towards increasing its security in the future.

The Subcommittee’s press release states:

“Given the amount and nature of personal information known to have been taken, the potential harm that could be caused if credit card information was also taken would be quite significant. The Subcommittee on Manufacturing, and Trade has a longstanding interest in consumer privacy, identity theft, and industry efforts to address threats posed by unauthorized access to consumers’ personal information resulting from a data breach.”

The Subcommittee is requiring a reply by no later than May 6, as part of a privacy driven effort “to protect consumer information.”

Meanwhile, Kaz Hirai will be holding a press conference tomorrow from Sony Japan, to address the PlayStation Network hacking crisis.

(more…)

Mass Effect 3: What REALLY Went Wrong, And How To Fix ItMass Effect 3: What REALLY Went Wrong, And How To Fix It

NOTE: THIS ARTICLE DISCUSSES THE ENDING AND EVENTS OF MASS EFFECT 3. DO NOT READ IF YOU DO NOT WISH THE GAME TO BE SPOILED FOR YOU.

In this day and age, one learns to take internet outrage with a heavy dollop of salt. The videogame community tends to be reactionary in the worst way, for a few reasons: they tend to be young, they tend to express their immediate feelings almost as a stream of consciousness, and let’s face it, the Greater Internet Dickwad Theory comes into play as well.

When it comes to game endings, when I hear that the community is upset about a game’s ending, I almost always take that as a good sign that the ending is daring and provocative. For example, there was an outcry over the abruptness of the ending of Halo 2, which had the nerve to conclude with a cliffhanger. The 2009 Prince of Persia reboot ended with the player undoing all of the work to free an ancient evil god they’d just imprisoned.

So when I heard that there was a growing outcry about the endings of Mass Effect 3, my interest peaked, because invariably, that meant the story was provocative and daring, instead of predictable and boring.

(more…)

Retro Gaming: Mega Man 9 Get’s Flicker and BugsRetro Gaming: Mega Man 9 Get’s Flicker and Bugs

Capcom isn’t fooling around, they know their market for Mega Man 9 on Xbox Live, WiiWare and PSN and its nostalgic gamers with a desire to be a kid again. Any retro gamer will tell you the old school experience must include some pixel flickers, slow down and 8-bit style bugs.

They have decided to include an optional feature to enable old school bugs on purpose. The limitations of early hardware like the NES caused situations where you would only see a limited number of creatures on the screen at any one time else things slowed down, flickered and got undesirable fast. What used to be undesired is now nostalgic!

“Yeah, there were some things, like you couldn’t have more than three enemies on the screen at once, so we had to make sure that that’s how it stayed in our game. In the part with the dragon with the flame, [there should be] flickering, and whatnot,” noted the game’s producer. “In the options of this game, you can adjust that, unlike the old games. We purposely put some of those old-school bugs into this game, so it does recreate that feel.” (joystiq)

Luckily these options are disabled and can be enabled to get a bit of old world feel if your little heart desires. For most of us, we should have moved on from the old times and are ready to play old school games on new school hardware to show off a bit more fluid 8-bit logic. Not so for everyone, which is why the feature was added as an optional one.

Staying true to old school computing in an emulator is extremely important when playing old ROM games because the game was coded with a certain speed and understanding of the hardware. Change the hardware without updating the game can lead to an unusable product. Mega Man 9, however, is a new game so it doesn’t have to adhere to old standards. But, it’s funny to see it try.