- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
08-18-2025 09:06 AM
I want to prevent the execution of anydesk.exe, choco.exe, and cloudflared.exe. However, I went to the Prevention Policy Rules and created restrictions for applications, but it only allows blocking in specific locations, so that doesn't meet my needs. I want these applications to be blocked whenever they are detected anywhere in the system.
08-19-2025 11:49 AM
To block executions in your use case you can do several things:
Realize that hashes can change if files are updated for example new versions of the same sofware are uploaded.
If you feel this has answered your query, please let us know by clicking like and on "mark this as a Solution". Thank you.
KR,
Luis
08-20-2025 07:01 AM
Hi again @J.Lopes154290 ,
There is something else you can do.
You can block the remote access software by signer. The cons are that if this software vendor, develops other software that is not for remote access you are blocking it too.
Create a BIOC just adding the signer you want to block (TeamViewer, etc... whatever you want), then you can test it if you want to make sure it works as expected.
At this point BIOC is just alerting, not blocking anything
To block: right clicking on the BIOC you can add it to a restriction profile. This will send the BIOC to the agents under that policy rule and will start blocking that signer, any software from that signer.
If you feel this has answered your query, please let us know by clicking like and on "mark this as a Solution". Thank you.
KR,
Luis
08-19-2025 11:49 AM
To block executions in your use case you can do several things:
Realize that hashes can change if files are updated for example new versions of the same sofware are uploaded.
If you feel this has answered your query, please let us know by clicking like and on "mark this as a Solution". Thank you.
KR,
Luis
08-20-2025 07:01 AM
Hi again @J.Lopes154290 ,
There is something else you can do.
You can block the remote access software by signer. The cons are that if this software vendor, develops other software that is not for remote access you are blocking it too.
Create a BIOC just adding the signer you want to block (TeamViewer, etc... whatever you want), then you can test it if you want to make sure it works as expected.
At this point BIOC is just alerting, not blocking anything
To block: right clicking on the BIOC you can add it to a restriction profile. This will send the BIOC to the agents under that policy rule and will start blocking that signer, any software from that signer.
If you feel this has answered your query, please let us know by clicking like and on "mark this as a Solution". Thank you.
KR,
Luis
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!