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
Video
Cartoon
Current Issue
Flash Poll
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-1291
Published: 2015-09-03
The ContainerNode::parserRemoveChild function in core/dom/ContainerNode.cpp in Blink, as used in Google Chrome before 45.0.2454.85, does not check whether a node is expected, which allows remote attackers to bypass the Same Origin Policy or cause a denial of service (DOM tree corruption) via a web s...

CVE-2015-1292
Published: 2015-09-03
The NavigatorServiceWorker::serviceWorker function in modules/serviceworkers/NavigatorServiceWorker.cpp in Blink, as used in Google Chrome before 45.0.2454.85, allows remote attackers to bypass the Same Origin Policy by accessing a Service Worker.

CVE-2015-1293
Published: 2015-09-03
The DOM implementation in Blink, as used in Google Chrome before 45.0.2454.85, allows remote attackers to bypass the Same Origin Policy via unspecified vectors.

CVE-2015-1294
Published: 2015-09-03
Use-after-free vulnerability in the SkMatrix::invertNonIdentity function in core/SkMatrix.cpp in Skia, as used in Google Chrome before 45.0.2454.85, allows remote attackers to cause a denial of service or possibly have unspecified other impact by triggering the use of matrix elements that lead to an...

CVE-2015-1295
Published: 2015-09-03
Multiple use-after-free vulnerabilities in the PrintWebViewHelper class in components/printing/renderer/print_web_view_helper.cc in Google Chrome before 45.0.2454.85 allow user-assisted remote attackers to cause a denial of service or possibly have unspecified other impact by triggering nested IPC m...

Dark Reading Radio
Archived Dark Reading Radio
Another Black Hat is in the books and Dark Reading was there. Join the editors as they share their top stories, biggest lessons, and best conversations from the premier security conference.