Hi @RajeshPremSingh, thank you for writing to Live Community.
You are correct that if a file hash often changes the way to block it would not be through the file hash allowlist.
You can create a custom process based BIOC rule to detect the execution of the file you’re looking to block. Go into Detection Rules --> BIOC --> Add BIOC and follow these steps to create a new process query.
Next, head over to Policy Management→ Profiles→ Add Profile →Create New→Choose platform (note that this will not apply to iOS or Android) and choose Restrictions Profile. Make sure to enable Custom Prevention Rules
After creating the BIOC rule you can now configure a custom prevention rule by going into Detection Rules → BIOC → Locate your newly created BIOC rule→ Right click and choose ‘Add to restrictions profile’.
Next, choose the profile you’ve created and click ‘Add’.
You should see the following message after you’re done.
Hope this helps!
Hi @RajeshPremSingh, thank you for writing to Live Community.
You are correct that if a file hash often changes the way to block it would not be through the file hash allowlist.
You can create a custom process based BIOC rule to detect the execution of the file you’re looking to block. Go into Detection Rules --> BIOC --> Add BIOC and follow these steps to create a new process query.
Next, head over to Policy Management→ Profiles→ Add Profile →Create New→Choose platform (note that this will not apply to iOS or Android) and choose Restrictions Profile. Make sure to enable Custom Prevention Rules
After creating the BIOC rule you can now configure a custom prevention rule by going into Detection Rules → BIOC → Locate your newly created BIOC rule→ Right click and choose ‘Add to restrictions profile’.
Next, choose the profile you’ve created and click ‘Add’.
You should see the following message after you’re done.
Hope this helps!
