Enterprise Browser FAQs

This page contains the latest FAQs and best practices for Enterprise Browser (EB) version 1.0.

What if I had a previous version of the Enterprise Browser and I have problems installing a new version?
Which operating system do you support?
Which SSO/SAML system do you support?
Can I use the Enterprise Browser with the Netskope Client?
How can I resolve performance issues or slow loading times?
What steps should I take if a web site or application doesn’t function as expected?
Why am I experiencing compatibility issues with certain enterprise tools?
How does POP selection work for Enterprise Browser?
Does the Enterprise Browser support policies?

I have a previous version of EB and I’m having trouble installing a new version

If you installed an Alpha or Beta version of EB, you must clean up your system before installing the GA version. NOTE: installing the GA version will delete every profile that you have set up, including cookies and saved passwords.

Which operating system do you support?

For GA, EB supports:

Windows OS: Windows 10/11 (Intel)
Mac in Beta (Intel/ARM)

Which SAML/SSO do you support?

Enterprise Browser relies on Cloud Explicit Proxy and Forward Proxy configurations, therefore any supported SAML/SSO is supported. Several providers were tested during the Alpha and Beta releases. The following topics provide Netskope specific set up steps:

Can I use the Enterprise Browser with the Netskope Client?

The main use case for EB is unmanaged devices, both solutions can work together with the proper configuration.

Configure Enterprise Browser and Netskope Client

1 Navigate to Configuration > Security Cloud Platform > Traffic Steering > Edit Configuration. Confirm the following: “Bypass exception traffic at Client”

2 Configuration → Security Cloud Platform → Traffic Steering → App Definition → Certificate Pinned Application

3 Create a “New Certificate Pinned App” as follows:

4 Configuration → Security Cloud Platform → Traffic Steering → Exceptions. Add a “New Exception”, selecting the pinned app created in the previous step.

Repeat the steps above for updater.exe including *.<MP>.goskope.com in Custom App Domains. MP is based on the location of your account.

How can I resolve performance issues or slow loading times?

Try the following:

Check your internet connection, browse the same web sites with an additional browser, verify if you still encounter performance issues or slow loading times.
Close any unnecessary applications consuming system resources.
Verify that no enterprise-level restrictions or firewalls are causing delays.

What steps should I take if a web site or application doesn’t function as expected?

Verify that you have connectivity to other web sites and the Enterprise Browser is properly working for other cases.
Use an alternative browser to identify if the issue is with the non-functioning web site or application is browser-specific.

Why am I experiencing compatibility issues with certain enterprise tools?

Compatibility issues may arise due to specific configurations. Verify that you have access with your usual access method but not with the Enterprise Browser and review the policy settings to ensure there are no conflicts with the Enterprise Browser permissions.

How does POP selection work?

It helps to think about what Netskope has to do in order to locate the optimal DC. Given that endpoints need to establish a TLS connection(s) to a DC in the NewEdge Security Cloud, they have to discover where to connect before initiating any connections.

This is done in one of two ways, depending on whether your account has the Netskope Client running on the endpoint or not. Clientless methods (like EB, CEP) rely on DNS resolution for optimal DP location which is why DNS lookup doesn’t always assign the “expected DP”.

Does Enterprise Browser support policies?

The Enterprise Browser provides options for managing extensions through policy configurations. These options allow companies to control which extensions are installed, whether users can modify them, and how permissions are handled. These are the main policies:

Extension Allowlist: Defines which extensions are permitted. Users can install only extensions on this list.
Extension Blocklist: Prevents the installation of specific extensions or all extensions if set to "*" (wildcard). By default in our configuration.
Force-Installed Extensions: Automatically installs and enforces specific extensions, preventing users from disabling or removing them. It happens once the policies are loaded into the browser and rebooted.

Enterprise Browser version 1.0 does not support configuring extensions through the UI. An Extension Manager UI is planned and on our roadmap, but there is no confirmed release date yet. If a predefined list of extensions is a need, contact your Netskope account team to make a request.

Enterprise Browser FAQs