Reply to thread

Message

<blockquote data-quote="XLR8R" data-source="post: 1071664" data-attributes="member: 85385">The program uses a tool named killproc which does exactly what it says using methods that are very much similar to &quot;KillAV&quot;. The killproc is also heavily utilized by the eScan BB. This program is still effective protection wise but code-wise it&#039;s a frankenstein, there&#039;s layers and layers of code and a lot of legacy modules still run. It is surprisingly light despite this and is the last AV that still supports Windows 2000.Basically eScan AV has some G-Data legacy code, some own modules, their own web filtering and real-time drivers coupled with BitDefender&#039;s ATC from 2017-2018 modified with their own ruleset (periodically updated) and complemented with a self-developed behavioral monitoring &quot;add-on&quot; that actually works in tandem with the BitDefender ATC/AVC. They also use the BitDefender scan engine SDK, but have their own signatures for certain threats and PUPs BitDefender does not detect.</blockquote>

[QUOTE="XLR8R, post: 1071664, member: 85385"] The program uses a tool named killproc which does exactly what it says using methods that are very much similar to "KillAV". The killproc is also heavily utilized by the eScan BB. This program is still effective protection wise but code-wise it's a frankenstein, there's layers and layers of code and a lot of legacy modules still run. It is surprisingly light despite this and is the last AV that still supports Windows 2000. Basically eScan AV has some G-Data legacy code, some own modules, their own web filtering and real-time drivers coupled with BitDefender's ATC from 2017-2018 modified with their own ruleset (periodically updated) and complemented with a self-developed behavioral monitoring "add-on" that actually works in tandem with the BitDefender ATC/AVC. They also use the BitDefender scan engine SDK, but have their own signatures for certain threats and PUPs BitDefender does not detect. [/QUOTE]

Verification