CryptoStopper™  Features

Signature based products like anti-virus are not able to detect zero-day threats and AV is only about 43% effective. Ransomware gets past your traditional defenses by using social engineering attacks against the company employees whom are not consistently able to distinguish a phishing email from a valid email. To make matters worse fileless ransomware attacks only require an employee to visit a site to start a ransomware attack that runs solely in memory. No files touch the disk so AV never detects it.

We offer a 60 day money back guarantee. No other guarantee.

Yes. CryptoStopper™ uses an algorithm to monitor specially crafted WatcherFiles™. When Ransomware attacks your server, CryptoStopper™ correlates the offending user and immediately isolates that user. It simultaneously notifies the admin via email.

Yes, we offer a 60 day money back guarantee.

The average time to detection is :09 seconds.

Instead of monitoring each endpoint with CryptoStopper™, we monitor the data that sits on the file server, and again once a threshold is met, we flag that as ransomware.

Setting the archive bit will not activate CryptoStopper™ since setting the archive bit doesn’t modify the file. The archive bit is simply an attribute of the file.

CryptoStopper™ is extremely lightweight. The software only monitors the files that it creates so it’s not burdened by watching thousands of files.

Yes. WatchPoint provides automatic updates to CryptoStopper.

A typical install will take 15 minutes or less.

Yes, we have a beta version available now. Click here to download.

No, your backup only updates the archive bit and doesn’t modify the file.

CryptoStopper™ will detect all ransomware.

No. The software is not a HIPs. We monitor the data to look for an excessive amount of changes. Once that threshold is met, we know it’s ransomware or possibly an anomaly that should be investigated immediately.

CryptoStopper™ should be installed on your server to monitor for infections.

Potentially, although the false positives should be minimal we have found instances where a program folder is located in the same path as a protected shared folder. If the software is reinstalled you will get a false positive.