If you are using a signed PoC, search the "Vendor List" for the vendor. Also, check "HIPS Events" in Logs for the Cloud verdict. Based on this, you can disable features and retest.
I'd assume the language we warned you about and how to talk to other members of the forum.one question and i dont know where to ask this: why am i being moderated? all my coments needs aproval now.
i thought so but it was not anything related to forum users nor disrespect with anyone. it was just one person who, for whatever reason, was frustated about one word used in a setence wich had nothing to do with this user or his feelings, but he was in the need of some attention and tried to change the subject to make this personal. astleast that is what im feeling about it. as feelings are what people take in consideration, maybe my feelings would be taken into it too. no?I'd assume the language we warned you about and how to talk to other members of the forum.
Agree to disagree; apologies, by the way, for getting you off topic.i thought so but it was not anything related to forum users nor disrespect with anyone. it was just one person who, for whatever reason, was frustated about one word used in a setence wich had nothing to do with this user or his feelings, but he was in the need of some attention and tried to change the subject to make this personal. astleast that is what im feeling about it. as feelings are what people take in consideration, maybe my feelings would be taken into it too. no?
see the problem? (i think i manage to explain a little bit more this time).
oh, btw, i apologized for the word even if it was nothing wrong with it. anyway... we are offtopic again.
sorry but youre wrong. the exe has certs but the dll hasnt (atleast is seems so). the dll continues to be ignore by cis, cloud lookup, valkyrie, etc. but even win defender can recognize it. so, no, the test is not wrong and there is nothing to check on logs as cis has no proper log for this dll. just that its not recognized but still its allowed to run on default config.According to the Comodo alert, the PoC has a digital signature. It appears the Comodo cloud contains this signature, but the local whitelist does not. As a result, the PoC failed in this test. If you had checked the Comodo logs as I repeatedly suggested, you would have discovered this solution during the first test. The problem with your PoC tests is that you post the results without confirming them.
Nothing new here. What comes next? A PoC uses a certificate on the Comodo local whitelist, alongside a method to disable that whitelist!
Defeats the purpose I use comodo as the comodo cloud has less false positives then wdac ,Smart App Control etc that are superior in terms of securityI do not recommend disabling cloud lookup, except when a "family administrator" has the motivation to protect "computer illiterate" users or when Comodo is used in organizations.
I do not use such a setup, so I cannot exclude the possibility that it might be hardly usable in practice. I think that Comodo users can share some thoughts about it in this thread.
Yes disabling cloud is definitely far more restrictive but makes the product too unusable...
She's missing because of this:Anyway really miss cruel sister in this fourm she's absolutely an expert on everything comodo and more
Comodo Internet Security 2025 Beta / Final / Infos ThreadI've given up on MT recently as it seems to be overrun by Trolls for only God knows why. I've posted videos about various AM applications (MB, eset, esmisoft, Symantec, etc) being bypassed by malware (and these could be confirmed as the malware was in the Wild) all of which raised barely a peep. but when something trivial is found against Comodo it's like the World is ending
I also miss Cruel; she is THE Comodo expert.She disabled it specifically to show the containment blocks the samples in her videos as it was marked as malware
But she doesn't disable cloud lookup in her config
Yes disabling cloud is definitely far more restrictive but makes the product too unusable as it's always a balance between false positives and at that ratio of false positives you're better of using superior built in protections
Anyway really miss cruel sister in this fourm she's absolutely an expert on everything comodo and more
Most users shouldn't disable cloud lookup or whitelists. Instead, I suggest using Comodo Firewall Proactive Security with Microsoft Defender. If you don't use containment, replacing it with blocking unknowns will enhance protection. Experts can remove certain vendors from the trusted vendor list and disable cloud lookup. This will undoubtedly become bothersome, particularly when running unsigned applications without cloud lookup. If Comodo offered an "ask" option for auto-containment alerts, I'd definitely keep core vendors and disable cloud lookup.Disabling cloud lookup significantly reduces the possibility of using by the attackers the Trusted (but vulnerable) EXE files to avoid auto-containment. This approach is similar to WDAC or AppLocker policies (strict default-deny, no cloud app reputation). It can also prevent other attack vectors (different from DLL hijacking) when Trusted files are exploited. The shorter the Trusted Vendors list, the smaller the chances of infection.
I do not recommend disabling cloud lookup, except when a "family administrator" has the motivation to protect "computer illiterate" users or when Comodo is used in organizations.
I do not use such a setup, so I cannot exclude the possibility that it might be hardly usable in practice. I think that Comodo users can share some thoughts about it in this thread.