- Apr 21, 2018
- 397
- Content source
- https://youtu.be/JPESRmqFXjg
but it doesnt run, he shouldve showen then containment atleastSeems one malware bypass containment.
I suppose he erased the container but i am not sure.but it doesnt run, he shouldve showen then containment atleast
there is also another comodo sandbox bypass
it's Comodo fault if it failed to auto sandbox the malware(or malware probably bypassed the sandbox)..At Leo's video we don't know if it was contained at all.
Absolutely spot onThis is the problem I have when people test software but cannot explain the protection scheme. The tester's "I am just one of you so the a-v has to please me", should only go as far as how the settings are arranged and how protections are managed. Beyond this, the tester is a tester, not a consumer user->he is an educator. Instead, this guy constantly acts like it's not his job to know how the program works in all his videos. Well, his videos go down the tubes because of this of course.
So on to Comodo. So I believe what we are seeing is what malware can do when the container is set to run at default settings. Also, the sandbox was not emptied which is HIGHLY recommended after a bout on a system with over 1000 malwares...oh yeah. Also, @cruelsister has it right. If you want to have 100% bullet-proof protection against malware--->default block rather than virtualize. And please remember to empty the sandbox if not . Thankyou...
Oh, one last thing. I think we should recall all of the ransomware and REALLY horrible malware that Comodo has blocked in videos from @cruelsister and others. We've seen it contain "limited", "partially limited", and block, and we have seen the difference with our eyes. Traces will be on the system with "limited" and "partially limited" and wallpaper can change, etc. Yet, even then no infection have we seen, even from the worst and most brilliantly constructed (if you will) malwares.
Totally agree.Comodo has so many unique characteristics, in the way functioning, that souldn't be tested with Leo's "automatic test running programm" because it missed the whole point.This is the problem I have when people test software but cannot explain the protection scheme. The tester's "I am just one of you so the a-v has to please me", should only go as far as how the settings are arranged and how protections are managed. Beyond this, the tester is a tester, not a consumer user->he is an educator. Instead, this guy constantly acts like it's not his job to know how the program works in all his videos. Well, his videos go down the tubes because of this of course.
So on to Comodo. So I believe what we are seeing is what malware can do when the container is set to run at default settings. Also, the sandbox was not emptied which is HIGHLY recommended after a bout on a system with over 1000 malwares...oh yeah. Also, @cruelsister has it right. If you want to have 100% bullet-proof protection against malware--->default block rather than virtualize. And please remember to empty the sandbox if not . Thankyou...
Oh, one last thing. I think we should recall all of the ransomware and REALLY horrible malware that Comodo has blocked in videos from @cruelsister and others. We've seen it contain "limited", "partially limited", and block, and we have seen the difference with our eyes. Traces will be on the system with "limited" and "partially limited" and wallpaper can change, etc. Yet, even then no infection have we seen, even from the worst and most brilliantly constructed (if you will) malwares.
This configuration turns CIS into the ultimate protection machine. All possible protections are activated and all critical COM interfaces and files are protected.
Also keep in mind Leo was running it in the "Internet Security" configuration instead of "Proactive Security" configuration.
Regardless, whether running CIS in proactive would've helped is unknown.
Maybe sometime in the future AV vendors must consider the possibility to sell their products with high/hardened settings at default, will help them also for marketing reasons having good test results.This is very true
This is the one problem I have with some of these videos is that they don't really take the time to explain the actual product and how different settings could have an impact on its protection capabilities good or bad. Granted that most people like to test everything at default settings as that's the setting(s) most people will use, but I always feel like if you are going to take the time make a video to test/review a product, at least take the time to explain the WHOLE product, its settings and what each of them can do. Sometimes just turning on one or 2 settings can make a significant difference in its capabilities...or not, but regardless it should still be discussed.