Netskope Private Access (NPA) browser-based access lets users reach private web and non-web applications through a browser without exposing those apps directly to the internet.
Historically, Netskope documentation referred to Browser Access as a single solution for accessing Private Apps via a browser. This Browser Access capability is implemented using a reverse proxy and is already well known to many customers (for example, features such as Browser Access User Portal and Browser Access AnyApp). Netskope now supports two methods to enable browser-based access to private apps, which we collectively refer to in this article and its sub-sections as browser-based access:
- Browser Access: Reverse proxy based browser access to private apps (existing capability; feature names remain unchanged in the UI and documentation).
- Browser Access with Enterprise Browser: Forward proxy based browser access to private apps using the Netskope Enterprise Browser.
This section describes how these two browser-based options apply to different deployment scenarios.
Browser Access (reverse proxy) is well suited for zero-install, URL-based access to internal web apps, often for contractors or BYOD users, and can also be used to broker access to RDP and SSH when those services are published as NPA AnyApp Private Apps.
Browser Access with Enterprise Browser (forward proxy) can likewise be used to access both internal web apps and broker access to RDP and SSH via NPA AnyApp Private Apps, while additionally providing isolation and granular controls for browser sessions. Enterprise Browser apps can be used for both managed and unmanaged users based on your security and user experience requirements.
Use the following guides to configure each browser-based option: