Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Security
Video Reviews - Security and Privacy
ESET Internet Security VS FCrypt Ransomware
Message
<blockquote data-quote="SeriousHoax" data-source="post: 870710" data-attributes="member: 78686"><p>Not much really. Their response to any kinds of missed threats has always been that a malware simply doesn't arrive on the system. It either comes from a malicious sites or email attachments etc and in those case Eset would likely block the arrival of that ransomware in the first place before it would do any damage. Which is correct and I agree with them but still it shouldn't be an excuse to the failure of the Ransomware shield. But Eset has always been a signature focused, pre execution based detection type of AV. It's the best at detecting variants of known malware but if something brand new comes along Eset usually fails. Eset also has what I would say a "<span style="color: rgb(226, 80, 65)">False positive phobia</span>". They prioritize this over everything.</p><p>Btw, this signature removal thing recently happened once again. In February in a malware pack from our malware hub one sample was missed by Eset. It was a .ps1 Powershell script. I submitted it to them and they added a signature. Few days ago I saw that Eset is not detecting that anymore, not even after executing with everything set to aggresive. I submitted it back to them and also wrote this used to be detected then the next day Eset started detecting it again. I don't know why this happened again! But by the looks of it, it seems it happens more than often.</p></blockquote><p></p>
[QUOTE="SeriousHoax, post: 870710, member: 78686"] Not much really. Their response to any kinds of missed threats has always been that a malware simply doesn't arrive on the system. It either comes from a malicious sites or email attachments etc and in those case Eset would likely block the arrival of that ransomware in the first place before it would do any damage. Which is correct and I agree with them but still it shouldn't be an excuse to the failure of the Ransomware shield. But Eset has always been a signature focused, pre execution based detection type of AV. It's the best at detecting variants of known malware but if something brand new comes along Eset usually fails. Eset also has what I would say a "[COLOR=rgb(226, 80, 65)]False positive phobia[/COLOR]". They prioritize this over everything. Btw, this signature removal thing recently happened once again. In February in a malware pack from our malware hub one sample was missed by Eset. It was a .ps1 Powershell script. I submitted it to them and they added a signature. Few days ago I saw that Eset is not detecting that anymore, not even after executing with everything set to aggresive. I submitted it back to them and also wrote this used to be detected then the next day Eset started detecting it again. I don't know why this happened again! But by the looks of it, it seems it happens more than often. [/QUOTE]
Insert quotes…
Verification
Post reply
Top