Apparently Sophos engine is capable of handling password-protected zips. In the files used to test Webroot (less than successfully) Sophos detected malware.
www.sophos.com
View attachment 276073
@Trident , please allow me simple questions from my very ignorant side:
1. If Sophos engine is capable of handling password-protected zips, can we infer that ZAESNG based on Sophos engine is capable to do the same? Or not necessarily? To be based on a Sophos and Kaspersky engine means to have same capabilities as Sophos and Kasperky engines have?
2. Here in this thread, are you always using ZAESNG in your tests? Or sometimes you use Harmony EndPoint?
3. Your attached forensic images are from Harmony EndPoint? Or from your ZAESNG at C:/Program Data/Check Point/Endpoint Security/Threat Emulation/Reports?
Btw this is how I like tests, with few samples every day so I can pick and understand them, otherwise too many samples at one is not as effective test.
Yeah, it's another great way to test. Besides the fact of giving you a full and better comprehension, few samples every day also offer high quality tests because reflect zero-day-attack responses or at least reflect latest pest protection capabilities.
Btw that stealer is signed. Under default policy ZA and Harmony Endpoint terminate trusted files but don't delete them (the original file remained on the system). This is why it may look like ZoneAlarm didn't do anything... coupled with the slow message that takes time to appear... I forgot to add in the post above. Only on Harmony Endpoint this setting can be changed to get trusted files deleted and not just terminated.
4. What about connections? Sorry to ask, it's not totally clear to me, "terminate" means that the stealer started (and only then was terminated). So, it sounds that the stealer wasn't stopped or blocked to run. If that is the case, did the stealer manage to make any connections? Or the stealer never ran at all, nor succeeded to make connections etc?