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

Visa Gave TJX a Pass on PCI in 2005

Retailer got some slack on security compliance - and got hacked in the interim

The comedy of errors that led to TJX Companies' loss of an estimated 94.7 million credit card records isn't very funny. But as the puzzle pieces come together, it is amazing to see how many things went wrong.

Less than two weeks ago, court documents revealed that when TJX was first hacked back in 2005, it had failed to meet nine of the 12 security controls specified by the Payment Card Industry's Data Security Standard, the compliance guidelines for maintaining credit card data. (See Huge Breach Causes Little Pain at TJX.)

On Friday, a closer look at those documents revealed that Visa knew about TJX's compliance problems -- and agreed to give the retailer an extension on its PCI project until 2009.

According to a report, the credit card giant cut TJX some slack in 2005, agreeing not to impose fines on the retail giant or its official credit card processor, Fifth Third Bank, as long as they continued to "diligently pursue remediation efforts." The letter agrees to suspend fines until Dec. 31, 2008.

Unfortunately, the Dec. 29, 2005, letter from Visa arrived months after hackers had already broken into TJX systems and begun systematically sucking out credit card information from all of TJX's customers.

Visa did eventually levy $880,000 in fines on Fifth Third Bank due to TJX's sloppy compliance effort -- but not until this summer, when the horse was already out of the barn.

— Tim Wilson, Site Editor, Dark Reading

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
Cybersecurity Industry: It's Time to Stop the Victim Blame Game
Jessica Smith, Senior Vice President, The Crypsis Group,  2/25/2020
Google Adds More Security Features Via Chronicle Division
Robert Lemos, Contributing Writer,  2/25/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
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-9431
PUBLISHED: 2020-02-27
In Wireshark 3.2.0 to 3.2.1, 3.0.0 to 3.0.8, and 2.6.0 to 2.6.14, the LTE RRC dissector could leak memory. This was addressed in epan/dissectors/packet-lte-rrc.c by adjusting certain append operations.
CVE-2020-9432
PUBLISHED: 2020-02-27
openssl_x509_check_host in lua-openssl 0.7.7-1 mishandles X.509 certificate validation because it uses lua_pushboolean for certain non-boolean return values.
CVE-2020-9433
PUBLISHED: 2020-02-27
openssl_x509_check_email in lua-openssl 0.7.7-1 mishandles X.509 certificate validation because it uses lua_pushboolean for certain non-boolean return values.
CVE-2020-9434
PUBLISHED: 2020-02-27
openssl_x509_check_ip_asc in lua-openssl 0.7.7-1 mishandles X.509 certificate validation because it uses lua_pushboolean for certain non-boolean return values.
CVE-2020-6383
PUBLISHED: 2020-02-27
Type confusion in V8 in Google Chrome prior to 80.0.3987.116 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.