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
NOD32 10.0 HIPS Test (Catastrophic failure)
Message
<blockquote data-quote="RejZoR" data-source="post: 578580" data-attributes="member: 57233"><p>[MEDIA=youtube]dMUqcyrhf6Y[/MEDIA]</p><p></p><p>NOD32 was hugely requested and to my surprise, it was absolute and total letdown. Not only it failed after FIRST executed sample, the HIPS component did exactly NOTHING through the entire test. It hasn't done anything for ransomware samples either. Granted, I don't know NOD32 in depth as much as I do avast! (and many others), but in this case, either HIPS component heavily relies on Real-Time part or it was really this bad. In which case, it is annoying to have a toggle for separate functions which later don't work at all without any disclaimer or notification about potentially limited protection. I mean, during tests, I sometimes disable real-time components of my AV, but I want to be sure on-execution, HIPS or behavior blocker components still protect me in case I by mistake somehow execute test samples on my host system. In case of NOD32, things would end up pretty badly, where in case of AVG, Kaspersky and Bitdefender, that wouldn't be the case as their proactive components work fully independently and also highly efficiently. I know ESET is pretty strong on file heuristics, but they really have to send their HIPS component back to the drawing board...</p><p></p><p>Version used in this test was: NOD32 Antivirus 10.0.369.0 (fully updated before the test)</p></blockquote><p></p>
[QUOTE="RejZoR, post: 578580, member: 57233"] [MEDIA=youtube]dMUqcyrhf6Y[/MEDIA] NOD32 was hugely requested and to my surprise, it was absolute and total letdown. Not only it failed after FIRST executed sample, the HIPS component did exactly NOTHING through the entire test. It hasn't done anything for ransomware samples either. Granted, I don't know NOD32 in depth as much as I do avast! (and many others), but in this case, either HIPS component heavily relies on Real-Time part or it was really this bad. In which case, it is annoying to have a toggle for separate functions which later don't work at all without any disclaimer or notification about potentially limited protection. I mean, during tests, I sometimes disable real-time components of my AV, but I want to be sure on-execution, HIPS or behavior blocker components still protect me in case I by mistake somehow execute test samples on my host system. In case of NOD32, things would end up pretty badly, where in case of AVG, Kaspersky and Bitdefender, that wouldn't be the case as their proactive components work fully independently and also highly efficiently. I know ESET is pretty strong on file heuristics, but they really have to send their HIPS component back to the drawing board... Version used in this test was: NOD32 Antivirus 10.0.369.0 (fully updated before the test) [/QUOTE]
Insert quotes…
Verification
Post reply
Top