Reply to thread

Message

<blockquote data-quote="shmu26" data-source="post: 794982" data-attributes="member: 37647">1 If you want to improve on the default Comodo protection, go into advanced settings, miscellaneous, embedded code detection. Over there, you can enable more processes to be protected. But even if you enable all of them, it is a short list, it does not cover everything, and furthermore, it has not been tested thoroughly. It works well for Powershell, but I have questions about some of the other ones.If you find that this conflicts with your software in some way, disable embedded code detection only for the process that gives you trouble. (You can still get protection for that process if you enable Comodo HIPS and make some custom settings, but that is another subject).2 I don&#039;t know how well OSA works with Comodo. You could try it, and deliberately cause blocks of various sorts, and see if it works right.3 If you want to add to Comodo protection by using another solution, I would recommend [USER=32260]@Andy Ful[/USER]&#039;s Hard_Configurator. Using it, you can enable protection for a long and inclusive list of vulnerable processes (he calls them &quot;sponsors&quot;), and it will not conflict with Comodo. But even if you don&#039;t enable any of them, the default protections of &quot;Recommended SRP&quot; are already very strong. You can use the special template that Andy prepared for Avast hardened/aggressive mode, because it is appropriate also for Comodo @CS settings. That is what I use on my wife&#039;s laptop.4 Please note that enabling full protection for all vulnerable processes, or sponsors, or lol bins, or whatever you want to call them -- this is not possible on all systems. It depends a lot on your hardware and software. If you have a conflict, but still want protection for that process, then you need a security solution that allows you more fine-grained control, such as NVT ERP, or ReHIPS, or Comodo HIPS (it you know how to configure it properly).</blockquote>

[QUOTE="shmu26, post: 794982, member: 37647"] 1 If you want to improve on the default Comodo protection, go into advanced settings, miscellaneous, embedded code detection. Over there, you can enable more processes to be protected. But even if you enable all of them, it is a short list, it does not cover everything, and furthermore, it has not been tested thoroughly. It works well for Powershell, but I have questions about some of the other ones. If you find that this conflicts with your software in some way, disable embedded code detection only for the process that gives you trouble. (You can still get protection for that process if you enable Comodo HIPS and make some custom settings, but that is another subject). 2 I don't know how well OSA works with Comodo. You could try it, and deliberately cause blocks of various sorts, and see if it works right. 3 If you want to add to Comodo protection by using another solution, I would recommend [USER=32260]@Andy Ful[/USER]'s Hard_Configurator. Using it, you can enable protection for a long and inclusive list of vulnerable processes (he calls them "sponsors"), and it will not conflict with Comodo. But even if you don't enable any of them, the default protections of "Recommended SRP" are already very strong. You can use the special template that Andy prepared for Avast hardened/aggressive mode, because it is appropriate also for Comodo @CS settings. That is what I use on my wife's laptop. 4 Please note that enabling full protection for all vulnerable processes, or sponsors, or lol bins, or whatever you want to call them -- this is not possible on all systems. It depends a lot on your hardware and software. If you have a conflict, but still want protection for that process, then you need a security solution that allows you more fine-grained control, such as NVT ERP, or ReHIPS, or Comodo HIPS (it you know how to configure it properly). [/QUOTE]

Verification