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

9/23/2015
06:00 PM
Connect Directly
Twitter
RSS
E-Mail
100%
0%

Healthcare Organizations Twice As Likely To Experience Data Theft

Bad guys very willing to invest in attacking medical data, but healthcare not very willing to invest in defending it.

Healthcare institutions are twice as likely to experience data theft than other sectors, and already see 3.4 times more security incidents, according to a study released today by Raytheon and Websense.

Why is healthcare so popular with attackers? Perhaps because the balance sheet tips in their favor. Medical records are very desirable on the black market, because medical records, themselves, may be a treasure trove of PII, financial information, and insurance numbers.

The exact figures vary, but while basic PII may run for just $1 on the black market these days, Jim Trainor of the FBI Cybersecurity Division told CBS News in February that "PHI records can go from 20 say up to -- we've even seen $60 or $70." A new report released by BitSight today references a recent report by NPR's "All Things Considered" which found a "value pack" of just 10 Medicare numbers that sold for about $4,700.

Yet, security measures that ensure those records stay confidential can inhibit patient care -- or at least that's how it seems to some medical professionals. Nurses and physicians fully understand the importance of data availability, but when patients' lives are on the line, data confidentiality takes a back seat.

According to the Raytheon Websense report, healthcare professionals "have an increased tendency to try and get around IT security policy in order to better serve their patients" and "up to 75 percent of hospital network traffic goes unmonitored by security solutions out of fear that improperly configured security measures or alarming false positives could dramatically increase the risk to patient health or well-being." 

"Outside of stock trading, I can't think of another industry where you have to err on the side of openness," says Bob Slocum, senior product marketing manager of data and endpoint security for Websense. Further, there is no other industry, he says, where an employee (like a doctor) can routinely trump a security policy.

The end result is that attackers are far more willing to invest in stealing medical records than healthcare institutions are willing to invest in protecting them from being stolen.

As the Raytheon Websense report references, the average healthcare organization only spends about 3 percent of its IT budget on security, even though HIMSS recommends they spend at least 10 percent. Bitsight reports that while healthcare has done a good job closing up those Heartbleed vulnerabilities (only 4.4 percent), it's still wide open to FREAK (43.4 %) and POODLE (73.5 %).

Conversely, attackers will bring their best tools to bear. According to Raytheon and Websense, healthcare organizations are four times as likely to be hit with advanced malware -- particularly the CryptoWall ransomware (450% likelier), Dyre Trojan (300% likelier), and stealthy Dropper (376% likelier), which opens backdoors and drops other assorted payloads.

Healthcare is also 14 times as likely to be hit by the Andromeda botnet -- which has a particularly stealthy loader with anti-VM and anti-debug capabilities that can stay silent for months before it communicates with its command and control server, according to Raytheon and Websense.

Slocum says that he expected the numbers to be bad, and but not quite as "astronomically bad" as they were.

Plus, while outside attackers barrage them with malware, medical institutions also have malicious insiders to worry about. According to a report released yesterday by Trend Micro, healthcare has a larger insider leak problem than any other sector, attributing 17.5% of its breaches over the past 10 years to it. Insider leaks were the primary source of identity theft cases (44.2%) and healthcare was hit harder by identity theft than any other sector, accounting for 29.8% of cases.

The Bitsight report has declared healthcare the second-worst industry performer in data security, ahead of only education. According to Trend Micro, more than one-quarter (26.9%) of the data breaches reported in the past 10 years were in the healthcare sector.

And it isn't only an American problem; as the Raytheon Websense report cites, the U.K.'s National Health Services has been fined £1 million for its data security transgressions.

Complexity contributes to the problem. Multiple hospitals, labs, imaging centers, and pharmacies in multiple locations share data and computing resources.

The complexity just increases as the early-adopting industry hooks more medical devices into the Internet of Things. As guests of today's Dark Reading Radio episode on "Fixing IoT Security" remarked, one of the challenges of the IoT is installing software security updates -- something that is infinitely more complicated when the device needing the update resides within a patient's body.

Slocum says he takes the issue to heart, being a diabetic himself, but that medical device manufacturers he's spoken to have been very proactive about security -- not only by inviting ethical hackers to try to break into their devices, but by securing their other systems extra carefully, knowing that any sort of breach would damage their brand reputation and thus people's trust in their devices.

Slocum says there's some reason for optimism. He says that IT leaders in healthcare oganizations have been "beating the drum" and asking their CEOs for cybersecurity funding for years, to no avail; but since the Anthem breach, the conversation has changed.

"I believe they're going to get more [money] and executive support," he says. He recommends that they direct some of these funds to more unified solutions that can manage complex environments and to better end user awareness training.

Sara Peters is Senior Editor at Dark Reading and formerly the editor-in-chief of Enterprise Efficiency. Prior that she was senior editor for the Computer Security Institute, writing and speaking about virtualization, identity management, cybersecurity law, and a myriad ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
<<   <   Page 2 / 2
lynnbr2
50%
50%
lynnbr2,
User Rank: Strategist
10/1/2015 | 1:22:21 PM
Re: A cost effective approach
I agree the article "perfectly focused the point," and it was in the very first sentence where Sara said that "healthcare not very willing to invest in defending it."

Look, if I'm the CIO or CISO and I go the CEO and say "the state of our security is an unknown-unknown" (to channel Don Rumsfeld), I'll likely be replaced in the next quarter after the CEO's executive search committee comes back with some candidates. Ok, suppose the CEO is a good guy, and allows the CISO to continue. (I'll defer the discussion of just how many CEOs are good guys to Matthew 19:24?) So next the CISO has to tell the CEO just how large a honeypot of $ he needs to secure things, and over what time period. Then the CEO has to get buy-in from the rest of the C-suite and the board. But time flies, and that money is spent and gone now, and regardless of whether the CISO squashed 15 vulns, 150 vulns, or 500 vulns, the state of security is still an unknown-unknown? Well, for sure the executive search committee is getting back in session. The CEO isn't ready yet to add this new, never ending, ever expanding cost into the companies' 10-K statements, when legal is telling him they're covered. One persons cost effective approach is another persons business tax.

 
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
10/11/2015 | 8:16:13 PM
Re: A cost effective approach
"Attackers are always looking for a cost effective approach."

Indeed, security research indicates that attackers -- like "defenders" -- are lazy, and constantly recycle code.  One security research company in Israel focuses on using predictive analytics to predict -- and defend against -- new attacks based upon old attacks and old malware and old software.
<<   <   Page 2 / 2
COVID-19: Latest Security News & Commentary
Dark Reading Staff 6/5/2020
How AI and Automation Can Help Bridge the Cybersecurity Talent Gap
Peter Barker, Chief Product Officer at ForgeRock,  6/1/2020
Cybersecurity Spending Hits 'Temporary Pause' Amid Pandemic
Kelly Jackson Higgins, Executive Editor at Dark Reading,  6/2/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: What? IT said I needed virus protection!
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-13890
PUBLISHED: 2020-06-06
The Neon theme 2.0 before 2020-06-03 for Bootstrap allows XSS via an Add Task Input operation in a dashboard.
CVE-2020-13889
PUBLISHED: 2020-06-06
showAlert() in the administration panel in Bludit 3.12.0 allows XSS.
CVE-2020-13881
PUBLISHED: 2020-06-06
In support.c in pam_tacplus 1.3.8 through 1.5.1, the TACACS+ shared secret gets logged via syslog if the DEBUG loglevel and journald are used.
CVE-2020-13883
PUBLISHED: 2020-06-06
In WSO2 API Manager 3.0.0 and earlier, WSO2 API Microgateway 2.2.0, and WSO2 IS as Key Manager 5.9.0 and earlier, Management Console allows XXE during addition or update of a Lifecycle.
CVE-2020-13871
PUBLISHED: 2020-06-06
SQLite 3.32.2 has a use-after-free in resetAccumulator in select.c because the parse tree rewrite for window functions is too late.