The Netskope client has connected to Chennai Gateway but the https://notskope.com is showing that the traffic is not steering to Netskope. We have configured the Traffic steering policy with dynamic steering enabled, if we disabled the dynamic steering then if we select the “All traffic” means, the traffic is steering towards Netskope. If we select the cloud APPS only then the traffic is not steering to Netskope.
Any thoughts on this
Hi @MariaAlex ,
If you choose "Cloud apps" as the steering type, you need to specify which apps should go through Netskope. Only those CASB apps will go through Netskope. For example, if you've added "Amazon S3" to cloud apps, only Amazon S3 traffic will pass through Netskope. If you visit https://noskope.com, it won't be steered through Netskope because this URL isn't specified in cloud apps for steering.
The easiest way to check if traffic is going through Netskope is by looking at the certificate or checking the nsddebug log.
On Windows PowerShell:
Navigate to cd C:UsersPublic
etSkope.
Run the command: Get-Content .
sdebuglog.log -wait -tail 1
If the traffic is going through Netskope, the logs will indicate "tunneled." If not, they will show "bypassed."
If you haven't already registered, now is a good time to do so. After you register, you can post to the community, receive email notifications, and lots more. It's quick and it's free! Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
