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.

Application Security

11:50 AM
Curtis Franklin
Curtis Franklin
Curt Franklin

HONEST Poll Results: When Should You Pay the Ransom?

When ransomware hits, when should you just pay up? The Security Now community has spoken.

Ransomware has captured the imagination of executives and IT professionals even though, taken in the context of all security issues, it's not really at the top of the list. Unless, of course, you're the one staring at a screen demanding a ransom payment in order to get your data back.

If you do see such a screen, do you pay the ransom or not? That's the question we asked in our most recent poll and the answers provided by our community were decisive. Half of the total taking the poll said that "Never!" is the only right answer when it comes to when a ransom should be paid. Another quarter said that paying up is a last resort, while 16% got judgmental, saying that paying a ransom is an admission that your backup and recover plans aren't what they should be.

As always, we recognize the limitations of our methods. We understand that the polls we conduct here on our pages aren't going to fuel academic research. That's why it's important that we properly label the conclusions. I think it's accurate to call them a Highly Opinionated, Not Especially Scientific Tally -- or, as I like to think of them: HONEST results.

Security Now community member Joe Stanganelli explained his "last resort" vote: "Game theory dictates that you never pay a blackmailer because there's nothing to prevent the blackmailer from blackmailing you again." That's a sentiment explained in more detail in Carl Herberger's recent article here at Security Now.

Herberger pointed out, "paying a ransom provides no safe harbor." He recognized, though, that business considerations often win out over principle when it comes to ransomware. "When facing a ransom attack, many companies must weigh the cost of paying the fee against the cost of downtime or a leak. The decision is not easy because ... paying a ransom just proves that a business is willing to pay."

So what is the "wisdom of the crowd" when it comes to paying a ransom? Stated simply, it's this: Never, ever pay a ransom -- unless you have to.

Related posts:

— Curtis Franklin is the editor of SecurityNow.com. Follow him on Twitter @kg4gwa.

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
Manchester United Suffers Cyberattack
Dark Reading Staff 11/23/2020
As 'Anywhere Work' Evolves, Security Will Be Key Challenge
Robert Lemos, Contributing Writer,  11/23/2020
Cloud Security Startup Lightspin Emerges From Stealth
Kelly Sheridan, Staff Editor, Dark Reading,  11/24/2020
Register for Dark Reading Newsletters
White Papers
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
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2020-11-28
An issue was discovered in the Linux kernel before 5.2.6. On NUMA systems, the Linux fair scheduler has a use-after-free in show_numa_stats() because NUMA fault statistics are inappropriately freed, aka CID-16d51a590a8c.
PUBLISHED: 2020-11-28
An issue was discovered in __split_huge_pmd in mm/huge_memory.c in the Linux kernel before 5.7.5. The copy-on-write implementation can grant unintended write access because of a race condition in a THP mapcount check, aka CID-c444eb564fb1.
PUBLISHED: 2020-11-28
An issue was discovered in mm/mmap.c in the Linux kernel before 5.7.11. There is a race condition between certain expand functions (expand_downwards and expand_upwards) and page-table free operations from an munmap call, aka CID-246c320a8cfe.
PUBLISHED: 2020-11-28
An issue was discovered in kmem_cache_alloc_bulk in mm/slub.c in the Linux kernel before 5.5.11. The slowpath lacks the required TID increment, aka CID-fd4d9c7d0c71.
PUBLISHED: 2020-11-28
An issue was discovered in romfs_dev_read in fs/romfs/storage.c in the Linux kernel before 5.8.4. Uninitialized memory leaks to userspace, aka CID-bcf85fcedfdd.