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.

Comments
Stolen Medical Data Is Now A Hot Commodity
Oldest First  |  Newest First  |  Threaded View
lynnbr2
50%
50%
lynnbr2,
User Rank: Strategist
10/14/2014 | 1:41:46 PM
The fun part
of this is that once something gets "posted" to your medical history, there is neither a mechanism to protest it nor to have it removed. It stays with you. And the major insurance companies have access to all of this to determine your rates, and even eligibilty, for various health and life insurance products.
Marilyn Cohodas
50%
50%
Marilyn Cohodas,
User Rank: Strategist
10/14/2014 | 2:41:14 PM
Re: The fun part
Several years ago a family member of mine requested a copy of a discharge report after a hospital stay and the report she received was someone else's health record. I would hope that those kinds of mistakes don't happen so much anymore. Am I being naive? 
ni@root
100%
0%
[email protected],
User Rank: Apprentice
10/14/2014 | 3:13:16 PM
Data Exposures and Butthurt
I spend a lot of time looking for sensitive data. I have found close to 40 different exposures over the last month or so. One thing I find is that some organizations get upset when one of the good members of the security community find something and report it to them. They use terms such as "illegally accessed" or "stole records" when in each case the access was 100% legal. They just happen to not be as competent in protecting their data as they should be.

Yesterday I set out to find another exposure and in less than an hour found medical records with full SSN. Possible 90k plus records exposed at one time or another. After the initial investigation on my part I will inform this company of the exposure (not breach) and cross fingers they won't get upset. This attitude needs to change.
Stratustician
50%
50%
Stratustician,
User Rank: Moderator
10/14/2014 | 4:06:11 PM
Re: The fun part
Sadly I think everyone still struggles with how do we properly share information between agencies (healthcare, insurance etc) and at the same time ensure that it is properly protected through technologies such as encryption etc. We can't expect health care practitioners to be responsible for ensuring patients information is protected (their jobs are obviously to focus on providing patient care), so we really need to better enforce controls for security teams involved with these agencies. The downside is that often there is lack of awareness and budget to properly protect these resources. There has to be a better way to create these systems moving forward.
Marilyn Cohodas
100%
0%
Marilyn Cohodas,
User Rank: Strategist
10/15/2014 | 9:58:30 AM
Re: The fun part
Ideally, these HIT systems should increase practitioneers' productivity, and free them from the drudgery of records management. But the learning curve is steep and frustrating. And the ROI doesn't happen quick enough, at least from the healthcare employee perspective. 
TubeLugs
50%
50%
TubeLugs,
User Rank: Apprentice
12/2/2014 | 10:21:25 PM
Balderdash
"We can't expect health care practitioners to be responsible for ensuring patients information is protected"

 

This statement is both false and dangerous. We expect bankers to perform their primary business function AND keep our PII safe. We expect retail establishments to run their business AND protect our data. Why should we expect less from a medical chain or office?


HCPs are the front line in collecting health data. OF COURSE we should expect them to ensure it is protected. If they are not held as part of the responsibility chain, they will do nothing to improve the horrid state of data security in medical practices.


 

Andrew Clyne

 

<[email protected]>
worldmoneylive
50%
50%
worldmoneylive,
User Rank: Apprentice
9/10/2015 | 12:52:58 PM
commodity market
U.S. labor market strengthening; imported inflation weak 


News
FluBot Malware's Rapid Spread May Soon Hit US Phones
Kelly Sheridan, Staff Editor, Dark Reading,  4/28/2021
Slideshows
7 Modern-Day Cybersecurity Realities
Steve Zurier, Contributing Writer,  4/30/2021
Commentary
How to Secure Employees' Home Wi-Fi Networks
Bert Kashyap, CEO and Co-Founder at SecureW2,  4/28/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-31793
PUBLISHED: 2021-05-06
An issue exists on NightOwl WDB-20-V2 WDB-20-V2_20190314 devices that allows an unauthenticated user to gain access to snapshots and video streams from the doorbell. The binary app offers a web server on port 80 that allows an unauthenticated user to take a snapshot from the doorbell camera via the ...
CVE-2021-31916
PUBLISHED: 2021-05-06
An out-of-bounds (OOB) memory write flaw was found in list_devices in drivers/md/dm-ioctl.c in the Multi-device driver module in the Linux kernel before 5.12. A bound check failure allows an attacker with special user (CAP_SYS_ADMIN) privilege to gain access to out-of-bounds memory leading to a syst...
CVE-2021-31918
PUBLISHED: 2021-05-06
A flaw was found in tripleo-ansible version as shipped in Red Hat Openstack 16.1. The Ansible log file is readable to all users during stack update and creation. The highest threat from this vulnerability is to data confidentiality.
CVE-2019-25043
PUBLISHED: 2021-05-06
ModSecurity 3.x before 3.0.4 mishandles key-value pair parsing, as demonstrated by a &quot;string index out of range&quot; error and worker-process crash for a &quot;Cookie: =abc&quot; header.
CVE-2020-18889
PUBLISHED: 2021-05-06
Cross Site Request Forgery (CSRF) vulnerability in puppyCMS v5.1 that can change the admin's password via /admin/settings.php.