This page describes known compatibility considerations for Netskope Enterprise Browser with security software, web applications, operating systems, and third-party tools.
Antivirus and Endpoint Detection and Response (EDR)
Some antivirus and EDR solutions may interfere with Enterprise Browser installation or normal operation. If you encounter installation failures, blocked network connections, or unexpected behavior, configure your security software to allow access to the following:
Windows file system paths:
- C:\Users\<USERNAME>\AppData\Local\Netskope\Browser
- C:\Users\<USERNAME>\AppData\Local\Netskope\NetskopeBrowserUpdater
- C:\Users\<USERNAME>\AppData\Local\Temp
- C:\Windows\Installer (MSI installation only)
Windows registry key:
- HKCU\Software\Netskope\Update
If installation continues to fail after configuring these exclusions, contact your security software vendor to verify that process injection scanning, memory scanning, or network inspection features are not blocking browser startup or update processes.
User-Agent Compatibility
Enterprise Browser sends its own User-Agent string, which identifies it as a Netskope browser rather than standard Chrome. Some web applications inspect the User-Agent and may block or degrade the experience for unrecognized browsers.
Google Meet — Anonymous Join Blocked
Issue: Users who are not signed into a Google account cannot join Google Meet sessions from Enterprise Browser. They receive an error when attempting to join. Users who are signed into a Google account are not affected.
Root cause: Google Meet’s ResolveMeetingSpace API returns a 403 Forbidden response when the Enterprise Browser User-Agent is detected and the user is unauthenticated.
Workaround: Ensure that users accessing Google Meet through Enterprise Browser are signed into a Google account. Anonymous meeting join is not supported from Enterprise Browser.
Note: This is a Google-side restriction based on User-Agent validation. There is no configuration in the admin console to override it.
Intermittent Access Errors on Third-Party Websites
Issue: Some websites with strict browser validation policies (CDNs, security filters) may intermittently reject Enterprise Browser connections with 401 Unauthorized or 403 Forbidden errors. This has been observed on sites such as FedEx package tracking but may occur on any site that validates the browser User-Agent before serving content.
Root cause: Third-party servers that enforce an allowlist of known browser User-Agent strings may reject the Enterprise Browser User-Agent non-deterministically.
Workaround: There is currently no customer-configurable workaround. If a specific site is consistently failing, contact Netskope support to investigate whether a site-specific policy adjustment is possible.
Netskope Client (NSClient) Coexistence
Enterprise Browser can run alongside the Netskope Client (NSClient) on desktop and mobile platforms. On iOS, coexistence requires additional configuration in the Netskope console:
- Go to Security Cloud Platform → App Definition → Certificate Pinned Apps.
- Add a Certificate Pinned Application entry for iOS with the relevant management plane domains.
- Configure steering exceptions for the appropriate user groups.
Without this configuration, traffic may be double-steered or connection errors may occur on iOS.
Web Application Compatibility
Enterprise Browser is built on Chromium and supports the same web standards and APIs as the corresponding Chromium release. Most modern web applications work without modification.
Known limitations:
- Google Docs: Data Masking does not apply to Google Docs content because Google Docs renders using an HTML5 Canvas engine rather than standard DOM text nodes.
- Google Meet (anonymous join): See the User-Agent Compatibility section above.
- WebRTC screen sharing (iOS): Screen sharing interception for WebRTC is not supported on iOS. Screenshot and Screen Sharing Protection applies to native screenshot and screen recording APIs only.
- Screenshot protection — bypass scenarios: Screenshot and Screen Sharing Protection may not be effective in the following situations on Windows and macOS: kernel-level screen capture tools; screenshots taken from Chromium DevTools; browser extensions using internal screen-sharing APIs; on macOS, duplicating a protected tab or rapidly resizing the window may expose a brief unprotected frame.
- Android Overview/Recents screen: On Android, the system-level Screenshot and Selection features in the Overview screen cannot be disabled by the app. Content visible in the Overview screen may be captured via this system feature.
- PDF Viewer: The native Chromium PDF viewer does not support Data Masking.
- Export as PDF (Print → Save as PDF): In some applications such as Microsoft 365, the Print menu’s Export as PDF option triggers a download not captured by the Print blocking policy. To block this, create a Real-Time Protection DLP policy to block downloads for the relevant application.
- HTTP traffic: Enterprise Browser only steers HTTPS traffic through the Netskope cloud. HTTP traffic is not inspected.
Captive Portals
Connecting to networks that use captive portals (for example, hotel or airport Wi-Fi) may require completing authentication in a standard browser first:
- Open Safari or another standard browser and complete the captive portal sign-in.
- Once the device has internet access, switch to Netskope Enterprise Browser.
Extension Compatibility
- Some extensions may not be discoverable in the Extension Governance policy tool by name or ID. Known examples include Google Docs Offline and certain security extensions. Use the full Chrome Web Store extension ID when configuring policies for these extensions.
- Extensions that use internal Chromium screen-sharing APIs may bypass Screenshot and Screen Sharing Protection.
Operating System Version Requirements
Enterprise Browser requires the minimum OS versions listed in System Requirements. Running on unsupported OS versions may cause unexpected behavior or crashes.
To learn more: System Requirements | Performance Issues | Enterprise Browser Installation and Troubleshooting