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
The Future Of ATM Hacking
Newest First  |  Oldest First  |  Threaded View
RetiredUser
100%
0%
RetiredUser,
User Rank: Ninja
7/31/2017 | 3:31:47 PM
Re: Security Cost vs. Risks
It should be noted that by deferring costs for securing a user's private data or money (even though insured, its still your money being attacked since your personal info is attached to it) rather than fixing a known problem (or an anticpated problem) a company risks alienating customers and breaking a very fundamental business ethics practice.  We need to get better at saving money early on in the process so we can put due diligence into the design, secure early on to avoid such exploits, and maintain ethical relationships with our customers.  Heck, we could even use some of the money saved on operational security monitoring...
IdahoseW596
0%
100%
IdahoseW596,
User Rank: Apprentice
5/8/2017 | 12:48:53 PM
Re: ATM Security
hi there
jcavery
50%
50%
jcavery,
User Rank: Moderator
8/28/2016 | 10:23:41 PM
Re: Security Cost vs. Risks
you're rght andrew, cost is the main driver when choosing a defense against hackers. the problem will always be that hackers only have to invest in the first target, once hacked, there is no cost for them to replicate the hack again across infinite targets. however, banks, institutions, etc have a huge initial cost for the solution, and then multiplied to implement across every customer they have. this is why the hackers will have a "cost" advantage until a better solution is found
AndrewfOP
50%
50%
AndrewfOP,
User Rank: Moderator
8/13/2016 | 2:14:38 PM
Security Cost vs. Risks
"Unfortunately, many ATM operators are reluctant to make hardware upgrades..."

 

It's all about costs vs. risks.  If the costs of better security is more than the damage of the risks, decision makers would continue to avoid 'costly' security until the damage itself becomes far more costly.  It's the same thing with EMV adaption with merchants: when VISA & Master Card made the ones that won't adopt EMV bear the fraud damage, the adoption became far more wide spread. Until the manufacturers/operators start to bear More of the damage responsibility, there would continue to be poor security with ATMs.  
Nabeelshaikhd
50%
50%
Nabeelshaikhd,
User Rank: Apprentice
8/13/2016 | 8:11:25 AM
Thanks for this nice post!
I love this blog and its posts!
DrNashik
50%
50%
DrNashik,
User Rank: Apprentice
8/11/2016 | 2:53:14 PM
ATM Security
I remember the May ATM scandle Japan. I wonder if using the chips in ATM's would help reduce the fraud. Seems to be working everywhere else..


News
Former CISA Director Chris Krebs Discusses Risk Management & Threat Intel
Kelly Sheridan, Staff Editor, Dark Reading,  2/23/2021
Edge-DRsplash-10-edge-articles
Security + Fraud Protection: Your One-Two Punch Against Cyberattacks
Joshua Goldfarb, Director of Product Management at F5,  2/23/2021
News
Cybercrime Groups More Prolific, Focus on Healthcare in 2020
Robert Lemos, Contributing Writer,  2/22/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Building the SOC of the Future
Building the SOC of the Future
Digital transformation, cloud-focused attacks, and a worldwide pandemic. The past year has changed the way business works and the way security teams operate. There is no going back.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-25284
PUBLISHED: 2021-02-27
An issue was discovered in through SaltStack Salt before 3002.5. salt.modules.cmdmod can log credentials to the info or error log level.
CVE-2021-3144
PUBLISHED: 2021-02-27
In SaltStack Salt before 3002.5, eauth tokens can be used once after expiration. (They might be used to run command against the salt master or minions.)
CVE-2021-3148
PUBLISHED: 2021-02-27
An issue was discovered in SaltStack Salt before 3002.5. Sending crafted web requests to the Salt API can result in salt.utils.thin.gen_thin() command injection because of different handling of single versus double quotes. This is related to salt/utils/thin.py.
CVE-2021-3151
PUBLISHED: 2021-02-27
i-doit before 1.16.0 is affected by Stored Cross-Site Scripting (XSS) issues that could allow remote authenticated attackers to inject arbitrary web script or HTML via C__MONITORING__CONFIG__TITLE, SM2__C__MONITORING__CONFIG__TITLE, C__MONITORING__CONFIG__PATH, SM2__C__MONITORING__CONFIG__PATH, C__M...
CVE-2021-3197
PUBLISHED: 2021-02-27
An issue was discovered in SaltStack Salt before 3002.5. The salt-api's ssh client is vulnerable to a shell injection by including ProxyCommand in an argument, or via ssh_options provided in an API request.