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.

Risk

9/28/2007
12:25 PM
Keith Ferrell
Keith Ferrell
Commentary
50%
50%

No Excuse: Security Lessons From T.J. MAXX Data Breach

Maybe the company should change its name to T.J. LAX -- lax security practices let the hacked retailer's data breach go from bad to worse to bad beyond belief while nobody did anything to remedy the situation.

Maybe the company should change its name to T.J. LAX -- lax security practices let the hacked retailer's data breach go from bad to worse to bad beyond belief while nobody did anything to remedy the situation.That's the finding of a Canadian investigation into T.J. MAXX parent company TJX and its security procedures -- or lack of them -- that let a data breach persist for well over a year, with customer records compromised throughout that time.

The small to midsized business security lessons to be learned? The ones you probably already know. Among the investigators' findings:

Watch for wireless weakspots: Indications are that the company breach may have taken place via insecure wireless networks at T.J. MAXX retailers. Any entry into your network is enough to compromise everything.

Upgrade promptly and efficiently: TJX took two years to convert its systems from weak to strong encryption. That's far too long -- more than long enough for two years' or so worth of customer data to be grabbed, in fact.

Systems exist to be monitored: Better monitoring -- i.e., constant, thorough, aggressive -- would have alerted the company to the breach sooner.

Acquire only the information you need and get rid of it when you're done: MAXX was acquiring driver's license numbers when refunding non-receipted items. That's an unnecessary data-get -- and exposed another customer record to hacking. Take only the information a transaction requires, and retain it only as long as your business and appropriate compliance/regulatory rules require.

Industry standards exist for industry reasons: Incredibly, the company was processing millions of credit card transactions without adhering to Payment Card Industry (PCI) standards.

Every one of these lapses was easily remedied, but more than that, every one of them was a breach of good business practice as well as good data security practice.

Take a look at your business with the lessons of T.J. LAX, uh, MAXX in mind.

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/14/2020
Lock-Pickers Face an Uncertain Future Online
Seth Rosenblatt, Contributing Writer,  8/10/2020
Hacking It as a CISO: Advice for Security Leadership
Kelly Sheridan, Staff Editor, Dark Reading,  8/10/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
7 New Cybersecurity Vulnerabilities That Could Put Your Enterprise at Risk
In this Dark Reading Tech Digest, we look at the ways security researchers and ethical hackers find critical vulnerabilities and offer insights into how you can fix them before attackers can exploit them.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-17475
PUBLISHED: 2020-08-14
Lack of authentication in the network relays used in MEGVII Koala 2.9.1-c3s allows attackers to grant physical access to anyone by sending packet data to UDP port 5000.
CVE-2020-0255
PUBLISHED: 2020-08-14
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2020-10751. Reason: This candidate is a duplicate of CVE-2020-10751. Notes: All CVE users should reference CVE-2020-10751 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidenta...
CVE-2020-14353
PUBLISHED: 2020-08-14
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2017-18270. Reason: This candidate is a duplicate of CVE-2017-18270. Notes: All CVE users should reference CVE-2017-18270 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidenta...
CVE-2020-17464
PUBLISHED: 2020-08-14
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.
CVE-2020-17473
PUBLISHED: 2020-08-14
Lack of mutual authentication in ZKTeco FaceDepot 7B 1.0.213 and ZKBiosecurity Server 1.0.0_20190723 allows an attacker to obtain a long-lasting token by impersonating the server.