Loose Lips Sinks Pennsylvania's Chief Information Security Officer

Information Comes Out at 2010 RSA Conference Where Open Discussion of Security Breaches Touted

2 min read
Loose Lips Sinks Pennsylvania's Chief Information Security Officer

According to today's ComputerWorld, Pennsylvania's Chief Information Security Officer (CISO) Robert Maley was fired after discussing a previously undisclosed security "anomaly" at the US RSA 2010 conference last week. Mr. Maley, the ComputerWorld story says, apparently disclosed that:

"a Philadelphia-area driving school ... was trying to get early driving tests for its students. The source said someone at the school exploited a configuration 'anomaly' in the Department of Transportation's online driver's test scheduling system."

As a result, the driving school could  jump the queue in scheduling tests for its students.

According to ComputerWorld, Mr. Maley, who was the state's CISO for four years and its first one, hadn't been authorized to speak about the incident, which a Pennsylvania government spokesperson says is being investigated by the Pennsylvania State Police.

The spokesperson also said that the incident was not a security issue, although she would not describe what the anomaly was or how it was supposedly exploited.

The ComputerWorld story also noted that Pennsylvania's IT security staff and budget have been reduced by approximately 40% each over the past 18 months (the state is looking at a $475 million deficit for this fiscal year, which ends June 30th) and according to unnamed sources, the remaining security staff has been told to shut up about cyber security problems.

I guess you don't want to advertise that the state is vulnerable to cyber attacks, do you?

Ironically, also at the RSA conference was a panel on the need for companies to tell law enforcement about security breaches. Companies are often hesitant to do so because of the perceived bad publicity that sometimes comes with a call. Privately run companies can more easily keep such calls to law enforcement quiet - public companies can for a short time but not forever.

Pennsylvania government officials did call law enforcement, but it also did not inform the public of the matter either. If it was trying to hide the incident because of the bad "political" publicity that it might create, firing the CISO probably wasn't a smart move. A quiet reprimand would have been better, and no one would have much noted the "anomaly." Now it is a big deal.

And if the State was trying to make a point to other state government employees by quickly firing the CISO over talking without permission, I expect that to backfire as well since it not only looks petty, but the message, rightly or wrongly, is that the current Pennsylvania government has lots of dirty cyber security linen to hide. Expect the state's press to start digging for it.

Now try hiring an experienced CISO into that environment. Unless, of course, Pennsylvania doesn't really want one.

The Conversation (0)

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
Vertical
A plate of spaghetti made from code
Shira Inbar
DarkBlue1

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less
{"imageShortcodeIds":["31996907"]}