Recently active topics

Dear Community Members,We are excited to announce the beta release of the Netskope Identity Dashboard, your new unified entry point for the Netskope applications and services your organization uses. The Identity Dashboard brings application access, profile management, and user administration together in a single, streamlined interface — making it easier than ever to get to the resources you need.As a user of the platform, your feedback is invaluable in helping us shape the experience. If you encounter any issues or have suggestions, please reach out to ciam@netskope.com.What Is the Netskope Identity Dashboard?The Identity Dashboard provides a single sign-on experience across connected Netskope platforms, including:Notification Portal Academy Support Community Partner PortalsSign in once at id-dashboard.netskope.com and access any connected application throughout your session — no repeated logins required. What's NewUnified Application AccessOne launchpad for Netskope applications avail

In our environment, we found that M365 Copilot Cowork is not working when user’s connection is protected behind Netskope. Other customers using Netskope seems to be reporting the same issue as well.Microsoft’s documentation on network requirements for Copilot Cowork has been published here Cowork network endpoints (Frontier) | Microsoft Support and they cited requirements around supporting long-lived connection. Microsoft support has also shared an internal document that mentioned about the use of Server-Sent Events--which based on Internet research is not something SASE/SWG products support by default.Do you have a recommended configuration that we can use to make Copilot Cowork to work behind Netskope? Any plan to make this configuration to be part of the standard M365 policy from Netskope so that we don’t need to request a configuration change in our company? 

how to bypass loom desktop  application ?

Dear Partner fellows,We have been informed by the Support team that if you create cases on behalf of customers, the SLA associated with the customer’s purchased support level will not be honored.Quoted from Support, with company information masked:“Also, regarding the SLA request, the reason is that the case was raised by a vendor account rather than the customer.Please sync with your account team for any further queries.”

Netskope Global Technical Success (GTS)Anthropic Claude - Access to Corporate Instance Only (via Instance Detection) Netskope Cloud Version - 135 ObjectiveAnthropic Claude - Access to Corporate Instance Only (via Instance Detection) PrerequisiteNetskope Next-Gen SWG license ContextCustomers licensed to use Anthropic Claude may require that access be restricted to users authenticated with approved corporate domain accounts. Any attempts to access Anthropic Claude using accounts from non-corporate or unauthorized domains should be blocked.This knowledge base article explains how to achieve this use case using Netskope CASB Instance Detection. Author NotesIf the core business objective is to allow access only to the Corporate Anthropic Claude instance and block all other instances, please follow the KB articles listed below.However, if the business objective is to allow access to the Corporate Anthropic Claude instance while permitting a few exceptions for specific users, please continue

Netskope API logs with CrowdStrike NG-SIEMThis guide walks through ingesting Netskope Events and Alerts logs into CrowdStrike NG-SIEM using the Netskope Security Service Edge Data Connector and the Netskope API v2 Data Export endpoint.PrerequisitesAdmin access to both Netskope and CrowdStrike tenants Netskope API v2 Data Export endpoint URL for your tenant (typically https://<tenant-name>.goskope.com) Netskope API token1. Log into your Netskope tenant as an administrator.2. Navigate to Settings > Administration >Administrators & Roles.3. Create a new service account with the role Netskope Cloud Exchange or equivalent. This account must have read permissions for Events and Alerts logs.4. Generate an API token for this service account. Copy and store this securely—you will need it in the next section.  CrowdStrike Data OnboardingGo to your CrowdStrike tenant > NG-SIEM >  Data onboarding. Add connection Filter Vendor to Netskope and select the Netskope Security Servi

Hello Team,We were trying to automate sending user invites over email which we are currently doing manually using as per below KB. Can Netskope team develope an API endpoint to send user invites over email.Sharing the documentation of the Netskope User Invite process which we are trying to automate but not able to find API endpoint to perform the task.https://docs.netskope.com/en/netskope-client-enrollment-using-email-inviteWe have also raised a Netskope case - 00643908

Team,We are facing an issue with GitHub access control, where we are unable to restrict access to Enterprise accounts only and block access through personal or external domains.During our investigation, we observed that the instance is identifying the user as IRIS_mansi.mittal instead of the corporate email address (mansi.mittal@irissoftware.com). Due to this, we are unable to apply the required controls based on the enterprise domain.We need assistance in understanding why the instance is capturing the username in this format and what configuration or solution can be implemented to enforce access only for Enterprise accounts while restricting personal or external accounts.Please help us with the recommended approach to resolve this issue.

Overview This guide shows how to stream Netskope alerts and events into Microsoft Sentinel.The connector is called Netskope Alerts & Events Connector (via Blob Storage). Netskope publishes it. It ingests alerts and events logs from Netskope Log Streaming into Microsoft Sentinel via Azure Blob Storage, using the Microsoft Sentinel Codeless Connector Framework (CCF).The data flow does not push logs straight into Sentinel. Netskope Log Streaming writes logs to an Azure Blob Storage container. Sentinel then reads those blobs and writes the records into the Log Analytics table NetskopeAlertEvents_CL.This article is based on the connector's own deployment template (netskope_alert_events_log_streaming.json). UIs in Netskope and Azure change over time, so verify each screen against current documentation as you go.How it works (architecture)The pipeline has three stages.Netskope Log Streaming sends Alerts & Events logs to an Azure Blob Storage container. Azure infrastructure signals new

Hi all, just reposting this in the ZTNA channel.The script allows for automated deployment for Netskope Private Access Publishers in AWS using CloudFormation. I updated the script to support the latest publisher and Ubuntu version.https://github.com/Mitsj0l/Netskope-ZTNA-Publisher-AWS-CloudformationIf you are interested in this you might also want to checkout: Copy from the GIT:This repository contains:netskope-publisher.yaml netskope-parameters.json nsk-deployment.shThe deployment flow is:CloudFormation creates the AWS resources. User data downloads nsk-deployment.sh from S3. The script creates the Publisher in Netskope. The script retrieves the registration token and registers the Publisher. Optional post-registration steps can run automatically: Browser Access AnyApp enablement System update and publisher image upgrade sensitive artifact cleanup

Hello Everyone,Hope All are doing well.I have some query regarding SAML-Forward Proxy Secure Enrollment..We’ve successfully completed the integration of Netskope Forward Proxy with Microsoft Entra ID (SAML), and everything is functioning as expected.Configuration Summary Microsoft Entra ID Created Enterprise Application Completed SCIM Provisioning Verified user synchronization on Netskope Configured Single Sign-On (SAML) for Netskope Forward Proxy Netskope Configured SAML Forward Proxy and exchanged certificates successfully Tested the configuration using the SAML Forward Proxy test button — validation completed successfully ✅  Client Enrollment BehaviorAfter deploying the Netskope Client agent, users are prompted to authenticate using Microsoft Entra ID credentials via SAML. During the enrollment process, however, the configuration download fails, displaying an Enrollment Error message.To isolate the issue, we temporarily disabled Secure Enrollment under

Dear Netskope Community Members, Thank you for tuning in (or signing up) for the second session of our SSPM Webinar Series: From Baseline to Execution.Whether you want to revisit a specific strategy or catch up on what you missed, we've got you covered. 🎥 Watch the RecordingYou can access the full replay and presentation slides right now:👉 Recording Link 📋 Quick Recap: What We Covered During this session, we shifted our focus from high-level introductions to hands-on execution, specifically exploring how to drive consistent and scalable SaaS security. Key takeaways included: Defining & Implementing Baselines: How to establish a strong SaaS security foundation. Policy Configuration: Best practices for strict enforcement without disrupting workflows. Continuous Monitoring: Operationalizing SSPM to catch drift and vulnerabilities in real time. Compliance Alignment: Mapping your SSPM strategy directly to your organizational security goals. 💬 Share Your Thoughts (Quick 1-Minut

 The 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 138 is here!Explore this month’s key features and enhancements to ensure you’re getting maximum value from your setup. 📄 Release Notes - June 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:Securing MCP communications with AI gateway: This feature allows the Netskope AI Gateway to parse Model Context Protocol (MCP) traffic, acting as an intermediary that applies security controls between AI agents (MCP client

This post extends the existing integration guide: Integration: Web Transactions from Netskope Log Streaming to Microsoft SentinelThe original guide walks through the full setup: streaming Netskope Web Transaction logs to an Azure Blob container and ingesting them into Microsoft Sentinel through the Codeless Connector Framework. Read that first if you have not deployed the connector yet. This follow-up covers one thing: updating an existing deployment to capture the new fields that come with the Netskope Web Transaction Universal Format log. What changed in Universal Format Universal Format adds 51 new fields to the Web Transaction log. The connector was updated to carry them.  Item Before After Fields in the log line 146 197 Columns in NetskopeWebTransactions_CL 147 198  The table column count includes the built-in TimeGenerated column, so it is one higher than the field count. The change is additive. No existing field

Hello Everyone,I am currently working on a requirement to block the chat feature on X.com. I have attempted to restrict access by blocking relevant URLs and applying regex patterns; however, these approaches have not been successful.I also tried identifying the exact destinations used by X.com for its chat functionality, but was unable to pinpoint them.Could anyone please assist or share guidance on how to effectively implement this use case?Thank you in advance for your support.

Are their plans to fully support Linear (linear.app) as a steered app, so I can build real-time CASB DLP policies for it? Or, will you be supporting it as a NextGen CASB API app? Thx

The Netskope Cloud R138.0.0 documentation is here! New & updated articles are live on docs.netskope.com. The release notes are here: Netskope Release Notes Version 138.0.0.The key new or updated feature is:Netskope Client SteeringEnhanced Selection for Golden Monthly ReleasesSubmit your feedback via docs.netskope.com.

Netskope Global Technical Success (GTS)Anthropic Claude - Access to Corporate Instance Only (via Header Insertion) Netskope Cloud Version - 135 ObjectiveAnthropic Claude - Access to Corporate Instance Only (via Header Insertion) PrerequisiteNetskope Next-Gen SWG license ContextCustomers licensed to use Anthropic Claude may require that access be restricted to users authenticated with approved corporate domain accounts. Any attempts to access Anthropic Claude using accounts from non-corporate or unauthorized domains should be blocked.This knowledge base article explains how to achieve this use case using Netskope Header Insertion. Do You Know?Anthropic assigns an Org ID to all their Organizations customers. Where to find the Organization IDConfigurationConfigure Header InsertionPath: Netskope Tenant UI >>> Settings >>> Manage >>> Header Insertion anthropic-allowed-org-ids VerificationValidate Header Insertion configurationTry to login via any other accountCont

Hi all: Is anyone out there running WSL Version two and using Netskope? 

Hello Everyone,I have a query regarding Netskope with Sensitivity Labels for Email DLP.We’ve successfully integrated Netskope with Sensitivity Label Integration so that all labels are published into Netskope. For Cloud and Web traffic, DLP enforcement is working perfectly with label‑based rules.Current Email DLP Setup Created DLP Entities, Rules, and Profiles for all labels: Public, Restricted, Secret, Top Secret. For Word documents, we extracted metadata via File → Info → Properties → Advanced Properties → Custom tab. And created a Regex Entity. Example: ClassificationContentMarkingHeaderText.*Restricted Used these regex entities in SMTP DLP policies. Real‑time protection policy adds headers for enforcement: X-Netskope-Action: Block This works fine for Word attachments  (Emails) — detection and enforcement trigger correctly. What I’ve Already Tested GUID‑based approach: Extracted GUIDs from the MIP portal and created a custom regex Entity for e.g.: MSIP_Label_4119f1cb-5a0c-41ad-

OverviewA continuation of Sending Alerts and Events to Microsoft Sentinel using the Codeless Connector Platform.The first article set up the Codeless Connector for a single Netskope tenant. This post extends it. It sends alerts and events from several Netskope tenants into one Microsoft Sentinel workspace, and it labels each record so you can tell the tenants apart.If you have not read the single-tenant article, start there. The base ideas carry over: the Codeless Connector Framework, the RBACv3 service-account token, and the REST API index. Architecture Each Netskope tenant sends alerts and events to the same connector. The connector posts the data to one Data Collection Endpoint. A separate Data Collection Rule for each tenant adds a TenantSource value and writes the record to the shared tables. The result: all tenants share the same tables, and the TenantSource column tells you which tenant a row came from.This template supports up to five tenants.What is different from the single-t

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