July 13, 2007

The State of Ohio Data Theft — One More Time: Independent. Investigation.

Filed under: Money Tip of the Day, Privacy/ID Theft, Taxes & Government — TBlumer @ 10:27 am

I’m late getting to this (some of the others who were on this much earlier included RAB [here, here, and here], Matt at WoMD, Conservative Culture, and the Keeler Report), but I surely won’t ignore it:

671,000 more at risk in state data theft

More than 671,000 Ohioans who haven’t cashed refund checks or have done business with the state were added yesterday to the list of people whose personal information may be at risk because of last month’s theft of a state computer backup storage device.

In all, the number of Ohioans or businesses with some form of personal data on the device has climbed to 1.1 million.

Anyone who believes their personal information may be at risk should contact the toll-free number or the web space set up to deal with the matter. They are 800-267-4474 and www.ohio.gov/idprotect, respectively.

Is there anyone left who considers the Strickland Administration’s pattern of drip-by-drip revelation acceptable?

I don’t think the Governor is orchestrating the buffoonery, but it’s understandable that many think he is is. The only way to clear the air is to do something I suggested when we learned that the data involved was, contrary to original assertions, not encrypted, then called for when it was learned that the number of people affected was “only” a couple of hundred thousand, and then “only” a half million: Conduct an independent investigation.

If the Governor doesn’t set up an independent investigation, he will only have himself to blame when the cloud over the ongoing snafu parks over his head, and stays there.

____________________________________

UPDATE: I have to note that the Blade’s Jim Provance felt it necessary to cite the Governor’s high approval numbers at the end of his report — as if that’s relevant, especially since the poll was done before the latest revelation.

No Comments

No comments yet.

RSS feed for comments on this post.

Sorry, the comment form is closed at this time.