()tries to get access to comodo in memory

what is the suggested action, when i have to choose to let something accessing comodo parts (cfp.exe, cmdagent.exe, etc.) in memory. or if “()tries to change userinterface of cfp.exe, etc…”.
this questions mostly happen, if you run a program that detects for cheat software, or which is “monitoring” something.
in this example i am speaking about steam especially.

what can a program do with cis in that cases? or with instant messengers or antivirus for another example?
and what would happen, if the “good” program is exploited…

If it’s bad and you give it access to an other program’s memory regions then it can control the “attacked” application… so basically you could be infected by then in memory that is…

CIS should be protected against those attacks by default.

Can you post a screenshot of such a tool accessing the memory ?

I would say those “anti-cheats” are danger close to being malware/rootkit’s i wouldn’t like those to access all my memory regions of all running apps, could give them full control over your system.

In this case you are only protecting the safety of your system, not cheating, strange Terms & Conditions if you ask me. I’d ask the admin of those games what his “view” is on blocking these with D+ ?

I my case this would be a No No, Game Over :smiley: