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
Threaded  |  Newest First  |  Oldest First
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...