Risk
8/14/2013
12:26 PM
Connect Directly
RSS
E-Mail
50%
50%

Most VA Privacy Breaches Trace To Paper, Not PCs

Majority of data breaches at the Veterans Administration result from mislaid paper documents, official says, not stolen PCs.

5 Helpful Online Services From Uncle Sam
5 Helpful Online Services From Uncle Sam
(click image for larger view)
Most data breaches at the Veterans Affairs Department involve mishandled paper documents, not information technology assets, proving that the agency is doing a good job of protecting its computer systems, a VA IT leader told InformationWeek Government recently.

"Between 96 and 98 percent of our [data breach] incidents -- it varies from month to month -- deal with physical paper where … people are not thinking about the fact that that piece of paper they're carrying around making benefits determinations has sensitive information and they need to protect it," said Stephen Warren, VA acting assistant secretary for information and technology. "It's an area that we spend a lot of time and training on. We are constantly updating our campaign to inform the staff that they have to take this seriously. We are constantly reinforcing the message that it matters."

The central point that Warren makes to VA employees who handle sensitive information is that patients can't get critical services if their identity has been stolen. "It has huge impact on an individual," he said.

[ The Veterans Administration leads in telemedicine. Read Why The Private Sector Lags VA In Telehealth. ]

Most of these data breach incidents are cited as "mishandled or misused physical or verbal information" in the department's monthly reports to Congress of data incidents, which are assembled by the VA Office of Information Security's Incident Resolution Team.

In one case involving the VA's Milwaukee, Wis., facility last April, a paper notification letter was inadvertently sent to the wrong beneficiary. The letter contained the beneficiary's name, address, home phone number, Social Security number and bank account information. The beneficiary who erroneously received the document called VA to report the incident and returned it to the facility.

The VA employees involved in the Milwaukee incident were counseled on the importance of handling personally identifiable information, according to the April report.

In another April case, documents containing the full names and the last four digits of the Social Security numbers of 270 veterans were found on two separate occasions in men's restrooms in a Nashville, Tenn., VA office. The veterans were notified of the incident and investigators concluded that the documents were "inadvertently" left in the restrooms by unidentified employees who had attended morning meetings in the building.

According to the April report, there were 227 incidents of data breaches across the VA between April 1 and April 28 in which information was manually mishandled in one way or another. In comparison, only eight cases of stolen or missing PCs or laptops were reported and investigated in the same month.

Missing laptop or PC cases often involve inventory mixups, Warren said. For example, in an April incident at a Coatsville, Pa., VA facility, four desktops PCs were reported missing from the inventory; three of them were later found. No personally identifiable information or protected health information was stored on any of the PCs, the response team found.

"If you consider the fact the VA has about 440,000 people that we service and that the department over 900,000 devices on the network, [a data breach count relating to IT assets] of somewhere between one and 10 in a month is pretty good," Warren said. "And many of those are things disappearing in inventory. Many are found subsequently because they got moved somewhere."

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
jaysimmons
50%
50%
jaysimmons,
User Rank: Apprentice
8/20/2013 | 4:25:58 AM
re: Most VA Privacy Breaches Trace To Paper, Not PCs
ItGÇÖs refreshing to see that IT security isnGÇÖt to blame in
this case, and that it seems the VA has been doing a good job in keeping their
digital information secure. Human error is always going to be a factor though, especially when you are dealing with protected health information on paper. More training and harsher repercussions may work in lowering these breaches a bit, but the human factor is always there and mistakes will happen.

Jay Simmons
Information Week Contributor
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Must Reads - September 25, 2014
Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-5619
Published: 2014-09-29
The Sleuth Kit (TSK) 4.0.1 does not properly handle "." (dotfile) file system entries in FAT file systems and other file systems for which . is not a reserved name, which allows local users to hide activities it more difficult to conduct forensics activities, as demonstrated by Flame.

CVE-2012-5621
Published: 2014-09-29
lib/engine/components/opal/opal-call.cpp in ekiga before 4.0.0 allows remote attackers to cause a denial of service (crash) via an OPAL connection with a party name that contains invalid UTF-8 strings.

CVE-2012-6107
Published: 2014-09-29
Apache Axis2/C does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.

CVE-2012-6110
Published: 2014-09-29
bcron-exec in bcron before 0.10 does not close file descriptors associated with temporary files when running a cron job, which allows local users to modify job files and send spam messages by accessing an open file descriptor.

CVE-2013-1874
Published: 2014-09-29
Untrusted search path vulnerability in csi in Chicken before 4.8.2 allows local users to execute arbitrary code via a Trojan horse .csirc in the current working directory.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
In our next Dark Reading Radio broadcast, we’ll take a close look at some of the latest research and practices in application security.