Reply to thread

Message

<blockquote data-quote="Deleted member 65228" data-source="post: 732842">NoVirusThanks OSArmor will not replace Malwarebytes Anti-Exploit and vice-versa.Malwarebytes Anti-Exploit supports enforcing Bottom-Up ASLR, DEP and a few other mitigation&#039;s. Furthermore, it performs Remote Code Execution (RCE) into monitored applications and uses this as an advantage to locally intervene with the behavior of the application to assist it in identifying and preventing exploitation attacks. Bear in mind, it also has specific mitigation&#039;s for some things and also supports protection with targets like Java.NoVirusThanks OSArmor does not do the things Malwarebytes Anti-Exploit does, in the same way that Malwarebytes Anti-Exploit does not do what NoVirusThanks OSArmor does. In fact, they both work entirely differently and I would not even estimate that a conflict would be 30% probable.If you already have Malwarebytes Anti-Exploit, fear not, NoVirusThanks OSArmor will NOT be useless (and vice-versa). If they work well when combined on your environment, and as long as they provide your requirements, then it should be really good.NoVirusThanks OSArmor is actually extremely light and non-intrusive from my experience and as long as you set it up which is right for you, it can be incredibly helpful. It might not work the same way that other vendors approach their exploit mitigation techniques, but it doesn&#039;t mean that the product is lesser than another.If you&#039;re looking for something lightweight, reliable and non-intrusive, then NVT OSArmor is the solution. Since it doesn&#039;t work like a majority of other Anti-Exploit components (e.g. it will not touch the memory of another running application nor the Windows Kernel aside from documented and Microsoft-approved techniques), it won&#039;t degrade performance of an applications general operations through interception and it&#039;ll neither break other applications through external manipulation (e.g. cause them to crash due to a bug in memory modification).</blockquote>

[QUOTE="Deleted member 65228, post: 732842"] NoVirusThanks OSArmor will not replace Malwarebytes Anti-Exploit and vice-versa. Malwarebytes Anti-Exploit supports enforcing Bottom-Up ASLR, DEP and a few other mitigation's. Furthermore, it performs Remote Code Execution (RCE) into monitored applications and uses this as an advantage to locally intervene with the behavior of the application to assist it in identifying and preventing exploitation attacks. Bear in mind, it also has specific mitigation's for some things and also supports protection with targets like Java. NoVirusThanks OSArmor does not do the things Malwarebytes Anti-Exploit does, in the same way that Malwarebytes Anti-Exploit does not do what NoVirusThanks OSArmor does. In fact, they both work entirely differently and I would not even estimate that a conflict would be 30% probable. If you already have Malwarebytes Anti-Exploit, fear not, NoVirusThanks OSArmor will NOT be useless (and vice-versa). If they work well when combined on your environment, and as long as they provide your requirements, then it should be really good. NoVirusThanks OSArmor is actually extremely light and non-intrusive from my experience and as long as you set it up which is right for you, it can be incredibly helpful. It might not work the same way that other vendors approach their exploit mitigation techniques, but it doesn't mean that the product is lesser than another. If you're looking for something lightweight, reliable and non-intrusive, then NVT OSArmor is the solution. Since it doesn't work like a majority of other Anti-Exploit components (e.g. it will not touch the memory of another running application nor the Windows Kernel aside from documented and Microsoft-approved techniques), it won't degrade performance of an applications general operations through interception and it'll neither break other applications through external manipulation (e.g. cause them to crash due to a bug in memory modification). [/QUOTE]

Verification