Recently active topics

I am dismayed that upon seeing the below notice when logging into the tenant, the linked Help page says “The migration guide is still in progress and will be available soon “  Netskope should consider holding off doing this due to a lack of proper documentation  Policy Update: Automated Migration of Steering Exceptions Netskope is decoupling Steering Configurations from Proxy processing to provide more granular, visible control over traffic handling.What is changing? Automated Policy Creation: Starting in 136.0.0, Netskope will automatically convert existing steering exceptions into explicit SSL "Do Not Decrypt" and RTP "Allow" policies. No Traffic Disruption: Your current bypass behaviors and traffic flows remain identical. Easy Identification: Migrated policies will be prefixed with "ns-migrate" and logged under "Netskope Migration" in your audit trail. Non-standard Ports: Non-standard ports are no longer controlled by Steering Configurations and can be managed by Service Objects

The Netskope Cloud R136.1 hotfix documentation is here! New & updated articles are live on docs.netskope.com. The release notes are here: Netskope Release Notes Version 136.1.0Submit your feedback via docs.netskope.com.

Is there a way to report out what network location profiles exist and what the IP addresses they contain?  Bonus points if it can be tied to what SSL policies!

OverviewTo streamline troubleshooting, organizations often want to automate log collection (e.g., triggered automatically when a user submits a support ticket).Technical Note: The Netskope REST API v2 allows for the retrieval of logs already present in the tenant. However, the "Collect Logs" function in the Netskope UI relies on a proprietary signaling mechanism that is not currently exposed via a public API. To automate the initiation of log collection, organizations must use a remote execution solution (MDM/EDR) to run the nsdiag utility locally on the endpoint.The Automation WorkflowSince the process cannot be triggered via a Netskope API call, the workflow moves from the Netskope Cloud to your internal management infrastructure. Trigger: An automation engine (e.g., ServiceNow, Jira Automation) identifies a new ticket with a hostname. Execute: Your MDM (Jamf, Intune, Kandji) or EDR (Tanium, CrowdStrike) runs the nsdiag command on the target host. Local Bundle: The nsdiag tool ge

We are experiencing an issue where Cursor AI traffic stops working when routed through Netskope with SSL decryption enabled. Specifically, the Cursor agent fails to function when traffic is inspected via Netskope.For security reasons, we do not want to bypass or exclude the Cursor AI domains from inspection. We would like to understand if there is a recommended solution that allows Cursor to function properly without bypassing SSL decryption.Could you please advise on: Any best practices for handling similar AI/agent-based applications under SSL inspection As part of our troubleshooting, we attempted lowering the HTTP version to 1.0. While this has resulted in partial functionality for some users, the issue is not fully resolved and the agent remains unstable. 

Hi Community,Are you curious about what’s actually happening inside your "Google Drive" traffic?Currently, when the Application filter is set to Google Drive, the dashboard displays events from Google Shared Domains identified generally as "Google Drive". We’ve recently released a Connector Improvement that provides much deeper visibility. I am sharing the dashboard that generated the attached example report so you can see how to obtain a corresponding report for your own tenants and understand the impact this would have on your specific data landscape. The "Current State" vs. The "Improved State" Current State: The dashboard currently displays events from shared domains generally identified as "Google Drive". Improved State: Once the recently released Connector Improvement is enabled, these domains would no longer be identified as "Google Drive". Instead, they would be automatically assigned to the specific new application identified within the dashboard.  Initial Dimension of Impac

Netskope Log Streaming GCP Pub/Sub to CriblTo move logs from a GCP bucket to Cribl using Pub/Sub, you’ll essentially set up a "trigger" system. When Netskope drops a log file into your bucket, GCP will send a notification to a Pub/Sub topic, which Cribl will then "pull" to ingest the data.Since Netskope writes files to GCS, we will use a "Notification-Based Ingestion" strategy. This is the gold standard: GCP tells Cribl a file exists, and Cribl immediately goes and grabs it.Here are the step-by-step instructions to set this up: PrerequisitesNetskope NLS setup sending logs to a GCP Bucket The Service account you used for the NLS setup should have the following permissions Pub/Sub Subscriber & Viewer Storage Object Viewer Pub/Sub Subscriber GCP InfrastructureYou need a "Topic" to announce new files and a "Subscription" for Cribl to listen to.Create a Pub/Sub Topic: * Go to Pub/Sub > Topics in the GCP Console.Click Create Topic (e.g., netskope-log-notifications). Create a Subscri

Hi Team,Quillpad is showing unknow in CCL is it safe to allow this translation app to our users. In virus total I don't see any malicious tag to the application/website. Please check and suggest.   Regards,Zakeriya Shaikh

Hello Everyone, We are unable to export the user list from Netskope tenant. We have tried to export the user list from Security Cloud Platform → User management, but unable to fetch the export option to export the user list.Kindly confirm is there any option in the Netskope tenant to export the user list from the tenant.If not, kindly suggest any alternative method for the same.

We are facing one issue where users are sharing google docs from external domains eg: gmail.com to nykaa.com, and nykaa.com users are able to access the google docs or sheets on which they can paste /write the sensitive information.So how do we block this transaction with Netskope

Hi Team,We are currently facing an issue on 2–3 devices where the installation fails with the error:“Installation failed to download the configuration. Check your internet connection and try again.”Although the affected users have an active internet connection and no VPN is connected, the issue still persists. All configurations appear to be correct from our end.I have attached a screenshot of the error for reference.Has anyone encountered this issue before or have any suggestions on how to resolve it?  

Hello everyone,We've seen a few questions lately about the best way to handle Netskope Client upgrades when you have a mixed environment of non-persistent VDIs and traditional laptops. A common challenge is that the same user might use both, but the upgrade strategy needs to be different for each.Let's break down the problem and the best-practice solution. The Challenge: Different Needs for Different Devices  Non-Persistent VDIs: You can't use the standard auto-upgrade feature from your Client Configuration. Any update applied during a session gets wiped when the VDI reverts to its golden image. Upgrades need to be manual and controlled. Laptops: You want them to auto-upgrade. It’s the easiest way to keep your users on the latest client version and maintain your security posture with minimal effort. So, how do you disable auto-upgrades for VDIs while keeping them enabled for laptops, especially when the same user logs into both? The Solution: The autoupdate=off Installer Flag is Key!

Your Netskope Monthly Highlights – April 2026The latest updates, resources, and events – all in one place.Hi there,As part of our ongoing commitment to helping you get the most value out of your Netskope investment, we’re excited to bring you this month’s Netskope Highlights—your one-stop roundup of the latest product updates, expert content, and upcoming learning opportunities. 🚀 Product Release UpdatesRelease 136 is here!Explore this month’s key features and enhancements to ensure you’re getting maximum value from your setup.📄 Release Notes - April 2026 ✅ Pro Tip: Check for features relevant to your current configurations. ✅ Features not to miss out!This section highlights key innovations from the recent Netskope release that can significantly enhance your Adoption and Value Realization journey.Top 5 Highlights:AI Discovery : Netskope is excited to announce the beta launch of a new capability called AI Discovery. This provides end-to-end visibility over AI usage across your organiz

Hi all,The Mission: The Netskope User Research team is looking for hands-on Insider Threat Analysts for a deep-dive study. 🎯 WHAT WE WANT TO LEARN: How you detect, investigate, and respond to internal risksWhat behaviors/patterns you look for What data you collect Which tools are used Detailed Workflows on investigation & response👥 WHO SHOULD APPLY? Active Netskope Customers: You use Netskope as part of your security stack. Practitioners: You spend a significant portion of your week managing internal risks and conducting investigations. 💻 SESSION DETAILS: 60 min 1:1 via Zoom 🎁 RECOGNITION: $50 gift cardSIGN UP VIA THIS LINK: https://forms.gle/WL6vsZ8KRPt7wChB8

Hello! We are experiencing some issues with the Netskope Client failing to reconnect when our users move the LAN cable from their Laptops to their Docking stations. The Netskope client fails to connect anytime the connection is attempted from the docking station’s NIC. From the laptop’s onboard NIC no issues are encountered. Attempted means to remedy include the following but to no avail:Updated Docking Station Firmware to latest available Updated Driver for NIC on Dock as well as Docking station driver Reinstalled Netskope Client & Netskope Endpoint SDWAN ModuleI’ve sent out a preliminary inquiry on the same to our rep at Netskope and was just curious if anyone in the community had encountered similar issues and were able to work through them. If so could you suggest any possibly remedies? Thank you!Chris WarrenCybersecurity Analyst II

Hi All,Thank you for joining our recent webinar on “Unlocking Value from Recent Netskope Releases – March 2026.”For those who would like to revisit the session or couldn’t attend, you can access the recording here:👉  Link Session Highlights:Recap of key features from releases R133, R134, and R135 Deep dive into how these features work and the problems they solve Step-by-step guidance on configuration and enablement Live demos showcasing feature impact Resources and next steps to help you maximize valueWe’d greatly appreciate your feedback to help us improve future sessions. Please take a moment to complete the survey:👉  Link Thanks again for your time and participation. Best regards,Rohit Bhaskar

Hi all,The Mission: The Netskope User Research team is looking for hands-on Insider Threat Analysts for a deep-dive study. 🎯 WHAT WE WANT TO LEARN: How you detect, investigate, and respond to internal risksWhat data you collect Which tools are used Detailed Workflows on investigation & response👥 WHO SHOULD APPLY? Active Netskope Customers: You use Netskope as part of your security stack. Practitioners: You spend a significant portion of your week managing internal risks or conducting investigations. 💻 SESSION DETAILS: 60 min 1:1 via Zoom 🎁 RECOGNITION: $50 gift cardSIGN UP VIA THIS LINK: https://forms.gle/WL6vsZ8KRPt7wChB8

 Netskope Global Technical Success (GTS)How to Enable DLP on the ChatGPT Native macOS Desktop AppNetskope Cloud Version - 135 Note : This configuration and fix were tested only on ChatGPT macOS version 1.2026.048. OpenAI may change TLS pinning, remove the NSUserDefaults override, or update the compiled SPKI hash list in future releases. If ChatGPT updates, rerun the strings extraction command to verify the key remains in the binary and refresh the hash list before reapplying the fix.  OveriviewThe ChatGPT macOS desktop app implements TLS certificate pinning. When Netskope performs SSL inspection, it presents its own Root CA certificate  which ChatGPT does not recognise  and the app refuses to start with a certificate error.The standard fix is to add ChatGPT to a Cert Pinned App steering exception which bypasses Netskope entirely and gives zero DLP visibility. This guide documents an alternative approach discovered through binary analysis that allows full SSL inspection to remain active