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
Hilton Data Breach Focuses Attention On Growing POS Malware Threat
Newest First  |  Oldest First  |  Threaded View
Page 1 / 2   >   >>
Joe Stanganelli
Joe Stanganelli,
User Rank: Ninja
12/1/2015 | 8:16:17 AM
Re: POS Exploitation
Indeed.  I recently gave a talk on cyber insurance and cyber liability issues at MIT, and one of the primary problems we're seeing is that whereas enterprise is getting on board, SMEs feel priced out of the cyber insurance market or otherwise feel that it is inaccessible -- simply because of its complexity.  Alas, SMEs are the ones most deeply impacted by a data loss or data breach.
Joe Stanganelli
Joe Stanganelli,
User Rank: Ninja
11/29/2015 | 8:05:55 PM
Re: POS
A simple little one-sheet instruction manual, or email, or pop-up when paying a bill online, or whatnot, could go a long way in educating customers.
Joe Stanganelli
Joe Stanganelli,
User Rank: Ninja
11/29/2015 | 8:04:25 PM
Re: Dumb POS
@Dr. T: Indeed, going back to the old cash registers would certainly make things more secure -- but then would be an obstacle to data collection.

The real problem, typically, is infrastructure.  The Target hack, for instance, was made possible because of the fact that the vendor's HVAC was connected to the same infrastructure as the POS systems were.
Joe Stanganelli
Joe Stanganelli,
User Rank: Ninja
11/29/2015 | 8:02:20 PM
Re: POS
Apple Pay and Google Pay are not inherently more secure; they just have different security vulnerabilites than EMV (or, for that matter, black-stripe cards).  Lose your device and you're potentially screwed (especially what with easily hackable fingerprint biometrics).  And there may still be viable MitM attacks.
RyanSepe
RyanSepe,
User Rank: Ninja
11/29/2015 | 5:01:10 PM
Re: POS
I've heard some companies that have Apple Pay capabilities ready are not necessarily always active.

IE: stores can use Apple Pay but have yet to set it up. Can anyone add to this?
RyanSepe
RyanSepe,
User Rank: Ninja
11/29/2015 | 4:59:27 PM
Re: POS Exploitation
@Joe: That's a little brazen on the CIO's part.

And yes it could be part of design...hopefully companies that go down this road have good cyber security insurance and their breach falls under the terms of their policy.
RyanSepe
RyanSepe,
User Rank: Ninja
11/29/2015 | 4:56:34 PM
Re: POS
@Joe. Agreed. I'm not even sure what that might look like in terms of approach. I envision similar to when Apple is teaching people how to use iCloud or BestBuy holds a tech learning session (etc) but instead with EMV? 
Dr.T
Dr.T,
User Rank: Ninja
11/29/2015 | 12:03:20 PM
Re: POS
I hear you, I would say Everybody should be equally responsible credit card company, bank and retail delivery company has to be equally responsible, that would take us to Apple Pay and we will have less troubles.
Dr.T
Dr.T,
User Rank: Ninja
11/29/2015 | 12:01:13 PM
Re: POS Exploitation
Obviously PCI compliance is not optional anymore if you are making business with government or other big companies, they ask their sub-contactors be PCI compliant anymore.
Dr.T
Dr.T,
User Rank: Ninja
11/29/2015 | 11:56:11 AM
Re: POS Exploitation
Agree, most POS is old technology so changing it costly but as Target and Hilton realize not changing is apparently more costly.
Page 1 / 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 10 Most Impactful Types of Vulnerabilities for Enterprises Today
Managing system vulnerabilities is one of the old est - and most frustrating - security challenges that enterprise defenders face. Every software application and hardware device ships with intrinsic flaws - flaws that, if critical enough, attackers can exploit from anywhere in the world. It's crucial that defenders take stock of what areas of the tech stack have the most emerging, and critical, vulnerabilities they must manage. It's not just zero day vulnerabilities. Consider that CISA's Known Exploited Vulnerabilities (KEV) catalog lists vulnerabilitlies in widely used applications that are "actively exploited," and most of them are flaws that were discovered several years ago and have been fixed. There are also emerging vulnerabilities in 5G networks, cloud infrastructure, Edge applications, and firmwares to consider.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2023-1142
PUBLISHED: 2023-03-27
In Delta Electronics InfraSuite Device Master versions prior to 1.0.5, an attacker could use URL decoding to retrieve system files, credentials, and bypass authentication resulting in privilege escalation.
CVE-2023-1143
PUBLISHED: 2023-03-27
In Delta Electronics InfraSuite Device Master versions prior to 1.0.5, an attacker could use Lua scripts, which could allow an attacker to remotely execute arbitrary code.
CVE-2023-1144
PUBLISHED: 2023-03-27
Delta Electronics InfraSuite Device Master versions prior to 1.0.5 contains an improper access control vulnerability in which an attacker can use the Device-Gateway service and bypass authorization, which could result in privilege escalation.
CVE-2023-1145
PUBLISHED: 2023-03-27
Delta Electronics InfraSuite Device Master versions prior to 1.0.5 are affected by a deserialization vulnerability targeting the Device-DataCollect service, which could allow deserialization of requests prior to authentication, resulting in remote code execution.
CVE-2023-1655
PUBLISHED: 2023-03-27
Heap-based Buffer Overflow in GitHub repository gpac/gpac prior to 2.4.0.