Reply to thread

Message

<blockquote data-quote="cruelsister" data-source="post: 990653" data-attributes="member: 7463">For WiseVector (which works well with CF). I would suggest leaving everything at default EXCEPT changing both the Firewall and HIPS modules of WVSX to Low Security- this is because the HIPS is not needed and the WV firewall is inferior to that of CF. Alternatively if you would rather try Kaspersky Cloud, this could be installed with CF, but note that the alert that Comodo is incompatible should be ignored- just proceed with the installation. As to the Cruel settings, yes they are still valid. As I use CF myself any new malware that I come across (or code myself) will be tried against CF. Still haven&#039;t been able to penetrate the protection afforded and God Knows I&#039;ve tried. You have noted that some claimed that CF was bypassed but none has been able to prove that such exists. Instead Cf has shown its value recently as a legitimately signed Magniber ransomware that was a true Zer0 Day (at the time) was ignored by available AV&#039;s but stopped by the File Rating module in CF which shunted the malware off to the sandbox where it expired in despair.Finally you have brought up the issue that occasionally Comodo will alert that various legitimate windows files are Blocked (especially certain WD things and something like SmartScreen). I do agree that this is a pain, but can be remedied by right clicking on them in the Blocked section of the GUI and adding them to Trusted. The dll&#039;s and aux files that Windows generates in Assembly are not really blocked as such and are just generated during installs/uninstalls so can be ignored.Hope this helps, and I apologize for not responding to this thread sooner.M</blockquote>

[QUOTE="cruelsister, post: 990653, member: 7463"] For WiseVector (which works well with CF). I would suggest leaving everything at default EXCEPT changing both the Firewall and HIPS modules of WVSX to Low Security- this is because the HIPS is not needed and the WV firewall is inferior to that of CF. Alternatively if you would rather try Kaspersky Cloud, this could be installed with CF, but note that the alert that Comodo is incompatible should be ignored- just proceed with the installation. As to the Cruel settings, yes they are still valid. As I use CF myself any new malware that I come across (or code myself) will be tried against CF. Still haven't been able to penetrate the protection afforded and God Knows I've tried. You have noted that some claimed that CF was bypassed but none has been able to prove that such exists. Instead Cf has shown its value recently as a legitimately signed Magniber ransomware that was a true Zer0 Day (at the time) was ignored by available AV's but stopped by the File Rating module in CF which shunted the malware off to the sandbox where it expired in despair. Finally you have brought up the issue that occasionally Comodo will alert that various legitimate windows files are Blocked (especially certain WD things and something like SmartScreen). I do agree that this is a pain, but can be remedied by right clicking on them in the Blocked section of the GUI and adding them to Trusted. The dll's and aux files that Windows generates in Assembly are not really blocked as such and are just generated during installs/uninstalls so can be ignored. Hope this helps, and I apologize for not responding to this thread sooner. M [/QUOTE]

Verification