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.

Cloud

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

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
Oldest First  |  Newest First  |  Threaded View
albertscales
0%
100%
albertscales,
User Rank: Apprentice
12/16/2019 | 9:05:30 AM
informative
Nice article
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.
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.
Stop Defending Everything
Kevin Kurzawa, Senior Information Security Auditor,  2/12/2020
Small Business Security: 5 Tips on How and Where to Start
Mike Puglia, Chief Strategy Officer at Kaseya,  2/13/2020
Architectural Analysis IDs 78 Specific Risks in Machine-Learning Systems
Jai Vijayan, Contributing Writer,  2/13/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
How Enterprises Are Developing and Maintaining Secure Applications
How Enterprises Are Developing and Maintaining Secure Applications
The concept of application security is well known, but application security testing and remediation processes remain unbalanced. Most organizations are confident in their approach to AppSec, although others seem to have no approach at all. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-7050
PUBLISHED: 2020-02-15
Codologic Codoforum through 4.8.4 allows a DOM-based XSS. While creating a new topic as a normal user, it is possible to add a poll that is automatically loaded in the DOM once the thread/topic is opened. Because session cookies lack the HttpOnly flag, it is possible to steal authentication cookies ...
CVE-2019-13965
PUBLISHED: 2020-02-14
Because of a lack of sanitization around error messages, multiple Reflective XSS issues exist in iTop through 2.6.0 via the param_file parameter to webservices/export.php, webservices/cron.php, or env-production/itop-backup/backup.php. By default, any XSS sent to the administrator can be transformed...
CVE-2019-13966
PUBLISHED: 2020-02-14
In iTop through 2.6.0, an XSS payload can be delivered in certain fields (such as icon) of the XML file used to build the dashboard. This is similar to CVE-2015-6544 (which is only about the dashboard title).
CVE-2019-13967
PUBLISHED: 2020-02-14
iTop 2.2.0 through 2.6.0 allows remote attackers to cause a denial of service (application outage) via many requests to launch a compile operation. The requests use the pages/exec.php?exec_env=production&exec_module=itop-hub-connector&exec_page=ajax.php&operation=compile URI. This only a...
CVE-2019-15592
PUBLISHED: 2020-02-14
GitLab 12.2.2 and below contains a security vulnerability that allows a guest user in a private project to see the merge request ID associated to an issue via the activity timeline.