theDocumentId => 1332365 7 Ways to Better Secure Electronic Health Records

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.

Application Security

7/24/2018
11:00 AM
50%
50%

7 Ways to Better Secure Electronic Health Records

Healthcare data is prime targets for hackers. What can healthcare organizations do to better protect all of that sensitive information?
Previous
1 of 8
Next

January was not a particularly bad month for electronic health record (EHR) breaches. Still, in just those 31 days, nearly a half-million records were exposed to unauthorized viewers.

According to the HIPAA Journal, the top four breaches in January were all the result of hacking or an IT incident, exposing more than 387,000 records. While these numbers pale in comparison to the tens of millions of records involved in recent credit bureau and social media hacks, the sensitive nature of the records amplify the damage done.

What's more, the number of records lost to hacking or IT incident has steadily increased year over year since 2009 (though authors of the "January 2018 Healthcare Data Breach Report" note that at least some of that increase could be due to a lack of reporting in earlier years). 

The reports points to several reasons why healthcare breaches continue to occur. First, they're valuable records that have currency with criminals and nation-state actors. Next, healthcare organizations come in a dazzling array of sizes, with an equivalent array of IT security skill levels at their service. Finally, almost every step along the records trail involves a human, and humans are infamously fallible. So what's a conscientious organization to do?

In this article, we look at seven ways to better secure this sensitive healthcare data. This is far from an exhaustive list, but each one is something that an organization can reasonably do to reduce its risk. Of note, many of these points can be applied to any organization with sensitive data to protect.

Have you found other steps worth taking to protect sensitive data? What have you tried and found effective? Let us know in the comments section, below.

(Image: pandpstock001)

 

 

 

Black Hat USA returns to Las Vegas with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier security solutions and service providers in the Business Hall. Click for information on the conference and to register.

 

Curtis Franklin Jr. is Senior Analyst at Omdia, focusing on enterprise security management. Curtis has been writing about technologies and products in computing and networking since the early 1980s. He has been on staff and contributed to technology-industry publications ... View Full Bio
 

Recommended Reading:

Previous
1 of 8
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
tdsan
100%
0%
tdsan,
User Rank: Ninja
7/26/2018 | 3:06:35 PM
Re: The BEST way to secure electronic health records
I agree with the first person who commented on the article (patch fanatic) but there is something flawing with out thinking because the hacks are still occuring, even though the numbers are down, it is still happening. I do think there are a few things that we need to follow that most organizations don't do:

→ Training needs to be put at the forftont, we need to evaluate the talent we have on staff on a consistent basis

→ Firewalls, routers, switches and other network gear needs to be follow the NSA security guidelines and framework - https://www.vmguru.com/2017/04/sizing-your-vmware-infrastructure/ (we need to add to this guideline and continue to test so we can push the envelope (or at least get close)

→ We really need to remove IPv4 from the mix of solutions and move to an IPv6 (pure) environment

→ We need to have a moc setup where we pay someone to hack the environment and we test the people there by putting them into a scenario

→ Application programming methodologies need to be reviewed by qualified hackers who have a deveopment background

→ We need to employ machine learning in the mix of products where the technology is always checking to see who is accessing what and reporting or even thwarting it

→ We need to automate the pentesting process but tailor it to our needs, get it to the point that the vulnerabilities can be mitigating by a autonomic programming change

→ We need to prioritize the threats or vulnerabilities, schedule weekend schedule patch and system updates to ensure the systems meet a certain severity level (sev1-5) and if the sev level is reviewed by outside vendor (reputable)

→ Implement next generation firewalls, endpoint monitoring, NMS, HIDS, NIDS, Zone/Layering and application integration without our existing security tools

→ We need a protocol monitoring device that identifies and baselines relationships between systems and applications, if there is an outside presence, then the system needs to tell us

→ Move pertinent data to zone 0, do not install DB on Web applications (separation of duties) and only allow data to write after a cleansing or holding area (similar to ACH) to ensure the data has not been compromised

→ If multiple records have been extracted by an outside source (Database), there needs to be a warning and action to go along with this potential threat, or at least after 10 records, then something needs to stop the data extraction (notification or autonomic stoppage)

→ If we are not doing business with a specific country, then block those countries that are not in our purvey using ACLs, NGFW with Country blocking capability

→ DNS needs to be configured with DNSSEC using specific keys that are stored in a safe place and only allow queries (recursive) to be done by systems that are internal, anything from the outside trying to access and perform lookups internally with outside IP addresses need to be thwarted

There are other things but this all I can think of right now.

Todd
paul.dittrich
50%
50%
paul.dittrich,
User Rank: Strategist
7/24/2018 | 3:36:35 PM
The BEST way to secure electronic health records
My #1 suggestion:

Be an absolutely merciless fanatic about patching and updating your software.  All of it.  Every day.  On every device you own.

The suggestions in the column are certainly valid but some of them require external experts and/or a higher level of technical skill than simply updating existing software.  IMO, keeping all software 100% up-to-date is the single most important security measure for just about every organization.
Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/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-34432
PUBLISHED: 2021-07-27
In Eclipse Mosquitto versions 2.07 and earlier, the server will crash if the client tries to send a PUBLISH packet with topic length = 0.
CVE-2021-20399
PUBLISHED: 2021-07-27
IBM Qradar SIEM 7.3.0 to 7.3.3 Patch 8 and 7.4.0 to 7.4.3 GA is vulnerable to an XML External Entity Injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose sensitive information or consume memory resources. IBM X-Force ID: 196073.
CVE-2021-20562
PUBLISHED: 2021-07-27
IBM Sterling B2B Integrator Standard Edition 5.2.0.0 through 5.2.6.5_3 and 6.1.0.0 through 6.1.0.2 vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclos...
CVE-2020-18428
PUBLISHED: 2021-07-26
tinyexr commit 0.9.5 was discovered to contain an array index error in the tinyexr::SaveEXR component, which can lead to a denial of service (DOS).
CVE-2020-18430
PUBLISHED: 2021-07-26
tinyexr 0.9.5 was discovered to contain an array index error in the tinyexr::DecodeEXRImage component, which can lead to a denial of service (DOS).