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 Ransomware Dilemma: What if Your Local Government Is Next?
Threaded  |  Newest First  |  Oldest First
BigKahuna13
100%
0%
BigKahuna13,
User Rank: Apprentice
5/30/2019 | 12:52:22 PM
To pay, or not to pay?
Scary how many groups and organizations have silently paid to avoid the public humiliation that Baltimore is currently enduring.
schopj
100%
0%
schopj,
User Rank: Strategist
5/30/2019 | 3:43:53 PM
What if you pay, then get hit again?
One of the things to consider when looking at the initial ransom cost vs cost of recovery is the cost of the next infection.  If you pay, the attackers now know youre willing to pay.  They ARE going to target you again.  So that 100,000 could quickly turn into much more over time because now youre seen as an easy target.  A city that doesnt pay, it doesnt make much sense for attackers to spend a lot of time and effort infecting them again when they get nothing out of it.  If we really want these types of attacks to stop, we need to make it cost more and profit less.  The only way to do that is for all businesses and governments to refuse to pay.  Without payment, the attackers will move on.  As long as even some vitims choose to pay, there will be more and more victims and the costs over the entire economy will keep going up.  
BanduraCSO
50%
50%
BanduraCSO,
User Rank: Author
5/31/2019 | 8:17:49 AM
Re: What if you pay, then get hit again?
Totally agree.  Guess the conundrum is there are a healthy number of organizations that are paying and so how do you stop something like this that's already in motion.  On the cost side, Baltimore is now pointing to $8.1 million in lost revenue.  I think if we expand this analysis out the real issue is comparing all of these costs against the investment they should have made to ensure an up to date IT infrastructure and more importantly to apply a patch that's been available for two years. 
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
5/31/2019 | 3:12:02 PM
Re: What if you pay, then get hit again?
Agreed. The reason companies are typically told not to pay the ransom is because you are operating under the mechanism that you are expecting an unethical entity to act ethically and do what they say they are going to do. Nothing stopping them from going back on their promises and exposing either the data or secrets that you don't want exposed. 

On the flip side if they are extorting data and you don't have a viable backup program, then you may be at their mercy for getting back.

Its really a lose lose any way you look at it.
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
6/5/2019 | 1:09:49 PM
Re: What if you pay, then get hit again?
FOR A SMILE - Firms that lack a backup strategy (damn dumb) now have one - their encrypted data stored securely by thieves.  Negotiate a payment plan and if they backup but do not encrypt the data locally, then the firm has a viable and secure method of restoration and recovery.  Monthly fee service. See, it works if you think weird.


Mobile Banking Malware Up 50% in First Half of 2019
Kelly Sheridan, Staff Editor, Dark Reading,  1/17/2020
Active Directory Needs an Update: Here's Why
Raz Rafaeli, CEO and Co-Founder at Secret Double Octopus,  1/16/2020
New Attack Campaigns Suggest Emotet Threat Is Far From Over
Jai Vijayan, Contributing Writer,  1/16/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: I've never actually seen the corporate ladder before.
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
How Enterprises are Attacking the Cybersecurity Problem
How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-5216
PUBLISHED: 2020-01-23
In Secure Headers (RubyGem secure_headers), a directive injection vulnerability is present in versions before 3.9.0, 5.2.0, and 6.3.0. If user-supplied input was passed into append/override_content_security_policy_directives, a newline could be injected leading to limited header injection. Upon seei...
CVE-2020-5217
PUBLISHED: 2020-01-23
In Secure Headers (RubyGem secure_headers), a directive injection vulnerability is present in versions before 3.8.0, 5.1.0, and 6.2.0. If user-supplied input was passed into append/override_content_security_policy_directives, a semicolon could be injected leading to directive injection. This could b...
CVE-2020-5223
PUBLISHED: 2020-01-23
In PrivateBin versions 1.2.0 before 1.2.2, and 1.3.0 before 1.3.2, a persistent XSS attack is possible. Under certain conditions, a user provided attachment file name can inject HTML leading to a persistent Cross-site scripting (XSS) vulnerability. The vulnerability has been fixed in PrivateBin v1.3...
CVE-2019-20399
PUBLISHED: 2020-01-23
A timing vulnerability in the Scalar::check_overflow function in Parity libsecp256k1-rs before 0.3.1 potentially allows an attacker to leak information via a side-channel attack.
CVE-2020-7915
PUBLISHED: 2020-01-22
An issue was discovered on Eaton 5P 850 devices. The Ubicacion SAI field allows XSS attacks by an administrator.