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.

Comments
More Than 50% Of Biggest Holiday Retailers May Not Be PCI-Compliant
Newest First  |  Oldest First  |  Threaded View
<<   <   Page 2 / 2
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: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: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.
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: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.
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.
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.
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!)

<<   <   Page 2 / 2


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-23416
PUBLISHED: 2021-07-28
This affects all versions of package curly-bracket-parser. When used as a template library, it does not properly sanitize the user input.
CVE-2021-23417
PUBLISHED: 2021-07-28
All versions of package deepmergefn are vulnerable to Prototype Pollution via deepMerge function.
CVE-2021-23415
PUBLISHED: 2021-07-28
This affects the package elFinder.AspNet before 1.1.1. The user-controlled file name is not properly sanitized before it is used to create a file system path.
CVE-2020-4974
PUBLISHED: 2021-07-28
IBM Jazz Foundation products are vulnerable to server side request forgery (SSRF). This may allow an authenticated attacker to send unauthorized requests from the system, potentially leading to network enumeration or facilitating other attacks. IBM X-Force ID: 192434.
CVE-2020-5004
PUBLISHED: 2021-07-28
IBM Jazz Foundation products are vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 192957.