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.

Attacks/Breaches

1/15/2020
06:00 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
100%
0%

2017 Data Breach Will Cost Equifax at Least $1.38 Billion

Company agrees to set aside a minimum of $380.5 million as breach compensation and spend another $1 billion on transforming its information security over the next five years. The 147 million US consumers affected by the breach have one week from today to file a claim.

The final minimum tab for Equifax's failure to patch a known web application security flaw—that later proved to be the root cause of the company's disastrous data breach in 2017—is over $1.38 billion.

The US District Court for the Northern District of Georgia Monday granted final approval of a settlement arrived at last July between the Federal Trade Commission and Equifax. Under the settlement, Equifax has agreed to set aside at least $380.5 million to settle claims related to its 2017 breach. The company has also agreed to spend at least $1 billion on information security and related technologies over a period of five years.

Personal data, including Social Security Numbers belonging to some 147 million US consumers was compromised in the breach. Equifax has blamed the incident on a buggy component in the open-source Apache Struts framework for which a patch was available at the time of the breach.

Money from the $380.5 million fund will be used to pay for credit monitoring services and compensation of up to $20,000 to individuals who can show documented out-of-pocket expenses directly related to the breach. The court-approved settlement allows individuals to claim up to 20 hours—at $25 per hour—for any time they might have had to spend taking preventative measures to protect their data against fraud and misuse following the breach. Up to 10 of those hours can be self-certified and requires no documentation.

Equifax will also provide up to four years of free three-bureau credit monitoring and identify protection services to victims of the data breach. In addition, the company will provide another six years of its own credit monitoring and identity protection service for free. Victims who were legal minors at the time of the breach are eligible for a total of 18 years of free credit monitoring.

Substantial as the costs are for Equifax, they could go even higher. The settlement for instance requires Equifax to set aside an additional $125 million in the event the $380.5 million fund proves insufficient to pay all claims. On top of that, the costs for the six years of additional credit monitoring that Equifax is required to provide under the settlement are not part of the $380.2 million fund. In approving the settlement, the court estimated that the market value of the free credit monitoring service—if all 147 million victims sign up for it—at an additional $2 billion for Equifax.

"This settlement is the largest and most comprehensive recovery in a data breach case in U.S. history by several orders of magnitude," District Judge Thomas Thrash, Jr. wrote. "The minimum cost to Equifax of the settlement is $1.38 billion and could be more, depending on the cost of complying with the injunctive relief," and other measures, he wrote.

Rui Lopes, sales engineering and technical support director at Panda Security says the security breach suffered by Equifax in 2017 was one of the biggest data in history. The big question is whether it could have been prevented. "And the answer is simply 'yes,'" Lopes says. "Equifax left the door open to cybercriminals by not updating an open-source web application development framework."

However, Jack Mannino, CEO at nVisium says what the incident really highlights, is the difficulty involved in running a security program at scale, especially for those under constant attack.

Though there were demonstrated gaps in security monitoring and secure development that contributed to the breach, the security issues at Equifax were not unique to them he says.  "Most organizations commonly struggle with keeping software libraries and dependencies up to date," Mannino says. "However, given the value of the data they protect, it demonstrates that there are real consequences to these events.”  

Equifax's Data Breach Settlement Website and settlement notice contains all details about the final settlement and the reliefs and benefits available under it. Consumers have until Jan. 22, 2020 to file a claim.

Related Content:

Check out The Edge, Dark Reading's new section for features, threat data, and in-depth perspectives. Today's top story: "How to Keep Security on Life Support After Software End-of-Life."

Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Why Vulnerable Code Is Shipped Knowingly
Chris Eng, Chief Research Officer, Veracode,  11/30/2020
Inside North Korea's Rapid Evolution to Cyber Superpower
Kelly Sheridan, Staff Editor, Dark Reading,  12/1/2020
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-2020-29565
PUBLISHED: 2020-12-04
An issue was discovered in OpenStack Horizon before 15.3.2, 16.x before 16.2.1, 17.x and 18.x before 18.3.3, 18.4.x, and 18.5.x. There is a lack of validation of the "next" parameter, which would allow someone to supply a malicious URL in Horizon that can cause an automatic redirect to the...
CVE-2020-5675
PUBLISHED: 2020-12-04
Out-of-bounds read issue in GT21 model of GOT2000 series (GT2107-WTBD all versions, GT2107-WTSD all versions, GT2104-RTBD all versions, GT2104-PMBD all versions, and GT2103-PMBD all versions), GS21 model of GOT series (GS2110-WTBD all versions and GS2107-WTBD all versions), and Tension Controller LE...
CVE-2020-29562
PUBLISHED: 2020-12-04
The iconv function in the GNU C Library (aka glibc or libc6) 2.30 to 2.32, when converting UCS4 text containing an irreversible character, fails an assertion in the code path and aborts the program, potentially resulting in a denial of service.
CVE-2020-28916
PUBLISHED: 2020-12-04
hw/net/e1000e_core.c in QEMU 5.0.0 has an infinite loop via an RX descriptor with a NULL buffer address.
CVE-2020-29561
PUBLISHED: 2020-12-04
An issue was discovered in SonicBOOM riscv-boom 3.0.0. For LR, it does not avoid acquiring a reservation in the case where a load translates successfully but still generates an exception.