Recently active topics

While we are able to successfully manage the customer's Chrome extensions through Netskope, we are encountering challenges with the extension updates due to dynamic URLs. We explored using regular expressions (regex) as a workaround, but this is not supported within the current URL list or destination profile settings

Hello Team,I would like to restrict access to Perplexity AI based on the following requirements:Block access for unauthenticated users. Allow access only to users who sign in with the company's authorized instance ID. Block access to any other instance IDs after authentication.Could you please provide guidance on configuring the necessary policies in Netskope?Thank you.

Hello Team,We are observing an issue while deploying applications through Microsoft Intune. The Netskope Client takes significantly longer to download and become available on the end-user machine compared to other applications.Once the Netskope Client is downloaded, the remaining applications are downloaded successfully.Could anyone help us understand why the Netskope Client takes longer to download during deployment via Microsoft Intune? Are there any specific configurations, prerequisites, or troubleshooting steps we should check to resolve this issue?Any suggestions or insights would be appreciated.

I am looking for best-practice advice on how to tune our inline Real-Time Protection policies to eliminate high-volume DLP false positives caused by automated tracking and analytics scripts logging standard website content. Because the script scrapes raw elements directly from the page framework, the payload packages underlying site styling code and public reference strings side-by-side. Our Predefined PII rule triggers on a standard threshold count, but a single tracking transaction easily multiplies that count and floods our incident logs because the inspection engine captures things like Raw CSS Styling Frameworks: The payload packages background font layout code from icon libraries (e.g., .fa-square-1{--fa:"\\e256"} ... .fa-birthday-cake,.fa-cake).       75\"}.fa-square-1{--fa:\"\\e256\";--fa--fa:\"\\e256\\e256\"}.fa- birthday -cake,.fa-cake,.fa-cake-candles{--fa:\"\\f1fd\";--fa--fa:\"\\f1f ...Kolodzey, Evan Hughes\",\"Publication date\":\"2026- 07-10 \",\"Name Public Directory / A

A running Netskope Client service does not necessarily mean that traffic is being steered as expected.Administrators may see the agent/services running normally while the client is not effectively steering traffic due to conditions such as:Enrollment or token issues User not included in the applicable steering configuration/group Client disabled Other user-specific enrollment or client-state issuesTo improve visibility, we are leveraging: nsdiag.exe -fwhich return the result ; Client status:: enable./disableWe collect this result through our endpoint/client management custom inventory and create a report showing the actual reported client status across managed endpoints.

Hi Community, To simplify proxy processing, Netskope is decoupling Steering Configuration from proxy processing.Currently, under the Coupled Proxy model, a Steering Exception acts as both a steering bypass and a proxy bypass, which can cause unexpected SSL decryption and Real-time Protection (RTP) behavior. With the Decoupled Proxy model, Steering Exceptions function solely as steering bypasses, allowing the Netskope Proxy to evaluate SSL and RTP policies independently. I am sharing the dashboard that generated the attached example report (Steering_Decoupling_Migration_Traffic_Demo) so you can obtain a corresponding report for your own tenants and evaluate how this migration will affect your specific traffic landscape. UPDATES & IMPROVEMENTS: Enhancements to the DashboardTo help you troubleshoot and analyze non-standard port traffic more effectively, I have made key updates to the dashboard.[!NOTE] Action Required: If you previously imported this dashboard, please download the upda

Dear Netskope: Why is there always a serious miss-communication between the new release documentation and other services within Netskope? There is a new category, paste sites, which specifically lists pastebin.com, controlc.com but NO mention of sites changing categories on notify.netskope.com.  I can’t run a report on how this is going to affect my organization unless I have this information, which possibly leads people to not be able access sites 

Event Follow-Up: Unlocking value from recent Netskope releases Date: October 6, 2026 (APAC / NAM) , October 7, 2026 (LATAM)Topic: Unlocking value from recent Netskope releases 🔍 Summary:Thank you to everyone who attended our  webinar, “Unlocking value from recent Netskope releases”.The webinar covered a recap of key technical features from recent releases that you might have missed. We hope you found it insightful and valuable. During this session, we covered the below topics : Deep dive into how key Netskope features work and the problems they solve. Step-by-step guidance on configuring and enabling the most impactful features Demo of selected features to show their impact in action Resources, documentation, and next steps to help you maximize value 🎥 Webinar Recording:If you missed the session or would like to revisit the content, you can watch the recording below:APAC Recording NAM Recording LATAM Recording💬 Continue the Conversation:Have questions or want to dive deeper into the

Hi Team,We are observing inconsistent UBA alert generation in our Netskope tenant for multiple failed login attempts to Naukri.com.In one instance, an alert was generated when a user had 3 failed login attempts within approximately 15 minutes. However, in another instance, the same user had 10–20+ failed login attempts within just 6–7 minutes, but no alert was generated.We would like to understand how Netskope UEBA detects and generates alerts for repeated failed login attempts.Is there a specific threshold or detection logic for this type of activity? Could the behavior differ depending on the application, browser, desktop client, or authentication method? Is this use case covered under the UEBA Standard license? Are there any known limitations or configurations that could explain this inconsistent behavior? Has anyone encountered a similar issue or can share insights into how this detection works in Netskope?Any guidance or suggestions would be greatly appreciated.Thanks!

Hello Community,We have a client who uses Amazon Connect as their contact center solution. The agents also have Netskope agents installed. According to our monitoring system, about 3.5% of calls are considered to have Poor Audio, and we are investigating possible causes. When we checked the Netskope Steering exceptions, we currently have some steering exceptions configured, however, the one I’m concerned about is regarding the STUN (Media) UDP 3478 traffic. According to the Amazon documentation (see Set up your network to use the Connect Customer Contact Control Panel (CCP) - Amazon Connect Customer), we need the following FQDN allowed:TurnNlb-*.elb.region.amazonaws.com When we check our steering profile configuration, this is the FQDN exception is configured:*.amazonaws.comFrom what I have been told, and by what I read in the Netskope documentation for Steering Profile Exceptions, it states:“Wildcard domains (e.g., *.example.com) include the root domain and all subdomains.”However, in

Thank you for joining our recent technical recap webinar!Whether you want to rewatch a specific feature configuration or share the highlights with your team, you can access the full session here:👉 Webinar Recording Here is what we covered in the session: Release Deep Dive: Breakdown of key technical updates across R139, R140, and R141, focusing on how they address common operational challenges. Step-by-Step Configuration: Setup and configuration walkthroughs for the highest-impact features. Recorded Demos: Demos showing these capabilities live in action. Resources & Next Steps: Links to relevant documentation to help you quickly implement these updates.

Thank you for joining our recent technical recap webinar!Whether you want to rewatch a specific feature configuration or share the highlights with your team, you can access the full session here:👉 Recording Link Here is what we covered in the session: Release Deep Dive: Breakdown of key technical updates across R139, R140, and R141, focusing on how they address common operational challenges. Step-by-Step Configuration: Setup and configuration walkthroughs for the highest-impact features. Recorded Demos: Demos showing these capabilities live in action. Resources & Next Steps: Links to relevant documentation to help you quickly implement these updates.

Your Netskope Monthly Highlights – October 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 142.0.0 is here! Explore this month’s key features and enhancements to ensure you’re getting maximum value from your setup.📄 Release Notes - October 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 Highlights:1. Standard FeaturesCloud Firewall Consolidated DNS Events: Generates one DNS event per transaction instead of separate request and response events. This reduces dupli

Hi,I would like to block Generative AI applications. Users should not be able to submit prompts without logging in. Users should be allowed to access and use Generative AI applications only after successful authentication. However, they should be able to use any instance ID, such as Gmail, a company account, Outlook, Yahoo, etc. Could any one  help on the best way to configure this policy?

Recently at login this new “SCALE” adoption guide has started popping up:  Apparently Marketing, or whoever came up with this idea, haven’t considered the fact, that some customers might actually have been using the product for ages…...

OverviewThe Netskope data connector for Microsoft Sentinel (Content Hub solution Netskope Data connector) now includes a Netskope Client Status connector. It ingests Netskope Client device status records into your Sentinel workspace through the Codeless Connector Framework (CCF) REST API poller, so you can monitor the health and posture of your Netskope Client fleet alongside the rest of your security telemetry.The solution also ships with:1 workbook: a Client Status dashboard 2 analytics rule templates: detections for users disabling Netskope protectionThis article covers why this data matters, the permissions you need, how to set up the connector, and what you get once data starts flowing.Why do you need Netskope Client Status data?Netskope alerts and events tell you what users and devices did. Client Status data tells you whether the Netskope Client that enforces your policy is installed, running, healthy and connected on each endpoint. Without it, there are blind spots:Coverage gap

Has anyone faced any problem related to email DLP where any code can be leaked via email if it is tagged between HTML tags?

We are trying to implement DLP on our MacBooks. First of all, it is unable to protect our source code and allowing randomly on some websites. Secondly, the source code is getting leaked via email if sent between HTML tags.

The Netskope Client Golden Updates for version 141 is here: Golden Release Updates Subscription.  This document provides a summary of the new features, fixed issues, and other Netskope Client updates introduced between versions 138 and 141.

Deploy Netskope AI Guardrails with Kong AI GatewayConfiguration guide: sending prompts from Kong to Netskope for evaluationIntegration Guide: AI Guardrails on DemandThis guide covers one thing: configuring Kong's AI Custom Guardrail policy so that every prompt passing through your Kong AI Gateway is sent to Netskope AI Guardrails for real-time evaluation, and blocked if it violates your Guardrails profile. It assumes you already have (or are about to set up) the two systems below — it does not walk through deploying them.RequiredNetskope tenant with the AI Guardrails license enabled Kong Konnect account with AI Gateway accessPre-workIf you don't already have these deployed, set them up first using Netskope's and Kong's own documentation:Netskope AI Guardrails appliance (Virtual Private Edge):  CPU version https://github.com/netskopeoss/netskope-guardrails-standalone GPU version https://github.com/netskopeoss/netskope-guardrails-gpu-standalone Kong AI Gateway: developer.konghq.com/ai-

Netskope AI Guardrails on DemandAWS deployment walkthrough using CloudFormationThis guide walks you through deploying the Netskope AI Guardrails on Demand appliance into AWS with a single CloudFormation stack, registering it with your Netskope tenant, and testing it. AI Guardrails on Demand ships as a Netskope Virtual Private Edge (VPE) virtual appliance. It scans AI prompts and responses through an API, so an AI gateway or agent you already run can call it and enforce the verdict.Beta. AI Guardrails on Demand is a Beta feature. Ask Netskope Support or your account team to enable it for your tenant and to share the VPE appliance AMI with your AWS account. The Stacknetskope-guardrails-standalone What the stack buildsOne aws cloudformation deploy creates everything below. No existing network is required.A new VPC with an internet gateway, two public and two private /24 subnets across two Availability Zones, one NAT gateway, route tables and an S3 gateway endpoint. The VPE appliance in an

Hi,I want to block PWA in web browser. What and how can I apply policies.

The Netskope Cloud R142.0.0 documentation is here! New & updated articles are live on docs.netskope.com. The release notes are here: Netskope Release Notes Version 142.0.0.The key new or updated feature is:Netskope Client SteeringNew Netskope Client UISubmit your feedback via docs.netskope.com.

The AgentSkope Marketplace announcement covered what the Marketplace does, and a shorter companion post walks the arithmetic. This is the complete version, for anyone who wants the mechanics rather than the summary. The same point came back from customer after customer. We want to consume everything you are building, they told us, but our procurement can't keep pace with your AI innovation. The constraint was never appetite. It was the purchasing motion itself. Three roles share the work. A Decision Maker estimates, purchases and renews credits. An Allocator distributes what was purchased and adjusts those allocations over time. A Practitioner runs the agents day to day. I'll follow two agents through all of it. The model You make one commitment, held as a pool of capacity credits. A credit is the funding unit. Every agent converts credits into its own unit of work at its own published rate, so an allocation sets how much work that agent can do in a calendar month.Capacity is monthly.