Your company has many users that are remote and travel often. You want to provide the greatest visibility into their activities, even while…

The Netskope Client is a software agent installed on endpoint devices (laptops, mobile phones) that steers traffic to the Netskope Security Cloud. This method is specifically designed for roaming and remote users, as it provides consistent visibility and policy enforcement regardless of the user's physical location or network connection. By capturing traffic directly from the endpoint, it ensures the greatest visibility into user activities, whether they are in the office, at home, or traveling, which directly addresses the scenario's requirements.

A. Use proxy chaining: This method is used to forward traffic from an existing on-premises web proxy to Netskope. It is not suitable for individual remote users who are not on the corporate network.

C. Use an IPsec tunnel: An IPsec tunnel creates a secure, site-to-site connection between a network edge device (like a firewall at an office) and the Netskope cloud. It is not designed for individual, mobile endpoints.

D. Use a GRE tunnel: Similar to IPsec, a GRE tunnel is a site-to-site method for forwarding traffic from a fixed network location to Netskope and does not support individual, traveling users.

1. Netskope Official Documentation

"Traffic Steering": This document outlines the various methods for directing traffic to the Netskope Security Cloud.

Section: "Steer Client Traffic": It states

"The Netskope Client is the preferred method to steer traffic to the Netskope Cloud for managed devices. The Client provides the ability to steer all traffic from a device for inspection... The Client is ideal for roaming users that are on and off the corporate network." This directly supports the use of the Netskope Client for remote and traveling users.

Section: "Steer On-Premises Traffic": This section describes IPsec and GRE tunnels as methods to "steer traffic from an entire office or network segment to Netskope

" confirming they are for fixed locations

not individual roaming users.

Section: "Explicit Proxy": This section details proxy chaining

explaining it is for environments that "already have a proxy deployed and want to chain to Netskope." This confirms it is not a solution for individual endpoints off the corporate network.