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.

Partner Perspectives  Connecting marketers to our tech communities.
SPONSORED BY
11/8/2016
10:00 AM
Malwarebytes Labs
Malwarebytes Labs
Partner Perspectives
50%
50%

Ransomware Doesn’t Have To Mean Game Over

3 methods can help you recover from a ransomware attack relatively unscathed.

It’s not difficult to wrap your brain around how ransomware could do serious damage to businesses. But how exactly do CISOs and other security executives deal with the infection and its aftermath? New technologies are popping up all the time that combat ransomware; however, most (if not all) require active protection before you get infected.

This article aims to help those who’ve already been hit with encrypting ransomware and are faced with either paying or losing files. Let’s look at three different ransomware infection scenarios and how business leaders can attempt to walk away relatively unscathed.

Prepared

Our first security executive -- the prepared one -- keeps her system up-to-date, uses security software, and provides employee training on cybersecurity best practices. Unfortunately, one of her employees visited a popular website that was dealing with a malicious advertising attack. The attack launched a zero-day, drive-by exploit, which installed a brand new family of ransomware that encrypted the customer database.

How did a prepared security executive handle this type of attack? Thankfully, she had the foresight to keep regular backups, which means that after the infection, all she had to do was clean the system using recently updated security software and then restore the backup. Only a day’s worth of data was lost.

Backing up files securely is one of the best ways to prepare your system to deal with a ransomware infection. However, you should keep file history enabled in your backup solution so that you can revert to a previous backup in case the most recent gets polluted with encrypted data. Also, use off-site and/or cloud backups rather than storing everything on a network drive, since many ransomware families are capable of reaching through mapped connections to encrypt files outside the victim’s hard drive.

Reactionary

Our next leader thinks that only gullible people get infected with malware, and that by avoiding obvious bad places, he can protect his business from a threat. One day, an employee received an invoice from a local vendor with a spoofed email address, and the invoice is actually a script that neuters security software and downloads malware. Suddenly, that employee was infected, and all mapped drives were encrypted.

Many believe that once you’ve been hit with ransomware, your files are encrypted and there is nothing you can do about it. However, thanks to the diligent efforts of our information security community, there are actually many decryptors available online. This software, when matched with the correct ransomware family, can decrypt files for free.

In order to identify the family of ransomware you are dealing with, you can look closely at the ransom note -- it often tells you itself. And when the note doesn’t say, you can look at the extension name of your encrypted files.

Ignorant

Our final leader just doesn’t know enough about computers. He has a few terminals set up in his shop that use trial security software. Unfortunately, one of his employees downloaded a malicious torrent online. Now, all of the networked systems in the shop are encrypted, including a folder that keeps all his trade secrets. 

Since our leader didn’t create regular backups and doesn’t know how to use decryptor tools, he’ll need to think about negotiating with the criminals. Rather than pay the full ransom, he can pay a smaller amount by identifying a particular set of files he needs more than others. Historically, attackers have been open to negotiating and returning a few files for a smaller ransom.

To be absolutely clear, I do not endorse paying the ransom. However, it has to be understood that for some folks, the loss of files would be far more damaging than just paying the ransom.

Conclusion 

So there you have it -- three methods that can help you recover from a ransomware attack. They might not be absolute solutions, but anything is better than losing valuable data to cybercriminals. Maybe knowing how disappointing the recovery methods are will motivate people to use proactive anti-ransomware technology, which remains the best option for fighting ransomware infection -- not allowing the malware to encrypt your files in the first place.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/6/2020
Ripple20 Threatens Increasingly Connected Medical Devices
Kelly Sheridan, Staff Editor, Dark Reading,  6/30/2020
DDoS Attacks Jump 542% from Q4 2019 to Q1 2020
Dark Reading Staff 6/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15564
PUBLISHED: 2020-07-07
An issue was discovered in Xen through 4.13.x, allowing Arm guest OS users to cause a hypervisor crash because of a missing alignment check in VCPUOP_register_vcpu_info. The hypercall VCPUOP_register_vcpu_info is used by a guest to register a shared region with the hypervisor. The region will be map...
CVE-2020-15565
PUBLISHED: 2020-07-07
An issue was discovered in Xen through 4.13.x, allowing x86 Intel HVM guest OS users to cause a host OS denial of service or possibly gain privileges because of insufficient cache write-back under VT-d. When page tables are shared between IOMMU and CPU, changes to them require flushing of both TLBs....
CVE-2020-15566
PUBLISHED: 2020-07-07
An issue was discovered in Xen through 4.13.x, allowing guest OS users to cause a host OS crash because of incorrect error handling in event-channel port allocation. The allocation of an event-channel port may fail for multiple reasons: (1) port is already in use, (2) the memory allocation failed, o...
CVE-2020-15567
PUBLISHED: 2020-07-07
An issue was discovered in Xen through 4.13.x, allowing Intel guest OS users to gain privileges or cause a denial of service because of non-atomic modification of a live EPT PTE. When mapping guest EPT (nested paging) tables, Xen would in some circumstances use a series of non-atomic bitfield writes...
CVE-2020-15563
PUBLISHED: 2020-07-07
An issue was discovered in Xen through 4.13.x, allowing x86 HVM guest OS users to cause a hypervisor crash. An inverted conditional in x86 HVM guests' dirty video RAM tracking code allows such guests to make Xen de-reference a pointer guaranteed to point at unmapped space. A malicious or buggy HVM g...