Block Execution of Specific Applications Regardless of Location

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Block Execution of Specific Applications Regardless of Location

L0 Member

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.

 

Cortex XDR 

2 accepted solutions

Accepted Solutions

L5 Sessionator

Hi @J.Lopes154290 

 

To block executions in your use case you can do several things: 

  1. Block hashes (one by one): going to action center and click on add new action and block list. Bear in mind that changes here will take effect on agents after the next check-in of the agent
  2. Block hashes (bulk number of hashes from file import): going to action center and click on Import Hash Exceptions.
    Check the video on how to do it: https://live.paloaltonetworks.com/t5/cortex-xdr-how-to-videos/cortex-xdr-how-to-video-import-file-ha...
  3. Add a restriction profile and play with the wildcards to implement your use case:
    https://docs-cortex.paloaltonetworks.com/r/Cortex-XDR/Cortex-XDR-3.x-Documentation/Set-up-restrictio...

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

View solution in original post

L5 Sessionator

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

View solution in original post

2 REPLIES 2

L5 Sessionator

Hi @J.Lopes154290 

 

To block executions in your use case you can do several things: 

  1. Block hashes (one by one): going to action center and click on add new action and block list. Bear in mind that changes here will take effect on agents after the next check-in of the agent
  2. Block hashes (bulk number of hashes from file import): going to action center and click on Import Hash Exceptions.
    Check the video on how to do it: https://live.paloaltonetworks.com/t5/cortex-xdr-how-to-videos/cortex-xdr-how-to-video-import-file-ha...
  3. Add a restriction profile and play with the wildcards to implement your use case:
    https://docs-cortex.paloaltonetworks.com/r/Cortex-XDR/Cortex-XDR-3.x-Documentation/Set-up-restrictio...

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

L5 Sessionator

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

  • 2 accepted solutions
  • 599 Views
  • 2 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!