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?
Newest First  |  Oldest First  |  Threaded View
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.
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.
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. 
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.  
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.


COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/3/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
New 'Nanodegree' Program Provides Hands-On Cybersecurity Training
Nicole Ferraro, Contributing Writer,  8/3/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-17452
PUBLISHED: 2020-08-09
flatCore before 1.5.7 allows upload and execution of a .php file by an admin.
CVE-2020-17451
PUBLISHED: 2020-08-09
flatCore before 1.5.7 allows XSS by an admin via the acp/acp.php?tn=pages&sub=edit&editpage=1 page_linkname, page_title, page_content, or page_extracontent parameter, or the acp/acp.php?tn=system&sub=sys_pref prefs_pagename, prefs_pagetitle, or prefs_pagesubtitle parameter.
CVE-2020-17447
PUBLISHED: 2020-08-09
MyBB before 1.8.24 allows XSS because the visual editor mishandles [align], [size], [quote], and [font] in MyCode.
CVE-2020-16248
PUBLISHED: 2020-08-09
** DISPUTED ** Prometheus Blackbox Exporter through 0.17.0 allows /probe?target= SSRF. NOTE: follow-on discussion suggests that this might plausibly be interpreted as both intended functionality and also a vulnerability.
CVE-2020-15820
PUBLISHED: 2020-08-08
In JetBrains YouTrack before 2020.2.6881, the markdown parser could disclose hidden file existence.