Recently active topics

Hi,When we publish applications using classic authentication, we do not encounter any issues. However, when we publish applications that are federated with our Identity Provider (IdP), after the authentication process completes and then the user is redirected back to the application's original URL, the browser displays an access error: ERR_NAME_NOT_RESOLVED Does anyone know if any additional configuration is required for this type of access to work? Thx 

    Building a CrowdStrike Falcon Dashboard on Netskope Data: a Step-by-step Guide How my team streamed Netskope web, DLP, and alert telemetry into CrowdStrike Falcon Next-Gen SIEM, wired up automated indicator sharing, and built a cross-source security dashboard that correlates Netskope, Falcon, and Okta signals in one place. Everything below is enough to build the same thing in your own tenant.   Why we built this My security operations team lives in CrowdStrike Falcon. That is where analysts triage, hunt, and respond. But a lot of the signal they need sits in Netskope: web transaction logs, DLP violations, anomaly alerts, and policy actions from the Netskope One Security Service Edge (SSE) platform. Every time an analyst had to pivot out of Falcon to check the Netskope Admin Console, we lost time and context. Our solution had two parts. First, stream Netskope logs into Falcon LogScale so analysts get a native Netskope dashboard inside Next-Gen SIEM, sitting next to t

There's a question every security vendor eventually has to answer: do you actually use your own product to protect your business? At Netskope, the answer isn't just yes — it's the foundation of how we operate. As the Customer Zero team, our job is to deploy our Netskope products before they reach customers. That includes our full portfolio of AI-powered security capabilities, which today sit at the center of how we detect threats, govern data, control access, and keep our workforce productive without sacrificing visibility. This isn't a case study from a customer. It's what we do every day. And the products we've deployed across our own environment paint a clear picture of where enterprise AI security is headed — and what it actually takes to get there.Our internal security strategy is structured around four primary pillars, which collectively ensure that our AI-driven capabilities provide comprehensive protection across every layer of the organization.  Capability Problem So

The problem we kept running intoEvery day, multiple Netskope employees would post in our internal #customerzero Slack channel asking for Enterprise Browser (EB) access. The messages were nearly identical: someone had just heard about EB, wanted to try it out, and needed a license key or enrollment invite to get started.The CZ team would then manually look up the user, send an enrollment invite through the Netskope admin console, and reply in the thread. This worked, but it was repetitive, manual work that pulled our team away from higher-value investigations and dogfooding activities.We started asking ourselves: why are we the bottleneck here? The process was entirely mechanical — receive request, identify user, send invite, confirm. It was a perfect candidate for automation.📊 By the numbersAfter analyzing 200+ posts in #customerzero, Enterprise Browser invite/license key requests were the second most common issue category — 16+ posts, fully repeatable, zero judgment required to resol

Hear from our SOC manager and Sr. Data Analyst as they share how we leverage AI security dashboards to monitor AI usage, uncover AI security concerns, and convert this into actionable insights.  Learn how to:Monitor AI adoption, uncover risky AI usage, and gauge overall AI risk level using the AI Usage and AI Risk Assessment Dashboards Manage risky user and model behaviors using the AI Guardrails Dashboard Monitor and control AI app-to-app traffic using the AI Gateway Dashboard Monitor MCP usage using the Agentic Broker - MCP Dashboard For more information, check out our Advanced Analytics forum.   View past events in this series!   Check out some customer questions below, or feel free to comment and continue the discussion!  Q: Where can I access this Activity in the AI Apps dashboard within the console?A: Visibility into user activities can be found in the "Activity in AI Apps" section of the AI Usage Dashboard.  Q: How can Netskope monitor and control the use of unsanctioned AI to p

Hello,we currently have 2 publishers at our site. They frequently connect to different NetSkope datacenters (A and B) with similar RTT, which is working as designed. However, the majority of our users are routed to datacenter C, and here we are noticing a discrepancy. Around 80% of the traffic is being routed through only one publisher because it is the only one falling within the (Latency range: 0-31 ms). It seems that even a minimal difference in latency - if it unluckily falls near the threshold of this range - causes the traffic to skew heavily toward a single publisher. Do you have any recommended solutions or workarounds for this behavior?

Hello I would be very interested by all localisation of the “stichers” in NETSKOPE worldWe have subsidarie in US (Philadelphia)We have local Publisher on Philadelphia Experience with NPA is not goodThe network path is : User (near Philadephia) > US-PHIL1 (GW) > US-DEN1 (Sticher) > Publisher (Philadelphia) > local ressource26+43+51Minimum 120 RTT time up to Publisher !!! FromHow having better time ?Eric  

Claude Desktop's third-party inference mode (generally available as of July 9, 2026) lets you point the app at your own cloud inference provider instead of Anthropic's first-party API - such as Amazon Bedrock, Google Cloud's Agent Platform, Microsoft Foundry, or any compatible gateway you operate. That's a big deal for regulated or security-conscious organizations: you get the full Claude Desktop experience (Chat, Cowork, and Code tabs, file creation, multi-step research) while inference and billing run through infrastructure you already control.What it doesn't give you out of the box is visibility and control over what's actually going over the wire - which prompts contain sensitive data, whether someone's about to leak a secret into a conversation, or whether a jailbreak attempt just landed. That's exactly the gap Netskope AI Gateway is built to close - sitting in front of your chosen inference provider as the policy and visibility layer that direct inference access doesn't give you.

As teams scale AI agents beyond basic chatbots, machine-to-machine traffic becomes much harder to govern.This recording covers how AI Gateway handles that agentic traffic, including a walkthrough of real-time token inspection, DLP guardrails, and model routing, plus a live demo of policy setup inside Netskope.If you're evaluating AI Gateway for your own environment, the session is a solid starting point before requesting a technical review or Proof of Value sandbox.▶ Watch here: https://netskopeacademy.skilljar.com/csg-customer-webinar-ai-gatewayOriginally shared in Community News & Announcements —  

This session tackles a gap most security teams are only now running into: conventional testing tools weren't designed for LLMs, so a chatbot can pass every check and still leak data on an edge case.The recording covers why standard scans and manual pen tests fall short for AI systems, how continuous adversarial testing replaces slower manual audits, how teams are folding this testing into their AI development workflows, and how to use a Proof of Value sandbox to safely stress-test proprietary models.▶ Watch here: https://netskopeacademy.skilljar.com/csg-customer-webinar-netskope-ai-red-teaming Originally shared in Community News & Announcements —  

Watch this recording to see how Netskope helps keep AI tools safe for everyday use. It checks conversations with AI as they happen, catching people trying to trick the AI into saying something it shouldn't, and blocking harmful or private information from slipping through.The session starts by explaining the risks in simple terms, then shows how the protection actually works. Good watch whether you're new to this or already using it.🎥 Watch here: https://netskopeacademy.skilljar.com/csg-customer-webinar-ai-guardrails💬 Questions after watching? Drop them below and the team will get back to you. Originally shared in Community News & Announcements — 

Visibility in the Age of Artificial IntelligenceAs enterprises rapidly shift toward a cloud-first and AI-driven landscape, the traditional boundaries of the corporate network have dissolved. Employees are accessing sophisticated AI tools from everywhere, making the internet the primary delivery mechanism for business productivity. This transition introduces a critical challenge: a loss of visibility into network paths, user experience, and application performance. Enter Netskope Digital Experience Management (DEM). DEM is a native component of the Netskope platform designed to provide comprehensive operational status and health visibility for all customer traffic. By leveraging a highly scalable data architecture, DEM pulls telemetry from various back-end sources to deliver real-time, actionable insights into the overall user and application experience. From monitoring tunnel status to tracking client steering and service availability, Netskope DEM ensures that IT teams maintain contro

Dear valued Customer, Thank you for your interest in our recent technical session: Governing AI Agent Traffic: Inside the Netskope AI Gateway. Whether you joined us live or couldn't make it, the full session recording is now available to stream on demand. Watch the On-Demand Recording → Key Session Highlights: Agentic Traffic Governance: Managing machine-to-machine interactions as teams scale AI agents beyond simple chatbots. Feature Walkthrough: Real-time token limit inspection, DLP guardrails, and model routing. Live Deployment Demo: Step-by-step setup and policy configuration inside Netskope. Interested in exploring this further? If you are evaluating AI Gateway for your environment and would like to set up a 1-on-1 technical review or a Proof of Value (PoV) sandbox engagement, feel free reach out to your Netskope account team. Best regards,Rahul Mavila (Principal Product Manager – AI Gateway)Rohit Bhaskar (CX Program Manager)Netskope Customer Succ

We have the AI Security features turned on for our tenant, but the only people who can see these features are tenant admins.  Many of our team are in the Security Admin role, and the only feature they can see is the AI Red Teaming section (No AI Command Center, AI Sec Ops, etc).  This feels like a misconfiguration.  While I could go in and clone our Security Admin role and add the features in ad hoc, there are two problems with this;We’ve never had to do anything like this in the past for things like DEM, IPS or other add on features.  The ability to at least view these new items was there for everyone to see. There is no “AI Security” feature I can just check a box for and add the visibility to the Security Admin role without a bunch of trial and error.  I would have to go through the 3 pages of potential check boxes and determine what is giving them the access and what isn’t.  Not efficient or convenient.Is there any way to have the AI Security features turned on from the Netskope si

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

 If you monitor your Netskope proxy logs or Real-Time Protection events, you have likely come across traffic destined for raw public IP addresses where the Host FQDN looks something like this: http://77.111.102.203/filestreamingservice/files/ff268a10-8dd6-4190-8bc1-d1db06722d0c?P1=...&cacheHostOrigin=1D.tlu.dl.delivery.mp.microsoft.comhttps://194.36.32.209/92f3b6cc-ee7d-4056-af0d-6026e0d4e2f2/.../86ec8c94.intunewin.bin?cacheHostOrigin=swdb02-mscdn.manage.microsoft.comSeeing raw IP addresses in HTTP GET requests can immediately raise red flags for SOC and network teams. However, this pattern is completely normal behavior for Microsoft Delivery Optimization (DO).In this post, we’ll explain why this happens and show you how to build a hyper-efficient, lightweight regex URL profile to accurately match and bypass/steer this traffic in Netskope.Understanding the Behavior: Why Raw IPs?When Windows endpoints fetch OS patches, Defender updates, or Intune app packages (.intunewin), Microsoft

INTEGRATION GUIDEAutomating Noncompliant Device Enforcement with Netskope Cloud Exchange and Microsoft IntuneCloud Exchange × Microsoft IntuneThis guide shows how the Netskope Cloud Exchange Risk Exchange (CRE) module reads device compliance from Microsoft Intune, tags noncompliant devices in the Netskope tenant, and drives real-time enforcement. The result is a closed loop between your Mobile Device Management (MDM) system and Netskope, with no manual handoff between consoles.How the integration worksMicrosoft Intune continuously evaluates enrolled devices against its compliance policies. Cloud Exchange pulls that device data through the Microsoft Intune plugin, merges it with the matching Netskope device record, and, when a business rule matches, pushes a device tag back to the Netskope tenant. A Device Classification rule reads that tag, and a Real-time Protection policy acts on the classification.The stages below trace a single noncompliant Windows device end to end. 1 2

Here I would like to give a suggestion Single-word keyword matching on AI responses produces a high rate of false positives for educational cybersecurity content. A response that merely defines "phishing" or "botnet" is treated the same as one that provides malicious guidance. Support for multi-word expressions, intent-based matching, or response-aware context would significantly improve precision while preserving legitimate educational use. If anybody can help me with the same , please !! 

Under what categories should a Custom Cloud App fall under ? Does the categorization rely on the domains that we provide when defining the application?

Hi Team, Can you please help to allow login to Codex Enterprise application only and block rest? I tried using the Header insertion but it's not working.