Netskope Global Technical Success (GTS)

Google Chrome - Blocking Traffic from Chrome Extensions

Netskope Cloud Version - 126

Objective

Block Google Chrome Extensions Traffic

Prerequisite

Netskope Next-Gen SWG license

Context

The business use case is to block all traffic originating from Google Chrome extensions, regardless of the destination.

Do You Know?

• The origin of all traffic which is being generated by Google Chrome extensions starts with ‘Chrome-extension’

Configuration

Step 1 - Create a HTTP Header Profile

Path: Netskope Tenant UI >>> Policies >>> Profiles - - - HTTP Header >>> New HTTP Header Profile

Step 2 - Create a Realtime Protection Policy

Path: Netskope Tenant UI >>> Policies >>> Realtime Protection Policy >>> New Policy

Verification

• To perform testing, I installed Grammarly on Google Chrome and here are the results

Author Notes

• With the controls implemented as described above, there will be no impact on regular browser traffic. For example, you can still access  grammarly.com directly through the browser without any issues.

• It is recommended to review -

Terms and Conditions

• All documented information undergoes testing and verification to ensure accuracy.
• In the future, it is possible that the application's functionality may be altered by the vendor. If any such changes are brought to our attention, we will promptly update the documentation to reflect them.

Notes

• This article is authored by Netskope Global Technical Success (GTS).
• For any further inquiries related to this article, please contact Netskope GTS by submitting a support case with 'Case Type – How To Questions'.