DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

Journal Times editorial: Paying ransom to computer hackers not the way to go

Posted on February 25, 2015 by Dissent

In response to a recent news story out of Midlothian (noted here), an editorial in The Journal Times reminds law enforcement that they should take their own advice and not pay ransom to hackers who lock up police files.

As the editors note, the Midlothian incident is not the first time law enforcement has paid ransom:

Last November, the Dickson County Sheriff’s Department in Tennessee paid out $572 when the same virus infected its computers. The sheriff there said his first reaction was “we are not going to be held hostage. But, he said, “once it was determined which records were involved and that they were crucial to victims of crimes in this county, and to the operations of the sheriff’s office and the citizens of this county … I had no choice but to authorize to pay this.”

I don’t recall ever seeing that case, but I do recall the one in Detroit earlier last year. In that case, the city didn’t pay the demand for hundreds of thousands of dollars.

As the editors note:

Paying ransom, even cheap ransom, is never a good policy, and it’s particularly unseemly when a police agency is held up.

Read more on The Journal Times.

We’ll probably never know how often entities pay ransom and just quietly go about their business if they’re lucky enough to get the promised decryption key, but the editors have a point: this should not be one of those “Do as we say, not as we do” situations.

Category: Commentaries and Analyses

Post navigation

← National Center for Charitable Statistics Discovers Unauthorized Access to Form 990 and e-Postcard Filing Systems for Nonprofit Organizations
Utah bill to require warrant to access state prescription database advances →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • Texas gastroenterology and surgical practice victim of ransomware attack
  • Romanian Citizen Pleads Guilty to ‘Swatting’ Numerous Members of Congress, Churches, and Former U.S. President
  • North Dakota Enacts Financial Data Security and Data Breach Notification Requirements
  • Pro-Ukraine hacker group Black Owl poses ‘major threat’ to Russia, Kaspersky says
  • Vanta bug exposed customers’ data to other customers
  • Lyrix Ransomware Targets Windows Users with Advanced Evasion Techniques
  • Central Maine Healthcare tackles suspected cybersecurity issue; hospitals remain open
  • Cartier Data Breach: Luxury Retailer Warns Customers that Personal Data Was Exposed
  • Beyond the Pond Phish: Unraveling Lazarus Group’s Evolving Tactics
  • Akira doesn’t keep its promises to victims — SuspectFile

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • Supreme Court Agrees to Clarify Emergency Situations Where Police Don’t Need Warrant
  • Stewart Baker vs. Orin Kerr on “The Digital Fourth Amendment”
  • Fears Grow Over ICE’s Reach Into Schools
  • Resource: HoganLovells Asia-Pacific Data, Privacy and Cybersecurity Guide 2025
  • She Got an Abortion. So A Texas Cop Used 83,000 Cameras to Track Her Down.
  • Why AI May Be Listening In on Your Next Doctor’s Appointment
  • Watch out for activist judges trying to deprive us of our rights to safe reproductive healthcare

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net

Mastodon: Infosec.Exchange/@PogoWasRight

Signal: +1 516-776-7756

DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.
Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report