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.

Database Security
Authentication
Mobile
Privacy
Compliance
Careers and People
Identity & Access Management
Security Monitoring
Advanced Threats
Insider Threats
Vulnerability Management

Cloud

12/13/2019
09:00 AM
Jai Vijayan
Jai Vijayan
Slideshows
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
3 comments
Comment Now

Lessons Learned from 7 Big Breaches in 2019

Capital One, Macy's, FEMA, and others: key takeaways from the year's most notable breaches.
4 of 8

Third-Party Security Failures Can Hurt Organization: The American Medical Collection Agency (AMCA) When: Breach was disclosed in May 2019 Breach Details: In June, medical debt collection company AMCA notified two of its largest customers - Quest Diagnostics and LabCorp - about an unauthorized user accessing an AMCA system containing sensitive data on millions of their patients. Data, including Social Security numbers, bank account and credit information, and medical information belonging to some 11.9 million Quest patients and 7.7 million LabCorp patients were compromised in the breach. Since then several other healthcare entities that used AMCA for debt-collection purposes have disclosed being impacted in the same breach. In total, the incident impacted 21 healthcare organizations and at least 24.4 million individuals. AMCA filed for bankruptcy protection after some its customers sued the company. Lessons Learned: For Quest, LabCorp, and the other victims, the AMCA incident was a classic example of third-party risk. It was a reminder of the need for organizations to ensure that business partners and other third parties with whom they interact, follow security best practices. 'The challenge for enterprises is managing information about the security posture of their third parties,' said Matan Or-El, CEO of Panorays. 'Issues include suppliers who do not fix security issues in time, partners who receive data and do not protect it as they should, and partners and third parties who receive access to an enterprise's network but fail to protect that access in an appropriate way.' Image source: AMCA

Third-Party Security Failures Can Hurt

Organization: The American Medical Collection Agency (AMCA)

When: Breach was disclosed in May 2019

Breach Details: In June, medical debt collection company AMCA notified two of its largest customers - Quest Diagnostics and LabCorp - about an unauthorized user accessing an AMCA system containing sensitive data on millions of their patients. Data, including Social Security numbers, bank account and credit information, and medical information belonging to some 11.9 million Quest patients and 7.7 million LabCorp patients were compromised in the breach. Since then several other healthcare entities that used AMCA for debt-collection purposes have disclosed being impacted in the same breach. In total, the incident impacted 21 healthcare organizations and at least 24.4 million individuals. AMCA filed for bankruptcy protection after some its customers sued the company.

Lessons Learned: For Quest, LabCorp, and the other victims, the AMCA incident was a classic example of third-party risk. It was a reminder of the need for organizations to ensure that business partners and other third parties with whom they interact, follow security best practices.

"The challenge for enterprises is managing information about the security posture of their third parties," said Matan Or-El, CEO of Panorays. "Issues include suppliers who do not fix security issues in time, partners who receive data and do not protect it as they should, and partners and third parties who receive access to an enterprise's network but fail to protect that access in an appropriate way."

Image source: AMCA

4 of 8
Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
amdenver
100%
0%
amdenver,
 User Rank: Apprentice
1/26/2020 | 8:14:03 PM
Great Concise Article
Author has done an excellent job of capturing the main avenues of getting breached with very good case selection. Great succinct read. Thanks for the time and effort that you put into this worth. Best Regards.
Matt Middleton-Leal Netwrix
50%
50%
Matt Middleton-Leal Netwrix,
 User Rank: Apprentice
12/20/2019 | 9:37:05 AM
Cloud data security is a huge concern
Great article. We can all learn from the mistakes made in these big breaches. In particular, I agree that there is continued concern about the risks of cloud storage. In a recent survey, 48% of organizations that store sensitive data in the cloud would consider moving that data back on premises. To best secure data in the cloud, it's important to know just how much data you have, who has access to it and which data is most critical in your IT environment, so you can prioritize your security efforts.
albertscales
0%
100%
albertscales,
 User Rank: Apprentice
12/16/2019 | 9:05:30 AM
informative
Nice article
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-29741
PUBLISHED: 2021-08-02
IBM AIX 7.1, 7.2, and VIOS 3.1 could allow a local user to exploit a vulnerability in Korn Shell (ksh) to gain root privileges. IBM X-Force ID: 201478.
CVE-2021-37840
PUBLISHED: 2021-08-02
aaPanel through 6.8.12 allows Cross-Site WebSocket Hijacking (CSWH) involving OS commands within WebSocket messages at a ws:// URL for /webssh (the victim must have configured Terminal with at least one host). Successful exploitation depends on the browser used by a potential victim (e.g., exploitat...
CVE-2021-20332
PUBLISHED: 2021-08-02
Specific MongoDB Rust Driver versions can include credentials used by the connection pool to authenticate connections in the monitoring event that is emitted when the pool is created. The user's logging infrastructure could then potentially ingest these events and unexpectedly leak the credentials. ...
CVE-2021-37160
PUBLISHED: 2021-08-02
A firmware validation issue was discovered in HMI3 Control Panel in Swisslog Healthcare Nexus Panel operated by released versions of software before Nexus Software 7.2.5.7. There is no firmware validation (e.g., cryptographic signature validation) during a File Upload for a firmware update.
CVE-2021-37161
PUBLISHED: 2021-08-02
A buffer overflow issue was discovered in the HMI3 Control Panel contained within the Swisslog Healthcare Nexus Panel, operated by released versions of software before Nexus Software 7.2.5.7. A buffer overflow allows an attacker to overwrite an internal queue data structure and can lead to remote co...