Have you enabled SSL Decryption? Since the Chrome Web Store runs over SSL, and if you're not using SSL Decryption, then your choice becomes permitting all extensions or blocking all extensions.
However, if you focus on the traffic generated by the "searchencrypt" extension - that's something much easier to target without collatteral damage. You're not necessarily stopping users from downloading the extension, but these options will prevent the extension from working.
The easiest way would be to use the URL Filtering engine and block the "proxy-avoidance-and-anonymizers" URL category - that will stop the searchencrypt extension from working. Two upsides to this method: 1.) it would block other/similar extensions which have been categorized as proxies by our URL filtering engine, and 2.) it can provide some visual feedback through the URL Response Pages. The error page can be customized to your environment and provide additional information to the user receiving the message.
Here's a screenshot after blocking that URL category:
If you don't have the URL filtering subscription, I believe you can still create custom URL categories. Add "searchencrypt.com" and "*.searchencrypt.com" to a custom URL category and deny access to that category.
Another option if you don't have the URL filtering subscription: create a custom AppID signature. I configured one that looks for "searchencrypt.com" in the SSL Response Certificate context of the SSL decoder. Here's a screenshot with most of the information you'd need to create the custom application signature:
And here's a screenshot from the traffic log showing it blocking based on the custom AppID signature:
Have you enabled SSL Decryption? Since the Chrome Web Store runs over SSL, and if you're not using SSL Decryption, then your choice becomes permitting all extensions or blocking all extensions.
However, if you focus on the traffic generated by the "searchencrypt" extension - that's something much easier to target without collatteral damage. You're not necessarily stopping users from downloading the extension, but these options will prevent the extension from working.
The easiest way would be to use the URL Filtering engine and block the "proxy-avoidance-and-anonymizers" URL category - that will stop the searchencrypt extension from working. Two upsides to this method: 1.) it would block other/similar extensions which have been categorized as proxies by our URL filtering engine, and 2.) it can provide some visual feedback through the URL Response Pages. The error page can be customized to your environment and provide additional information to the user receiving the message.
Here's a screenshot after blocking that URL category:
If you don't have the URL filtering subscription, I believe you can still create custom URL categories. Add "searchencrypt.com" and "*.searchencrypt.com" to a custom URL category and deny access to that category.
Another option if you don't have the URL filtering subscription: create a custom AppID signature. I configured one that looks for "searchencrypt.com" in the SSL Response Certificate context of the SSL decoder. Here's a screenshot with most of the information you'd need to create the custom application signature:
And here's a screenshot from the traffic log showing it blocking based on the custom AppID signature:
