Risk
1/24/2012
03:49 PM
50%
50%

7 Tools To Tighten Healthcare Data Security

Most of the largest healthcare data security and privacy breaches have involved lost or stolen mobile computing devices. Consider these tools and tips for protecting patient data and managing breaches.
Previous
1 of 7
Next


Smartphones, tablets, and other mobile devices can help facilitate better communication and more extensive patient-caregiver interaction. But they're also easy to lose and more challenging for IT departments to manage.

In fact, mobile devices--including laptop computers, flash drives, and other portable gear--have been involved with some of the largest Health Insurance Portability and Accountability Act (HIPAA) breaches to date affecting 500 or more individuals, according to the Dept. of Health and Human Services, which tracks those incidents on a data breach reporting website that healthcare players have dubbed, the Hall of Shame.

At the same time, healthcare providers have a lot more to lose besides their reputations when it comes to HIPAA violations: Under the HITECH Act, HHS now can impose penalties of as much as $1.5 million annually per organization--per hospital or doc practice--for violating HIPAA privacy rules.

Unfortunately, many of the largest data and security incidents--as well as large HIPAA breaches involving paper documents--have been caused by human error, according to HHS. But besides improving training of staff about best practices for protecting patient data privacy and security--and not allowing any sensitive data to be stored on mobile devices themselves--healthcare organizations can tap an array of vendors' software and other products to safeguard protected health information. Here's a look at some of those tools.

Previous
1 of 7
Next
Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6501
Published: 2015-03-30
The default soap.wsdl_cache_dir setting in (1) php.ini-production and (2) php.ini-development in PHP through 5.6.7 specifies the /tmp directory, which makes it easier for local users to conduct WSDL injection attacks by creating a file under /tmp with a predictable filename that is used by the get_s...

CVE-2014-9652
Published: 2015-03-30
The mconvert function in softmagic.c in file before 5.21, as used in the Fileinfo component in PHP before 5.4.37, 5.5.x before 5.5.21, and 5.6.x before 5.6.5, does not properly handle a certain string-length field during a copy of a truncated version of a Pascal string, which might allow remote atta...

CVE-2014-9653
Published: 2015-03-30
readelf.c in file before 5.22, as used in the Fileinfo component in PHP before 5.4.37, 5.5.x before 5.5.21, and 5.6.x before 5.6.5, does not consider that pread calls sometimes read only a subset of the available data, which allows remote attackers to cause a denial of service (uninitialized memory ...

CVE-2014-9705
Published: 2015-03-30
Heap-based buffer overflow in the enchant_broker_request_dict function in ext/enchant/enchant.c in PHP before 5.4.38, 5.5.x before 5.5.22, and 5.6.x before 5.6.6 allows remote attackers to execute arbitrary code via vectors that trigger creation of multiple dictionaries.

CVE-2014-9709
Published: 2015-03-30
The GetCode_ function in gd_gif_in.c in GD 2.1.1 and earlier, as used in PHP before 5.5.21 and 5.6.x before 5.6.5, allows remote attackers to cause a denial of service (buffer over-read and application crash) via a crafted GIF image that is improperly handled by the gdImageCreateFromGif function.

Dark Reading Radio
Archived Dark Reading Radio
Good hackers--aka security researchers--are worried about the possible legal and professional ramifications of President Obama's new proposed crackdown on cyber criminals.