GovernmentExecutive.com

Return to Article: Data on millions of vets stolen from VA employee's home

• 60013
  

  An excellent analysis of the subprime crisis and the scenario of ERM. Concepts like risk management have been publicized and hyped more than they have been practised. The urge for bracing big volumes in quick time (short term gains) have precluded managers and entrpreneurs from spotting long term risks. In India, which is supposedly on the other side of the table, organizations have been going all out towards building volumes under the hype of 'India Growth Story' and nobody has quite found the time or inclination to think about risks. Even where some risk analysis is done it is only on a pro forma basis. At the individual level also people have been pushed into taking huge risks by going for home loans and the like. Assessment of one's risk tolerance level is something totally lacking in India. Only we if can take some real cues from the West.

  Arman Oza Posted October 2, 2008 4:19 AM
• 17003
  

  This is another example as to why it was a huge mistake when the military in the early 70s stopped using serial numbers and went to social security numbers as IDs for serviceman. As a Marine Corps veteran who has been through the VA system, I am concerned for the safety and integrity of my identity. I have seen first hand the devastating consequences that ID theft has on people's lives.

  This moron and his supervisor should be either fired or severely disciplined for this incident. The impacted veterans whose identity may be potentially compromised should be notified by the VA immediately, though I won't hold my breath.

  Shameful lack of common sense!

  GovExec.com reader Posted May 30, 2006 8:27 AM
• 16994
  

  Ted, you are right. This guy should be sitting in a jail cell right now, but instead he is probably at home drawing full pay. That is a crime in itself. It is little wonder the veterans have little faith in the VA system. We have idiots in it who break every law in the book, knowing full well they will get away with it. To be perfectly honest, I have little faith in "Nicholson" myself to run the VA. They need to prosecute, prosecute and prosecute more in these kinds of cases. At least kick the guy out the door.

  Charlie (retired military) Posted May 27, 2006 10:13 PM
• 16906
  

  Doesn't surprise me a bit! The VA is a demoralizing place -- for the Veterans coming in to file claims and for all who work there. I worked there for a few years and believe me, this kind of "mishap" is commonplace. The raters are allowed to take veterans' claim files and work at home! Until someone revamps the whole VA system, this is just one more injustice to all of us veterans.

  GovExec.com reader Posted May 24, 2006 7:49 PM
• 16872
  

  As one of the affected vets, the VA hasn't contacted me yet so I am glad to read it here and pass it on to my fellow affected vets. The theft of this information is a huge problem and could be dormant for awhile.

  Encrypted or not, the VA should never allow this type of information to be taken home! This is what you call a low probability event but with terrible consequences to the millions of vets and their families.

  GovExec.com reader Posted May 23, 2006 9:04 AM
• 16871
  

  That's just great!!! I work for the government and just one year ago they compromised my credit card data when one of the government's credit card contractors lost all my personal info. I was allowed one credit report ... as if the thugs can't wait a year or two before using my info to destroy my life and my credit. I was also allowed to freeze my credit account for six months with no charge. Again, all the thugs have to do is wait before striking. All extra credit reports cost me money and so do the account freeze requests. Oh yeah, you get one free credit report per year so the thugs only have 11.5 months to screw you over. I was also in the military ... I get shafted again!!! We'll probably get one free credit report and one six-month freeze. If the thugs learned anything from the first debacle they'll know to wait six to eight months before striking, then they have 11.5 months to destroy everyone's credit and identity. There's no help for us folks in the government and we will never be properly compensated for being abused. Oh, I forgot ...Uncle Sam is giving us NSPS to make-up for everything. Thanks so much!!!

  Un-Civil Servant

  GovExec.com reader Posted May 23, 2006 9:01 AM
• 16870
  

  The government is too careless with Social Security numbers. The SSN is put on everything. Why? It is not supposed to be an ID. Use something else.

  GovExec.com reader Posted May 23, 2006 8:54 AM
• 16868
  

  I do hope that the fellow who lost the disk containing the personal data on millions of vets is not hit with the "f" word. Heaven forbid that any government employee should be "f-ed" for anything ever. Remember that they also serve who are only timeservers.

  Lawrence Stepelevich Posted May 23, 2006 8:41 AM
• 16863
  

  1) This turkey should be in jail, not setting at home getting paid to do nothing.

  2) He should be held personally responsible for any financial loss suffered by anyone that is impacted.

  3) VA should notify the credit bureaus to lock down these files for at least six months while the extent of the damage is fully investigated. How many 60-plus year olds are setting in full-time care and won't even know they are in danger? Yes, it makes it hard to get instant credit, (which making it harder is not necessarily bad), but at least they are protected in the near term.

  4) The FBI should keep a close watch on him to make sure the burglary is not a scam to sell this information.

  Ted Posted May 23, 2006 8:24 AM
• 16850
  

  No one has been fired yet. The individual who took this home and his supervisor need to be on the street now! Security has gone to hell because there are a bunch of losers working in government.

  Mike Kelley Posted May 23, 2006 6:01 AM
• 16849
  

  Two words that should apply to every government database file: data encryption.

  GovExec.com reader Posted May 23, 2006 5:52 AM