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
Ransomware Attacks: Why It Should Be Illegal to Pay the Ransom
Newest First  |  Oldest First  |  Threaded View
TomWool
100%
0%
TomWool,
User Rank: Apprentice
2/6/2020 | 7:58:44 PM
Re: Bad Advice from a Non-Involved Vendor
Making it illegal will make it less likely that attacks will be reported to authorities. Organizations will pay up and keep it quiet to avoid legal ramifications.   
acmcgregor
50%
50%
acmcgregor,
User Rank: Author
2/5/2020 | 11:37:53 PM
Re: Bad Advice from a Non-Involved Vendor
It is always a business decision first
christcpd@yahoo.com
80%
20%
[email protected],
User Rank: Strategist
2/5/2020 | 10:10:27 AM
Bad Advice from a Non-Involved Vendor
While it sounds great to make ransomware payments illegal, the author's perspective is one of being a non-involved vendor living and working in an ivory tower.  Real life, aka business, is not as simple.

It is easy to say that organizations should have good cybersecurity.  We all say it.  We all scream it from the rooftops.  Sadly, reality is far different when budgets and priorities enter the equation.

In reality, paying a ransom often presents the fastest return to operations.  Paying a ransom can drastically reduce the Mean Time To Repair resulting in less downtime and less risk of long term issues (like lawsuits and negative insurance claims.)

Paying a ransom is a business decision and should never be regulated by government.


Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
State of Cybersecurity Incident Response
State of Cybersecurity Incident Response
Data breaches and regulations have forced organizations to pay closer attention to the security incident response function. However, security leaders may be overestimating their ability to detect and respond to security incidents. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-5292
PUBLISHED: 2020-03-31
Leantime before versions 2.0.15 and 2.1-beta3 has a SQL Injection vulnerability. The impact is high. Malicious users/attackers can execute arbitrary SQL queries negatively affecting the confidentiality, integrity, and availability of the site. Attackers can exfiltrate data like the users' and admini...
CVE-2020-7009
PUBLISHED: 2020-03-31
Elasticsearch versions from 6.7.0 to 6.8.7 and 7.0.0 to 7.6.1 contain a privilege escalation flaw if an attacker is able to create API keys. An attacker who is able to generate an API key can perform a series of steps that result in an API key being generated with elevated privileges.
CVE-2019-13495
PUBLISHED: 2020-03-31
In firmware version 4.50 of Zyxel XGS2210-52HP, multiple stored cross-site scripting (XSS) issues allows remote authenticated users to inject arbitrary web script via an rpSys.html Name or Location field.
CVE-2020-5291
PUBLISHED: 2020-03-31
Bubblewrap (bwrap) before version 0.4.1, if installed in setuid mode and the kernel supports unprivileged user namespaces, then the `bwrap --userns2` option can be used to make the setuid process keep running as root while being traceable. This can in turn be used to gain root permissions. Note that...
CVE-2019-14905
PUBLISHED: 2020-03-31
A vulnerability was found in Ansible Engine versions 2.9.x before 2.9.3, 2.8.x before 2.8.8, 2.7.x before 2.7.16 and earlier, where in Ansible's nxos_file_copy module can be used to copy files to a flash or bootflash on NXOS devices. Malicious code could craft the filename parameter to perform OS co...