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
Heres How To Protect Against A Ransomware Attack
Oldest First  |  Newest First  |  Threaded View
theb0x
50%
50%
theb0x,
User Rank: Ninja
2/9/2016 | 12:53:45 PM
Ransomware
Because ransomware is capable of attacking both local and remote backups, the best line of defense is a proper retention policy of encrypted backups. I suggest a minimum of 2 weeks.

Since the backups are already encrypted, they are simply not vulnerable. No matter what method of attack is used. The ransomware will not have access to these files to apply it's own encryption algorithm.

Also, as far as I know the method of attack utilized is soley by file extension. Ransomware is not yet capable of anylizing mime type file headers. That being said, renaming the extension of a known file type such as a word document (ie .docx) to something completely obscure (ie .zyx612), followed by changing the new file type association to open with MS Word will result in the file indexing of the ransomware to bypass encryption of the unrecognized extension.
j03king
100%
0%
j03king,
User Rank: Apprentice
5/16/2016 | 9:44:20 PM
New Strain are Smarter than just targeted common file extensions! Your backup needs to be secured!
Apart from all the other Ransomware Protection best practice 101 guides.....

 

First of all just because you are encrypting your backups doesn't mean a ransomware cannot re-encrypt it. We've had a few cases where all clients had their encrypted backups targeted and damaged by ransomware! Your best defence to safe guard your backups:

1. Permissions - Remove all default file & folder permissions on the repository folder. Specifically add a single backup user permission. eg. create a user "repobackup" with read & write. Deny group administrators to this folder and other groups & users.

Configure your backup software to specifically use the repobackup user to do it's business.

Any access to this folder except for the user repobackup will be denied. So all attempts of the ransomware to find it on the network (including accessing hidden shared drives, c$, d$,etc etc) will be denied access to it once it hits your repofolder.

(even ransomware as they wont have permission to it.)

2. Sftp/scp -  some backup software have modules that will allow for remote replication via SFTP/SCP. You should make use of them.

 

Secondly, you shouldn't rely on simply tricking "ransomware" with renaming your files. We've had two cases of modified ransomware (well they should call it "ransom DAMAGEWARE") that had absolutely no intention of giving victims their data and allowed for * file extension.

 

 

OPTION if it is available to you.

 

Explore the software from "Cylance" for your unconventional Security Suite. So far clients that chose to implement it (following previous attacks), have been miraculously somewhat protected. Even with the new strains such as when Locky started to appear, it has seemed to have innoculated it.


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Enterprise Cybersecurity Plans in a Post-Pandemic World
Download the Enterprise Cybersecurity Plans in a Post-Pandemic World report to understand how security leaders are maintaining pace with pandemic-related challenges, and where there is room for improvement.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-21742
PUBLISHED: 2021-09-25
There is an information leak vulnerability in the message service app of a ZTE mobile phone. Due to improper parameter settings, attackers could use this vulnerability to obtain some sensitive information of users by accessing specific pages.
CVE-2020-20508
PUBLISHED: 2021-09-24
Shopkit v2.7 contains a reflective cross-site scripting (XSS) vulnerability in the /account/register component, which allows attackers to hijack user credentials via a crafted payload in the E-Mail text field.
CVE-2020-20514
PUBLISHED: 2021-09-24
A Cross-Site Request Forgery (CSRF) in Maccms v10 via admin.php/admin/admin/del/ids/<id>.html allows authenticated attackers to delete all users.
CVE-2016-6555
PUBLISHED: 2021-09-24
OpenNMS version 18.0.1 and prior are vulnerable to a stored XSS issue due to insufficient filtering of SNMP trap supplied data. By creating a malicious SNMP trap, an attacker can store an XSS payload which will trigger when a user of the web UI views the events list page. This issue was fixed in ver...
CVE-2016-6556
PUBLISHED: 2021-09-24
OpenNMS version 18.0.1 and prior are vulnerable to a stored XSS issue due to insufficient filtering of SNMP agent supplied data. By creating a malicious SNMP 'sysName' or 'sysContact' response, an attacker can store an XSS payload which will trigger when a user of the web UI views the data. This iss...