(Photo courtesy of wazzywooze at Flickr)
It never ceases to amaze me how a lack of information security translates into official statements that no one is aware of any identity theft that has occurred.
With as many people, we know have been compromised, and accounting for episodes like the one below where we probably aren't sure, who really knows?
The State of Nevada has a possible compromise, where no one seems to be certain, whether or not, a lot of people were compromised.
From the article written about this by RJG.com:
Hundreds of CDs containing payroll information about state employees, including Social Security numbers, have either been lost or stolen over the last three years.
That's the word from state Personnel Director Todd Rich, who says the system has been tightened to prevent unauthorized people from getting employee information.
Rich says his department sent a total of more than 13,000 CDs to 80 agencies for review every two-week pay period over the last three years. He says as many as 470 are still missing, but his agency has NOT been notified of any identity theft as a result.
The powers that be have since instituted putting a password on the CDs, along with a requirement that they be signed for.
The person, Jim Elste, who revealed the fact that the CDs were missing was fired. He claims it was for revealing this matter, but the State is claiming his employment was terminated for "poor management and lack of anger control."
There have been so many data breaches and so many people compromised, if they were to become an identity theft victim, it might be nearly impossible to figure out where the crook got their information.
No wonder, whenever a suspected breach occurs, no one is SURE if anyone has become a victim of identity theft. The only thing we can be sure of is that there are a lot of victims out there and the number is growing.
Reno Gazette-Journal story, here.
If you would like to see how many people have been compromised -- the list grows VERY frequently -- the Privacy Rights Clearinghouse tracks reported breaches, here.
As of this writing, this one isn't listed as a breach yet!