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.

Vulnerabilities / Threats

TJX Settles With Banks for $41 Million

More than 100 million account records were breached, retail giant reveals

TJX Companies has reached an agreement with Visa USA by which it will establish a $40.9 million fund for banks whose credit cards were exposed in the retailer's mammoth security breach earlier this year.

The settlement is TJX's second in a series of lawsuits arising from the breach, in which years of credit card records were exposed. In September, TJX agreed to pay $7 million in store vouchers (and later, cash) to customers who had been affected. The company also promised customers a discount sale. (See TJX Proposes to Settle Customer Lawsuit for $6.5M.)

The $41 million settlement is contingent on acceptance by at least 80 percent of the banks involved. If they agree to the settlement, the banks must also agree not to pursue further litigation against TJX.

"We believe this settlement agreement provides a fair resolution of these issues, and look forward to a high issuer acceptance of the proposal," said Carol Meyrowitz, president and CEO of the TJX Companies. "At TJX, we have learned a great deal about the risks of cyber attacks and have responded aggressively to take our own security to even higher levels. We also have learned about the heightened security risks that exist across the entire U.S. retail and banking industries as a result of today’s high-tech criminals."

In total, TJX has agreed to pay out less than $50 million over the breach, which exposed at least 45.7 million credit card records. During the trial, the banks estimated that the exposure was closer to 100 million records. The retailer has seen little financial impact from the debacle, and today posted a quarterly dividend of nine cents per share on its common stock.

Observers in the security industry say they aren't entirely satisfied by the settlements, which haven't forced TJX to give details on the causes and sources of the breach.

"Only the banks and credit card companies can determine if TJX’s offer of a $40.9 million settlement for its data breach is adequate," says Adrian Lane, CTO of security company IPLocks. "However, what should be required as part of the settlement is a case study of exactly what happened. Here is an opportunity for financial institutions to step in and help prevent this from happening to other retailers. The cost is almost nothing, and there would be a clear benefit to the retail industry and, ultimately, consumers.

"Data breaches are a problem that all companies potentially face. But when a company is breached, responses seem to fall into one of two responses: non-disclosure or non-informative press spin," Lane says. "They either do not disclose publicly, or if obligated in some way, we get the ‘we are deeply concerned, but we are on top of it’ response from press or legal teams. Security through anonymity is what this is, and it does not do anyone a lot of good."

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Tim Wilson is Editor in Chief and co-founder of Dark Reading.com, UBM Tech's online community for information security professionals. He is responsible for managing the site, assigning and editing content, and writing breaking news stories. Wilson has been recognized as one ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
How to Better Secure Your Microsoft 365 Environment
Kelly Sheridan, Staff Editor, Dark Reading,  1/25/2021
Attackers Leave Stolen Credentials Searchable on Google
Kelly Sheridan, Staff Editor, Dark Reading,  1/21/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2020: The Year in Security
Download this Tech Digest for a look at the biggest security stories that - so far - have shaped a very strange and stressful year.
Flash Poll
Assessing Cybersecurity Risk in Today's Enterprises
Assessing Cybersecurity Risk in Today's Enterprises
COVID-19 has created a new IT paradigm in the enterprise -- and a new level of cybersecurity risk. This report offers a look at how enterprises are assessing and managing cyber-risk under the new normal.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-3142
PUBLISHED: 2021-01-28
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2020-35128. Reason: This candidate is a reservation duplicate of CVE-2020-35128. Notes: All CVE users should reference CVE-2020-35128 instead of this candidate. All references and descriptions in this candidate have been removed to preve...
CVE-2020-35124
PUBLISHED: 2021-01-28
A cross-site scripting (XSS) vulnerability in the assets component of Mautic before 3.2.4 allows remote attackers to inject executable JavaScript through the Referer header of asset downloads.
CVE-2020-25782
PUBLISHED: 2021-01-28
An issue was discovered on Accfly Wireless Security IR Camera 720P System with software versions v3.10.73 through v4.15.77. There is an unauthenticated stack-based buffer overflow in the function CNetClientManage::ServerIP_Proto_Set during incoming message handling.
CVE-2020-25783
PUBLISHED: 2021-01-28
An issue was discovered on Accfly Wireless Security IR Camera System 720P with software versions v3.10.73 through v4.15.77. There is an unauthenticated heap-based buffer overflow in the function CNetClientTalk::OprMsg during incoming message handling.
CVE-2020-25784
PUBLISHED: 2021-01-28
An issue was discovered on Accfly Wireless Security IR Camera System 720P with software versions v3.10.73 through v4.15.77. There is an unauthenticated stack-based buffer overflow in the function CNetClientGuard::SubOprMsg during incoming message handling.