Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

4/26/2011
11:09 AM
50%
50%

Federal ID Strategy To Boost Health Data Security

Voluntary plan which seeks two-factor authentication and for online identity management should find wide application in healthcare.

Slideshow: RFID In Healthcare
Slideshow: RFID In Healthcare
(click image for larger view and for full slideshow)
A federal plan to involve the private sector in beefing up online identity management and user authentication, while also making it easier for individuals to manage passwords, should find plenty of applications in healthcare--which is exactly what the Obama administration envisions.

The National Strategy for Trusted Identities in Cyberspace, a roadmap released earlier this month for protecting consumers from fraud and identity theft, calls for the voluntary building of an "identity ecosystem" in which consumers can have a single, user-specific credential to log into any participating website. This, according to federal officials, will allow security-conscious sectors, including healthcare and finance, to make new online services available.

"[I]ndividuals and businesses need to be able to check each other's identity for certain types of sensitive transactions, such as online banking or accessing electronic health records," the 52-page document reads. Among other things, the strategy calls for wider adoption of two-factor authentication and unique security credentials for each user.

This is exactly the sort of thing healthcare needs, according to Hussam Mahgoub, senior VP for corporate development and research--and resident security specialist--at Diversinet, creator of a secure platform for developing mobile healthcare applications. "There's a lot of confusion in the marketplace about security and privacy," Mahgoub said.

Of particular worry, according to Mahgoub, is that the Health Insurance Portability and Accountability Act's (HIPAA) privacy and security regulations don't address "strong authentication" for users when they access protected health information (PHI).

Diversinet, which is based in Toronto but does most of its business in the United States, recently published a white paper listing nine best practices for securing health data on mobile networks and devices, that in many ways dovetails with the federal strategy. Diversinet recommends installing apps on smartphones, tablets, and laptops to turn each device into a kind of "wallet" for PHI. Sensitive data should be encrypted and the app should be able to deactivate or delete PHI from lost or stolen devices, just as banks and retailers can deactivate lost credit cards, Mahgoub explained.

Jeff Sponaugle, chief security and technology officer for Beaverton, Ore. healthcare connectivity company Kryptiq, sees at least one recent change in healthcare that needs this kind of approach. Interim Drug Enforcement Agency (DEA) regulations that took effect in June 2010 allow the electronic prescribing of certain controlled substances such as narcotics, but only with enough security in place to satisfy the law enforcement community, which has a lot more pull with the DEA than does the health IT industry.

"With electronic prescribing of controlled substances, two-factor authentication will be coming to the desktop of physicians and staff," Sponaugle said in an email. "The requirements for [electronic prescriptions for controlled substances] are very clear and do provide a 'need' for the physician to get some kind of digital ID."

Sponaugle noted, however, that two-factor authentication and other "strong" forms of digital security have been around for years, but often place too high of a burden on users to encourage widespread adoption. Resistance may rise when the users happen to be time-crunched and technologically challenged physicians.

"The key for promoting two-factor is to make it integrated into the application the doctor uses most," reported Sponaugle, who said that Kryptiq tries whenever possible to integrate its platform for secure messaging and e-prescribing into other companies' electronic medical records (EMRs). "As the EMRs add front-facing, two-factor workflows, we will use that same infrastructure for messaging. It would be a disaster if you made a doctor use a different two-factor system for the EMR, and yet another different system for messaging or prescribing," Sponaugle said.

"In the end, the goal of the second factor is to provide some protection from the key problem in security, which is people. People choose poor passwords, reuse them, tell them to people, log in from a kiosk in a coffee shop with a key logger, etc.," Sponaugle added. "Coming up with good workflow usability of the two factors is what will make it succeed."

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Commentary
Cyberattacks Are Tailored to Employees ... Why Isn't Security Training?
Tim Sadler, CEO and co-founder of Tessian,  6/17/2021
Edge-DRsplash-10-edge-articles
7 Powerful Cybersecurity Skills the Energy Sector Needs Most
Pam Baker, Contributing Writer,  6/22/2021
News
Microsoft Disrupts Large-Scale BEC Campaign Across Web Services
Kelly Sheridan, Staff Editor, Dark Reading,  6/15/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-32823
PUBLISHED: 2021-06-24
In the bindata RubyGem before version 2.4.10 there is a potential denial-of-service vulnerability. In affected versions it is very slow for certain classes in BinData to be created. For example BinData::Bit100000, BinData::Bit100001, BinData::Bit100002, BinData::Bit<N>. In combination with &lt...
CVE-2021-35041
PUBLISHED: 2021-06-24
The blockchain node in FISCO-BCOS V2.7.2 may have a bug when dealing with unformatted packet and lead to a crash. A malicious node can send a packet continuously. The packet is in an incorrect format and cannot be decoded by the node correctly. As a result, the node may consume the memory sustainabl...
CVE-2021-2322
PUBLISHED: 2021-06-23
Vulnerability in OpenGrok (component: Web App). Versions that are affected are 1.6.7 and prior. Easily exploitable vulnerability allows low privileged attacker with network access via HTTPS to compromise OpenGrok. Successful attacks of this vulnerability can result in takeover of OpenGrok. CVSS 3.1 ...
CVE-2021-20019
PUBLISHED: 2021-06-23
A vulnerability in SonicOS where the HTTP server response leaks partial memory by sending a crafted HTTP request, this can potentially lead to an internal sensitive data disclosure vulnerability.
CVE-2021-21809
PUBLISHED: 2021-06-23
A command execution vulnerability exists in the default legacy spellchecker plugin in Moodle 3.10. A specially crafted series of HTTP requests can lead to command execution. An attacker must have administrator privileges to exploit this vulnerabilities.