04-26-2023 07:29 AM
Has anyone successfully implemented in their environment? Do you do it by BIOC Restrictions, using digital signatures, file path or executable name?
04-26-2023 09:07 PM - edited 04-26-2023 09:08 PM
Hi @Kahlil
Thank you for writing to live community!
You may block a file/application from running on any of your endpoints in either way i.e.
1. By adding the associated hash to the block list but with new version of application, hash might change and thus application will not be blocked as application Hash would need to be updated.
2. By using BIOC restrictions and in BIOC restrictions to adapt with Hash change you may use the Digital Signature or Vendor Signature. You may refer to this thread for more details.
Hope this helps!
Please mark the response as "Accept as Solution" if it answers your query.
Regards.
04-26-2023 09:07 PM - edited 04-26-2023 09:08 PM
Hi @Kahlil
Thank you for writing to live community!
You may block a file/application from running on any of your endpoints in either way i.e.
1. By adding the associated hash to the block list but with new version of application, hash might change and thus application will not be blocked as application Hash would need to be updated.
2. By using BIOC restrictions and in BIOC restrictions to adapt with Hash change you may use the Digital Signature or Vendor Signature. You may refer to this thread for more details.
Hope this helps!
Please mark the response as "Accept as Solution" if it answers your query.
Regards.
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!
