- Sep 22, 2014
- 1,767
Here one interesting video by Britec09.
Block Downloads of a Specific File Type in Windows (with Comodo)
Block Downloads of a Specific File Type in Windows (with Comodo)
Please provide comments and solutions that are helpful to the author of this topic.
@AtlBo, you went pretty deep into Comodo HIPS. If you can't find your way out of the woods, you could try posting on the Comodo forum. The guys over there know the product pretty well.
I must admit that you are dealing with certain settings that I don't rightly understand.
@AtlBo, you went pretty deep into Comodo HIPS. If you can't find your way out of the woods, you could try posting on the Comodo forum. The guys over there know the product pretty well.
Thanks. Did this:
1. Sandbox set to "ignore" for both cmd.exes
2. Set them both to "Unrecognized" in files list
3. Made sure webshield.exe (Chrome extension) was "Unrecognized" in files list
4. Set all HIPs rules to ask for both cmd.exes
5. Turned off embedded detection for cmd.exe in Advanced->Misc
6. In HIPs set webshield.exe to ask (was allowed) for all HIPs protections
Glad to hear you are all sorted out.Thanks shmu26. Got it all worked out and back to the previous settings .
Glad to hear you are all sorted out.
NVT ERP already gives you cmd.exe protection, so you don't really need this tweak.
What security Mode ?
What HIPS settings?
Good point.True @shmu26. Still somewhat concerned about the fact that tricks can bypass command line protection. @Andy Ful 's thread here is the one that started me looking at this:
How-to Guide - How do you secure PowerShell?
Andy tested Comodo protection for powershell, and found it to be good.
He found a hole in Voodooshield, and the dev already patched it.
Yeah, a lot of people had trouble updating to the newest Comodo build on Windows XP, and also on Win7. But it went smooth for most, on Win10.I did not check anything, because I tried updating CF from version 8 to 10, on my dad's computer with Windows XP + SP3. The version 8 worked very well, but after update the system hanged. Thankfully, I could boot in the safe mode, and run autoruns. I had to uncheck all Comodo entries (services and drivers) to make the system bootable. So, I restored the CF 8, and it is OK.
Okay, after rereading @Andy Ful's interesting post, I realized that he was just giving a general overview of the features, rather than reporting on his own testing.Yeah, a lot of people had trouble updating to the newest Comodo build on Windows XP, and also on Windows 7. But it went smooth for most, on Windows 10.
Sorry for misquoting you! I guess I misunderstood your post:
How-to Guide - How do you secure PowerShell?
"Summing up the PowerShell security in Comodo Firewall, we have:
The 'Embeded Code Detection' catches fileless scripts, converts them into files in the: C:\ProgramData\Comodo\Cis\tempscrpt
- Comodo Sandbox with @cruelsister settings, when keeping powershell.exe and powershell_ise.exe as Unrecognized.
- "Heuristic Command Line Analysis" and "Embedded Code Detection", integrated under one interface as "Do Heurristic Command Line Analysis".
folder, and finally throws into the sandbox. This fucntion + heuristics has to be quite efficient in script blocking. People on Comodo forum complain, that their scripts (Visual Studio project assemblies) are autosandboxed, when "Do Heurristic Command Line Analysis" is activated. If one wants to run embedded scripts, he can activate the HIPS, and give the script hosting executable, the Installer/Updater policy.
So, for home users, CF offers very good PowerShell security."
The important thing with CF is to realize the best settings are not Rocket Science; trying to make it so will just end in tears.
I like CF, but I don't like having to download Comodo Dragon, and that Geek Buddy. Is there some way to avoid having to download that crap?
Hi @cruelsister, no question about it, your settings are the quickest way to security nirvana.Also, although the HIPS module will be of use with the sandbox at default
What would you use if it wasn't capable of this? What's in the market?But one thing I can assure you of- if CF could be compromised in ways like this I would never ever use it myself. I can be nasty beyond belief yet I am satisfied with CF.
Yes indeed, Comodo 10 with its awesome embedded code detection will stop straightforward exploits using powershell that actually execute the file the regular way. But what about attacks that use powershell in memory, and what about attacks that use cmd.exe? (By default, Comodo 10 disables embedded code detection for cmd.exe, because it cripples too many apps.)The more I think about it, the more I hate the term "Fileless Attack" as it is so misleading. When seeing that term one can reasonably infer that something just appears and will make changes to the local system without anything actually being run- and this is far, far from the case! In actuality a fileless attack will be something like going to a compromised webpage, running a Flash app (like through maladvertising) which will then run a PowerShell script locally on your system, which will them compromise you in various ways. CF will sandbox this process so no local changes will ever be seen. A file (malware) that tries to exploit something in another process can't actually do bery much if that process is not available to it.
About Boot time protection- Comodo has none at all! But it does not really matter as something has to get on the system first in order to mess with things at boot. A few years ago I coded a Timing trojan and did a few videos about it. Although it was undetected and got past all AV's tried (some had boot protection, some did not, some added such protection after the video), Comodo never allowed it to autostart, so Boot Time protection didn't even come into play.
But one thing I can assure you of- if CF could be compromised in ways like this I would never ever use it myself. I can be nasty beyond belief yet I am satisfied with CF.