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.

Database Security
Authentication
Mobile
Privacy
Compliance
Careers and People
Identity & Access Management
Security Monitoring
Advanced Threats
Insider Threats
Vulnerability Management
Comments
More Than 50% Of Biggest Holiday Retailers May Not Be PCI-Compliant
Threaded  |  Newest First  |  Oldest First
Joe Stanganelli
50%
50%
Joe Stanganelli,
 User Rank: Ninja
12/22/2016 | 6:55:40 PM
TJX -- have we not learned?
There's an old adage:

The fool never learns.

The smart man learns from his own mistakes.

The wise man learns from the others' mistakes.

Its applicability here: After the TJX breach years ago, which happened because of the failure to be compliant with the spirit of PCI-DSS and best practices related thereto, this is inexcusable.

For these reasons, I tend to pay with cash almost always.  (And ESPECIALLY this time of year!)

RetiredUser
50%
50%
RetiredUser,
 User Rank: Ninja
12/23/2016 | 2:51:32 AM
Re: TJX -- have we not learned?
Not paying with Bitcoin, Joe? :-)

It's tough knowing what we know and then going out and having to decide how we pay for things.  Personally, while I do try to use caution, I also case the hardware and make eye contact with my clerks when paying with credit.

The question I always ask here is "Who do we hold accountable?"  The vendors for not better promoting secure practices with their hardware?  The companies for not hiring good InfoSec?  Or InfoSec for not getting the message out there better?

Sometimes it feels like we have to have more than regulatory and legal shackles to force security to happen.  Perhaps a cease-and-desist order to close a business that doesn't pass should be implemented.  How many of those will be issued before everyone starts passing their compliance audits.

That this happens again and again is almost rediculous.
Dr.T
0%
100%
Dr.T,
 User Rank: Ninja
12/26/2016 | 8:24:36 PM
Re: TJX -- have we not learned?
"Who do we hold accountable"

This is a good question. Unless we put bad guys under enough pressure this will most likely never end.
Dr.T
0%
100%
Dr.T,
 User Rank: Ninja
12/26/2016 | 8:31:20 PM
Re: TJX -- have we not learned?
"Sometimes it feels like we have to have more than regulatory and legal shackles to force security to happen."

That is an important point, security is expensive, without regulation it is not happening, especially in IoT.
Joe Stanganelli
50%
50%
Joe Stanganelli,
 User Rank: Ninja
12/31/2016 | 12:34:38 PM
Re: TJX -- have we not learned?
With or without regulation, security measures will happen if there is a notable direct benefit or detriment involved to the company or the customer.

When it comes to consumer IoT, however, the detriment to consumers of compromised devices is minimal if not outright nil because their devices will still fundamentally work.  (The fridge will still be a fridge -- even while it acts as a botnet zombie to take down a web service.)
Joe Stanganelli
50%
50%
Joe Stanganelli,
 User Rank: Ninja
12/31/2016 | 12:37:25 PM
Re: TJX -- have we not learned?
> Not paying with Bitcoin, Joe? :-)

The stores in my area don't take them.  ;)
Dr.T
0%
100%
Dr.T,
 User Rank: Ninja
12/26/2016 | 8:20:27 PM
Re: TJX -- have we not learned?
"The wise man learns from the others' mistakes."
Agree. Wiser man put his learning into action.

 
Dr.T
0%
100%
Dr.T,
 User Rank: Ninja
12/26/2016 | 8:21:54 PM
Re: TJX -- have we not learned?
"I tend to pay with cash almost always."

This is a good idea. What I hate is the changes I get back, becomes harder to deal with after a while.
ClarenceR927
100%
0%
ClarenceR927,
 User Rank: Strategist
12/23/2016 | 10:49:13 AM
compliance != secure
Having consulted at 4 very large and well known retailers (and countless smaller ones) I can assure you that compliance does not equal secure. Management has always been very concerned about PCI compliance but not really willing to do what is necessary to be secure.  Good enough to pass the audit is good enough. I made things as much better as management was willing to go but none of them is really as secure as we should expect and PCI is mostly window dressing.

When you use your credit card you are simply a wildebeest on the plains. If the lion chooses you, you are as good as eaten.
Dr.T
0%
100%
Dr.T,
 User Rank: Ninja
12/26/2016 | 8:29:01 PM
Re: compliance != secure
"Good enough to pass the audit is good enough."

This is actually a good point. For me passing audit should be resulting into a good level of security measures in the environment.   
Dr.T
0%
100%
Dr.T,
 User Rank: Ninja
12/26/2016 | 8:33:34 PM
Re: compliance != secure
"When you use your credit card you are simply a wildebeest on the plains."

It makes sense but you can secure it, as Apple Pay does not share any personal info with the merchant it may be better than a credit card processing.
Joe Stanganelli
50%
50%
Joe Stanganelli,
 User Rank: Ninja
12/31/2016 | 12:39:17 PM
Re: compliance != secure
@Clarence: This is what I preach all the time in my own consulting, too.  Compliance, security, and data privacy are like slightly overlapping circles on a Venn diagram.  One does not equal the other; they are each merely components in the grander "data protection" scheme.
Dr.T
0%
100%
Dr.T,
 User Rank: Ninja
12/26/2016 | 8:19:02 PM
No security breach yet?
I would wait for a few years to see if there was any security breach during this holiday season, it seem that is how it works these days.
Joe Stanganelli
50%
50%
Joe Stanganelli,
 User Rank: Ninja
12/31/2016 | 12:40:54 PM
Re: No security breach yet?
@Dr.T: Target found out pretty quickly (at least, they didn't take "a few years" to learn about their own security breach) when they were hacked.  I think major retailers are more on the ball these days -- at least when it comes to after-the-fact detection (if nothing else).
Dr.T
0%
100%
Dr.T,
 User Rank: Ninja
12/26/2016 | 8:22:20 PM
D?
 

I really wonder what D stands for in this case, is it like no firewall in the perimeter?
Dr.T
0%
100%
Dr.T,
 User Rank: Ninja
12/26/2016 | 8:29:59 PM
Re: scalp psoriasis
I agree, quite informative article and covers very important subject.
Dr.T
0%
100%
Dr.T,
 User Rank: Ninja
12/26/2016 | 8:34:37 PM
PCI
Better to outsource this responsibility to a third-party, very expensive to secure and insure. 
sussanbetcher
50%
50%
sussanbetcher,
 User Rank: Apprentice
12/30/2016 | 4:35:37 AM
true
private louvre tour

That sounds very relevant. Thanks for sharing the news about retailers. Its true that, because no serious breaches have been reported it doesn't mean that we all may not collectively wake up with a security hangover.


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-36702
PUBLISHED: 2021-08-03
The "content" field in the "regular post" page of the "add content" menu under "dashboard" in htmly 2.8.1 has a storage cross site scripting (XSS) vulnerability. It allows remote attackers to send authenticated post-http requests to add / content and inject ar...
CVE-2021-36703
PUBLISHED: 2021-08-03
The "blog title" field in the "Settings" menu "config" page of "dashboard" in htmly 2.8.1 has a storage cross site scripting (XSS) vulnerability. It allows remote attackers to send an authenticated post HTTP request to admin/config and inject arbitrary web scr...
CVE-2021-30541
PUBLISHED: 2021-08-03
Use after free in V8 in Google Chrome prior to 91.0.4472.164 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
CVE-2021-30559
PUBLISHED: 2021-08-03
Out of bounds write in ANGLE in Google Chrome prior to 91.0.4472.164 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
CVE-2021-30560
PUBLISHED: 2021-08-03
Use after free in Blink XSLT in Google Chrome prior to 91.0.4472.164 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.