Author Topic: Using Software Restriction Policy to help prevent Cryptolocker  (Read 3995 times)

0 Members and 1 Guest are viewing this topic.

Offline Charyb-0

  • Avast Evangelist
  • Massive Poster
  • ***
  • Posts: 2508
Using Software Restriction Policy to help prevent Cryptolocker
« on: February 02, 2014, 06:21:48 PM »
Are there any more paths that can be entered into Software Restriction Policy that will help protect against Cryptolocker and any other type of Ransomware? I copied and pasted the paths using info provided by Bleeping Computers.

http://www.bleepingcomputer.com/virus-removal/cryptolocker-ransomware-information

Please see attachment.
« Last Edit: February 02, 2014, 06:32:04 PM by Charyb »

Offline polonus

  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 33912
  • malware fighter
Re: Using Software Restriction Policy to help prevent Cryptolocker
« Reply #1 on: February 02, 2014, 06:38:49 PM »
Other preventive measures are being mentioned here:
http://www.pcadvisor.co.uk/features/security/3491195/how-protect-yourself-from-cryptolocker-attack/
These measures consist of making back-ups and save these offline. Make online back-ups through free services.
The most important message however is to never to open a file or link from an email or on a social site
if one does not know whether it was sent deliberately for recipient.
Use this little program to prevent: http://www.foolishit.com/vb6-projects/cryptoprevent/
CryptoPrevent is completely FREE for personal and commercial usage!

greets,

polonus
Cybersecurity is more of an attitude than anything else. Avast Evangelists.

Use NoScript, a limited user account and a virtual machine and be safe(r)!

Offline essexboy

  • Malware removal instructor
  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 40589
  • Dragons by Sasha
    • Malware fixes
Re: Using Software Restriction Policy to help prevent Cryptolocker
« Reply #2 on: February 02, 2014, 07:05:23 PM »
The FoolishIT programme will be updated to cover new vectors, at the moment it has them covered

Hard_ROCKER

  • Guest
Re: Using Software Restriction Policy to help prevent Cryptolocker
« Reply #3 on: February 04, 2014, 12:19:16 AM »
Some other tools:

HitmanPro.Alert with CryptoGuard:
http://www.surfright.nl/en/alert/cryptoguard
latest beta:
http://www.wilderssecurity.com/showpost.php?p=2336519&postcount=1152

Bitdefender Anti-Cryptolocker(download link on the bottom of the post):
http://labs.bitdefender.com/2013/10/cryptolocker-ransomware-makes-a-bitcoin-wallet-per-victim/?sm_id=SMGlobal?utm_source=SMGlobal&utm_medium=SMGlobal&utm_campaign=H4S



Can avast! protect me against CryptoLocker?
http://blog.avast.com/2013/11/19/can-avast-protect-me-against-cryptolocker/
Quote
How to protect your computer from CryptoLocker?

AVAST users should be safe from infection during the short period when the malware is new and “undetected” as long as AutoSandbox and DeepScreen are active. “The infection is prevented by means of a dynamic detection,” said Sramek.

“We also automatically add detections for each new sample that passes our backend filters,” said Jiri Sejtko, Sramek’s colleague in the avast! Virus Lab.

“Against future threats like this, having a backup is always a good idea – who knows when CryptoLocker v2.0 will be released, and every antivirus solution is reactive by nature,” said Sramek. “The encryption used is virtually unbreakable, there is zero chance of recovering files after infection.”
« Last Edit: February 04, 2014, 12:45:01 AM by Darth.Mikey »

Offline Charyb-0

  • Avast Evangelist
  • Massive Poster
  • ***
  • Posts: 2508
Re: Using Software Restriction Policy to help prevent Cryptolocker
« Reply #4 on: February 05, 2014, 10:14:53 PM »
Thanks for the helpful information. I witnessed SRP work while trying to install HP Printer Control so at least the temp path keeps executables from running there.

I think I will try out Crypto Prevent. Seems much easier than SRP.

I do have HitmanPro.Alert installed but it is not the one for Cryptolocker. I will install it once it comes out of beta.

I also had Corrine mention to show known file extensions which will allow a user to view the extension before opening the file. Extensions such as <filename>pdf.exe more than likely are going to be bad news.

Thanks
« Last Edit: February 05, 2014, 10:17:28 PM by Charyb »