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
Study: Chip-&-PIN Won't Cure Retail Breaches
Newest First  |  Oldest First  |  Threaded View
Kelly Jackson Higgins
50%
50%
Kelly Jackson Higgins,
User Rank: Strategist
11/1/2014 | 7:55:51 PM
Re: A partial solution
I think consumers often miss or are in denial that they ultimately do pay for a data breach with higher prices at the victimized retailer, increased fees at the bank, etc. That fact really should be part of the disclosure process.
Ulf Mattsson
50%
50%
Ulf Mattsson,
User Rank: Moderator
11/1/2014 | 3:02:01 PM
EMV chip technology does not protect
I agree "That's because the total volume of card-not-present transactions are rising, and the bad guys will go after the easier targets as PoS systems get better locked down".

My main concern is that "EMV chip technology does not protect against malware attacks like those we have been reading about in the news, nor does it prevent card-not-present attacks" according to the new head of the PCI Council.

I think that more modern cost effective data protection, like data tokenization, should be used for all sensitive data, including personal data.

Recent studies reported that data tokenization can cut security incidents by 50 % compared to use of encryption.

I think it is time to secure the sensitive data in the entire data flow with modern approaches.

Ulf Mattsson, CTO Protegrity
Ed Telders
50%
50%
Ed Telders,
User Rank: Apprentice
10/31/2014 | 5:14:31 PM
A partial solution
The roll out of Chip and Pin will certainly reduce some risks.  But as always there is that tendency to think of these advances as a silver bullet.  Well unfortunately you are quite right, the CNP will continue to increase, particularly for the "smaller transaction" where the risk for the retailer would seems smaller, but as an aggregate, it will be a lot of fraud.  Also don't forget that getting a card number is not difficult outside of the retailer's environment.  I participated in an investigation where a malicious actor was conducting a very effective method of identifying valid card numbers by simply calling the card provider with a retailer's store identifier (easily obtained), used a phone spoofing technique to make the call appear to come from the "800" number of the retailer's PBX system, and conducted what are called "Zero-Auth" transactions.  That kind of transaction essentially asks the card provider to validate that the card number is a valid card number.  The malicious actor had thousands of valid card numbers in just a few minutes as a result.  With social media sources and all of the "big data" that is available it doesn't take long to associate a valid card with a name to use for CNP transactions.  None of that kind of attack even touches the retailer directly, and consequently the retailer is not actually a victim of the attack, nor is it a breach since it did not involve the retailer's systems at all.  The only victims are all of us collectively since even if we aren't directly involved, all the expenses related to card fraud eventually gets paid for by increasing fees and costs as these losses are recuperated by the retailers, card processing companies, and of course the banks.  The consumer pays the ultimate price for all of this.  Nonetheless, the push for Chip and Pin is a welcome direction.


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
How Enterprises Are Assessing Cybersecurity Risk in Today's Environment
The adoption of cloud services spurred by the COVID-19 pandemic has resulted in pressure on cyber-risk professionals to focus on vulnerabilities and new exposures that stem from pandemic-driven changes. Many cybersecurity pros expect fundamental, long-term changes to their organization's computing and data security due to the shift to more remote work and accelerated cloud adoption. Download this report from Dark Reading to learn more about their challenges and concerns.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-4034
PUBLISHED: 2022-01-28
A local privilege escalation vulnerability was found on polkit's pkexec utility. The pkexec application is a setuid tool designed to allow unprivileged users to run commands as privileged users according predefined policies. The current version of pkexec doesn't handle the calling parameters count c...
CVE-2021-40416
PUBLISHED: 2022-01-28
An incorrect default permission vulnerability exists in the cgiserver.cgi cgi_check_ability functionality of reolink RLC-410W v3.0.0.136_20121102. All the Get APIs that are not included in cgi_check_ability are already executable by any logged-in users. An attacker can send an HTTP request to trigge...
CVE-2021-40419
PUBLISHED: 2022-01-28
A firmware update vulnerability exists in the 'factory' binary of reolink RLC-410W v3.0.0.136_20121102. A specially-crafted series of network requests can lead to arbitrary firmware update. An attacker can send a sequence of requests to trigger this vulnerability.
CVE-2021-40423
PUBLISHED: 2022-01-28
A denial of service vulnerability exists in the cgiserver.cgi API command parser functionality of Reolink RLC-410W v3.0.0.136_20121102. A specially-crafted series of HTTP requests can lead to denial of service. An attacker can send an HTTP request to trigger this vulnerability.
CVE-2021-44463
PUBLISHED: 2022-01-28
Missing DLLs, if replaced by an insider, could allow an attacker to achieve local privilege escalation on the DeltaV Distributed Control System Controllers and Workstations (All versions) when some DeltaV services are started.