Reply to thread

Message

<blockquote data-quote="partha_roy" data-source="post: 1065692" data-attributes="member: 96828">Hi [USER=92939]@Shadowra[/USER], I was away for a while and just came across your test that I was eagerly waiting for; I appreciate you taking the&nbsp; time to review this product; it&#039;s one of my absolute favourites Just a few points that I wanted to touch base on with respect to the test and perhaps you may want to look into when you test it the next time -you may want to enable the code analyser under the Objects menu; that&#039;s eScan&#039;s heuristic scanner that examines suspicious codes and may aid in blocking powershell scripts that the other modules may missyou can see below that it detected and stopped a malicious ps script that I tried to extract; it was detected immediately upon access by the file explorer [ATTACH=full]279779[/ATTACH]One other point I wanted to bring up was you accidentally allowing access to a file that was detected by eScan as suspicious; it&#039;s at the 3:32 mark where you accidentally allowed the accessLastly, eScan does have a fairly extensive knowledge base repository and it can be accessed by clicking the question mark icon at the top right of any eScan dialog box[ATTACH=full]279780[/ATTACH]</blockquote>

[QUOTE="partha_roy, post: 1065692, member: 96828"] Hi [USER=92939]@Shadowra[/USER], I was away for a while and just came across your test that I was eagerly waiting for; I appreciate you taking the time to review this product; it's one of my absolute favourites Just a few points that I wanted to touch base on with respect to the test and perhaps you may want to look into when you test it the next time - you may want to enable the code analyser under the Objects menu; that's eScan's heuristic scanner that examines suspicious codes and may aid in blocking powershell scripts that the other modules may miss you can see below that it detected and stopped a malicious ps script that I tried to extract; it was detected immediately upon access by the file explorer [ATTACH type="full"]279779[/ATTACH] One other point I wanted to bring up was you accidentally allowing access to a file that was detected by eScan as suspicious; it's at the 3:32 mark where you accidentally allowed the access Lastly, eScan does have a fairly extensive knowledge base repository and it can be accessed by clicking the question mark icon at the top right of any eScan dialog box [ATTACH type="full"]279780[/ATTACH] [/QUOTE]

Verification