Risk
2/10/2014
09:05 AM
Kate Borten
Kate Borten
Commentary
Connect Directly
RSS
E-Mail
100%
0%

Healthcare Information Security: Still No Respect

More than a decade after publication of HIPAA's security rule, healthcare information security officers still struggle to be heard.

When I first was introduced to the infosec subculture in the1990s, there seemed to be very few of us in healthcare provider organizations with official security roles. And we were mostly "stuckees" who just fell into the job. (You know, someone in charge pointed at you and said, “You’re now our security person.”) 

You’d think patient privacy, and, thus, security, would be embraced, but it wasn’t so. Doctors and nurses swore they already were privacy sensitive. And, after all, we weren’t banks holding money to be stolen… Who’d want to steal our databases with a few million boring medical records? 

Photo credit:  Flickr
Photo credit: Flickr

We struggled to be heard in our organizations, to implement policies and strengthen passwords. But we were often thwarted and viewed as obstacles, if not threats, to patient care. Where else would you be told that patients might die because you made doctors memorize their own secret, six-character passwords? Or were made to feel audacious asking for staff while nurses were being laid off?

My own IT co-workers openly shared their passwords and laughed at my raised eyebrows. (OK, so I was an easy target with my earnestness and zeal, but still…) When the system administrator of our token authentication server left for another job, he handed in his token with his PIN taped to the back. He didn’t even try to hide the fact that he’d completely undermined the token’s purpose. 

My healthcare infosec colleagues and I did have a smattering of support from sincere leaders who got it. These champions understood the risks and the value of an infosec program to mitigate them, at least theoretically. One of my favorite doctors reported chiding medical residents for failure to log off their exposed hallway computers before walking away, and he routinely logged off any open computer he found. But when it came down to requiring managers to take time to review lists of users, for example, or, most challenging of all, enforcing security policies across the organization, support withered.

We stuckees consoled each other at healthcare security and privacy conferences. We attended sessions where we shared ideas for getting leadership buy-in and for running an infosec program on a tiny budget. But, to rephrase Rodney Dangerfield’s famous line, we lamented, "We don’t get no respect."

So what’s changed in healthcare security since the 90s? HIPAA’s security rule has definitely heightened awareness, and the word "security" pops up a lot more now. Healthcare organizations and their business associates have security policies, they talk about security at workforce training sessions, and they have designated security officials -- all required by HIPAA.

But here we are, more than 10 years after the security rule’s publication, and not nearly enough has changed. Yes, some organizations have recognized that this isn’t simply about regulatory compliance; it’s a business risk issue. And to do the job right, there needs to be a formal infosec program with a visible structure, real security expertise, and support at the top.  

Where are the CISOs?
From what I see, security savvy organizations are in the minority. Too many organizations’ infosec programs are still very immature. The glaring signs are: 1) lack of internal security expertise; and 2) insufficient resources to carry out security functions.

HIPAA requires healthcare organizations and their business associates to designate an information security official or ISO. But time and again I see the ISO is either a maxxed-out CIO with no security background or experience, or else a network administrator stuckee who may have some notion of network security, but no training, and little time for this extra responsibility. 

It continues to be unusual to see a full-time ISO with security credentials, much less staff, in other than the largest healthcare networks. Yet even in smaller organizations, reasonable security programs are by definition complex, require awareness of good security practices, and require people to implement and monitor security processes. Never mind the question of regulatory compliance. It’s just not possible to have such a program without expertise and resources.

Even mature infosec programs can’t eliminate all risk. But too many breaches today -- not only in healthcare but in other sectors -- aren’t due to zero-day attacks exploiting previously undiscovered vulnerabilities. They are avoidable events that are frequently tied to lack of security expertise and resources to implement security controls.

In healthcare, and elsewhere, lost and stolen laptops, hard drives, USB drives, and the like with unencrypted patient information are the biggest sources of breaches. To be sure, with today’s wide use of a variety of tablets and smartphones, mitigation strategies such as encrypting all end-user devices and media can be challenging financially and technologically. But slapdash security will keep us in a breach-a-week muddle.

We need to appoint ISOs with security knowledge and experience, and then give them enough clout and staff to accomplish the processes required by HIPAA and good practice. It’s time for senior leaders to finally recognize the essential business value of infosec and provide the necessary resources to make it happen. We need  R-E-S-P-E-C-T!  

Kate Borten, CISSP, CISM, provides her clients with expertise in security, privacy, and health IT from over 20 years inside the healthcare industry. In the 1990s she led the enterprise-wide security program at Massachusetts General Hospital, and as Chief Information Security ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Page 1 / 2   >   >>
anon5450533792
50%
50%
anon5450533792,
User Rank: Apprentice
4/18/2014 | 6:42:31 AM
Re: Exceptions to the rule?
We found in our recent independent research that hospitals, care providers and medical insurers experience twice as many internal security breaches in comparison to other sectors. As we are seeing more and more patient data being stored digitally, it's important that the appropriate steps are being taken to ensure that that data is secure from both malicious attack and accidental breaches.

More information from this report can be viewed here:

http://www.isdecisions.com/blog/it-security/healthcare-suffers-double-the-average-amount-of-internal-security-breaches/

 
asksqn
50%
50%
asksqn,
User Rank: Apprentice
3/27/2014 | 2:56:12 PM
Preaching to the choir
The weakest link in the HIPAA chain will always be the human one as far too many medical personnel are too self important (cough doctors cough) to even remember their own passwords.  To a lesser extent, nursing personnel also don't have a clue.  The bottom line is that security is not afforded a whole lot of respect (despite tremendous lip service to it by CEOs) because the cost of hiring competent personnel to implement (and train users) cuts too deeply into corporate healthcare profits.
J_Brandt
50%
50%
J_Brandt,
User Rank: Apprentice
2/14/2014 | 10:33:43 AM
Inconvenience and expense
"From what I see, security savvy organizations are in the minority." So true.  Security is intrusive on the end user.  It clogs up workflows.  It is expensive.  Many measures can be circumvented by an uninformed and disinterested user.  To the uninitiated it's just an inconvenience.  Is it any wonder that senior executives and management would rather avoid it?  Too many people want the barest minimum, (which is often below the true bare minimum), not realizing that route often ends up being much MUCH more expensive.
Kate Borten
50%
50%
Kate Borten,
User Rank: Apprentice
2/13/2014 | 6:12:47 PM
Re: EPHI Data Breach - One lost laptop or 10,000 recycled computers?
I agree that recycling is a risky business.  However, under HIPAA those companies are "Business Associates" and subject to government penalties for noncompliance.  That includes responsibility for destruction processes - such as per NIST Special Publication 800-88 - that prevent accidental disclosure of ePHI.  Even if the small healthcare organization fails to get a signed BA contract, HHS says "if it walks like a duck..."  These companies are HIPAA BAs.
Gary Scott
50%
50%
Gary Scott,
User Rank: Apprentice
2/13/2014 | 6:01:55 PM
EPHI Data Breach - One lost laptop or 10,000 recycled computers?
The biggest source of data breaches is not the one or two stolen laptops we hear about in the news but, the 100,000's of PCs and loose hard drives that organizations donate or send out for recycling. 

Small healthcare organizations continue to rely on electronic recycling companies to destroy hard drives and other digital media which may contain 1 million EPHI records each.  These unvetted recycling companies are allowed full access to EPHI - computer hard drives - from the time they leave the healthcare organization until the drives are finally destroyed.  

Organizations should insist that electronic recyclers physically shred hard drives (EPHI) prior to leaving the organizations custody.
Marilyn Cohodas
50%
50%
Marilyn Cohodas,
User Rank: Strategist
2/13/2014 | 3:00:23 PM
Re: Funding or structure?
"People don't know what they don't know." 

Kate, I really think that is true on so many levels. On the medical side, I think doctors' training is to diagnose a condition through medical tests. In many cases, rule out things to discover what a patient doesn't have. Figuring out what you don't know is much much harder... That's true in medicine, InfoSec and most everything we do in life!
Kate Borten
50%
50%
Kate Borten,
User Rank: Apprentice
2/11/2014 | 3:17:48 PM
Re: Funding or structure?
It's not inconsistent for CIOs to say their job is to keep the organization out of the papers (and really mean it), and yet not have good infosec programs in place.  They often don't know what a strong program looks like.  This is a big problem since, in my experience, many organizations of all sizes - but especially small - are not compliant.  They don't know what they don't know.  I'm sympathetic to the regulatory burden in healthcare, but good security is good business.  I think the real issue comes down to money.
WKash
50%
50%
WKash,
User Rank: Apprentice
2/10/2014 | 6:07:22 PM
50 Reasons Why We Need Better EHR Security
Depending on what report you read, a stolen medical ID number and record currently sells on the black market for $50 (and as much as $100), whereas a stolen credit card number is only worth $1.  The reason: In gaining access to a person's health records, a hacker has – in one fell swoop – acquired almost full reign of a person's identity, and the opportunity for prolonged fraud against the medical establishment. Yet it's clear the medical community is no where close to having the security controls of say, the banking industry, or the federal government.
zcobb
50%
50%
zcobb,
User Rank: Apprentice
2/10/2014 | 3:25:56 PM
Breaching misperceptions
Thank you so much for this article. Sheds light on a serious problem. Not enough organizations realize any PII is fair game for cyber crooks, the fact that it might be PHI doesn't enter the equation for many of them. And this is so true: "But too many breaches today -- not only in healthcare but in other sectors -- arenít due to zero-day attacks exploiting previously undiscovered vulnerabilities. They are avoidable events that are frequently tied to lack of security expertise and resources to implement security controls." Agreed! Stephen Cobb, CISSP
Laurianne
50%
50%
Laurianne,
User Rank: Apprentice
2/10/2014 | 2:37:52 PM
Funding or structure?
This paints quite a different picture than what I have heard from top hospital CIOs, who say things like "It is part of my job to keep us out of the newspaper." Those CIOs speak of a crushing regulatory burden right now. How are the smaller healthcare organizations keeping up with it, if the lack of expertise is this extreme?
Page 1 / 2   >   >>
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-0607
Published: 2014-07-24
Unrestricted file upload vulnerability in Attachmate Verastream Process Designer (VPD) before R6 SP1 Hotfix 1 allows remote attackers to execute arbitrary code by uploading and launching an executable file.

CVE-2014-1419
Published: 2014-07-24
Race condition in the power policy functions in policy-funcs in acpi-support before 0.142 allows local users to gain privileges via unspecified vectors.

CVE-2014-2360
Published: 2014-07-24
OleumTech WIO DH2 Wireless Gateway and Sensor Wireless I/O Modules allow remote attackers to execute arbitrary code via packets that report a high battery voltage.

CVE-2014-2361
Published: 2014-07-24
OleumTech WIO DH2 Wireless Gateway and Sensor Wireless I/O Modules, when BreeZ is used, do not require authentication for reading the site security key, which allows physically proximate attackers to spoof communication by obtaining this key after use of direct hardware access or manual-setup mode.

CVE-2014-2362
Published: 2014-07-24
OleumTech WIO DH2 Wireless Gateway and Sensor Wireless I/O Modules rely exclusively on a time value for entropy in key generation, which makes it easier for remote attackers to defeat cryptographic protection mechanisms by predicting the time of project creation.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Sara Peters hosts a conversation on Botnets and those who fight them.