Quick Start

There are two fundamental steps required to deploy Netskope in your environment:

This is typically done by integrating with your Identity Service (like Azure AD, Okta) using SCIM (API), or synchronizing your on-premises Active Directory using the Directory Importer Tool.

Having users and identity attributes in the Netskope platform is critical for two reasons:

There are numerous methods to steer traffic to the Netskope cloud for enforcement, but the primary one is the Netskope Client. This is a piece of software deployed to a user’s device that will:

The Netskope Client is incredibly lightweight as all inspection happens within the Netskope cloud: There is no traffic processing that occurs on the user machine.

The default configuration of the Netskope Client is to steer web traffic to Netskope for inspection, so there is no baseline configuration needed to get the Client to function out of the box.

This guide covers everything that a typical enterprise will need to do to get Netskope up and running effectively in your environment, including:

• Access the Admin Console
• Create Local Administrators
• Integrate an Identity Provider (IdP)
• Check Firewall Policy
• Bypass Netskope from your VPN
• Configure a Steering Profile
• Add Bypasses in Netskope
• Configure Netskope Client Settings
• Deploy the Netskope Client
• Allowlist the Netskope Client
• Validate Traffic Steering
• Create and Validate a Security Policy
• Next Steps