Skip to content
Endpoint AI Finder

HEAD-TO-HEAD · FACTS ONLY

Lasso vs Zscaler: AI endpoint control facts side by side

Short answer

Lasso describes 3 of the four product control types on the pages we read and Zscaler describes 1; they differ on on-device control, browser extension and AI or MCP gateway. On decisions, Lasso decides on a tool call before it runs and Zscaler does not describe tool-call decisions on the pages we read. We do not score either; the right choice depends on the AI tools people use, your devices, your current stack and whether you block or guide.

By The Device Desk · Endpoint AI Finder · Published 2026-10-11

Desk research from public vendor pages read on 27 September and 11 October 2026. Profiles follow our published method; we did not run the products.

Vendor pages read September and October 2026 · updated 2026-10-13

Where do their controls sit?

Lasso: described at 3 of 4 product control positions (browser extension, network or sse proxy, ai or mcp gateway), partly at 1 (on-device control).AI servicesMCP serversDEVOn-device controlBRWBrowser extensionNETNetwork or SSE proxyGWYAI or MCP gatewayPOLPolicy: no product
  • Filled or hatched marker: Lasso
  • Dashed teal ring: Zscaler, described
  • DEV Filled marker: described on the product pages we read
  • DEV Hatched marker: partly described (another component, a narrower scope, or method not detailed)
  • DEV Dashed marker: not in our sources (it may exist; we did not find it)
The map shows where each product's own pages describe a control, or where your answers point. It is not a measure of how well a product works.

What are the facts, side by side?

Lasso Security and Zscaler Generative AI Security, from each product's own pages. Differs is computed from recorded statuses, not wording.
FactLassoZscaler
OwnerNoneNone
PositioningAn AI security platform with discovery and an AI-BOM, posture management, automated red teaming and runtime enforcement at the proxy, API or AI gateway layer, plus usage control through a browser extension and an open-source MCP gateway.Zscaler's controls for employee use of generative AI: prompt-level visibility, allow or block by app, DLP blocking across GenAI apps, browser isolation that disables cut, paste and download, and data security for Microsoft Copilot.
How it reaches devicesSeveral components: a browser extension and proxy integrations for usage control, an open-source MCP gateway, and Claude Code lifecycle hooks set through the enterprise management platform.

Source: Lasso Security: AI usage control · Read 27 Sep 2026

Delivered with Zscaler's cloud security service in the network path; endpoint agents are not described on the page we read.

Source: Zscaler: Secure the use of generative AI · Read 11 Oct 2026

On-device controlDiffersPartly describedConnects directly to Claude Code's lifecycle hooks via the enterprise management platform and inspects every tool call before it runs; a resident device agent is not described.

Source: Lasso Security: AI coding assistants · Read 27 Sep 2026

Not in our sourcesNot described on the pages we read.
Browser extensionDiffersDescribedAI usage control through a browser extension.

Source: Lasso Security: AI usage control · Read 27 Sep 2026

Not in our sourcesNot described on the pages we read.
Network or SSE proxyDescribedProxy integrations for AI usage control; the page says it works with Palo Alto Networks or CrowdStrike.

Source: Lasso Security: AI usage control · Read 27 Sep 2026

DescribedSee all input prompts users send to apps, allow or block apps, block sensitive data with DLP across GenAI, and isolate the browser to disable cut, paste and download.

Source: Zscaler: Secure the use of generative AI · Read 11 Oct 2026

AI or MCP gatewayDiffersDescribedAn open-source MCP gateway that discovers MCP servers across Claude, Cursor and Windsurf and can block, alert or sanitize.

Source: Lasso Security: MCP security · Read 27 Sep 2026

Not in our sourcesNot described on the pages we read.
Names the coding agents it coversDiffersMatchesClaude Code lifecycle hooks, and MCP discovery across Claude, Cursor and Windsurf.

Source: Lasso Security: AI coding assistants · Read 27 Sep 2026

Not in our sources
Decides on a tool call before it runsDiffersMatchesInspects every Claude Code tool call before it is executed.

Source: Lasso Security: AI coding assistants · Read 27 Sep 2026

Not in our sources
Controls what goes into browser AIMatchesUsage control through a browser extension.

Source: Lasso Security: AI usage control · Read 27 Sep 2026

MatchesPrompt-level visibility, DLP blocking across GenAI apps, and browser isolation that disables cut, paste and download.

Source: Zscaler: Secure the use of generative AI · Read 11 Oct 2026

Rolls out through EDR or device management you runDiffersPartlyClaude Code hooks are set through the enterprise management platform; the other components are a browser extension, a proxy and a gateway.

Source: Lasso Security: AI coding assistants · Read 27 Sep 2026

Not in our sources
Can warn or ask instead of only blockingDiffersPartlyAlert is an action; asking the user is not described.

Source: Lasso Security: MCP security · Read 27 Sep 2026

Not in our sources
Can block an agent, tool or actionMatchesBlock, alert or sanitize on MCP traffic.

Source: Lasso Security: MCP security · Read 27 Sep 2026

MatchesAllow or block GenAI apps, and block sensitive data with DLP.

Source: Zscaler: Secure the use of generative AI · Read 11 Oct 2026

Has a watch-only or simulation modeDiffersPartlyAlert without blocking.

Source: Lasso Security: MCP security · Read 27 Sep 2026

Not in our sources
Records who or what took each actionDiffersPartlyAudit-ready reports.

Source: Lasso Security: AI usage control · Read 27 Sep 2026

Not in our sources
Also covers SaaS, cloud or homegrown AIDiffersMatchesDiscovery and AI-BOM, posture management, red teaming and runtime enforcement for AI apps.

Source: Lasso Security homepage · Read 27 Sep 2026

PartlyData security for Microsoft Copilot, including misconfigurations.

Source: Zscaler: Secure the use of generative AI · Read 11 Oct 2026

Has a public price or tiers (vendor site or marketplace)DiffersPartlyAWS Marketplace lists Lasso for Employees with an annual commit for GenAI chatbots at $20,000 for 12 months (marketplace list price); prices for its other products are not listed there.

Source: AWS Marketplace: Lasso for Employees · Read 11 Oct 2026

Not in our sources
Built intoNoneNone
Works withThe usage control page says it works with Palo Alto Networks. The usage control page says it works with CrowdStrike. Offers proxy integrations for AI usage control.

Source: Lasso Security: AI usage control · Read 27 Sep 2026

None in our sources
PriceMarketplace list price: Lasso for Employees, annual commit for GenAI chatbots, $20,000 for 12 months on AWS Marketplace. Other products: not published.

Source: AWS Marketplace: Lasso for Employees · Read 11 Oct 2026

Not published (demo request).

Source: Zscaler: Secure the use of generative AI · Read 11 Oct 2026

Where do they differ?

  • On-device control: Lasso partly describes it; Zscaler is not in our sources.
  • Browser extension: Lasso describes it; Zscaler is not in our sources.
  • AI or MCP gateway: Lasso describes it; Zscaler is not in our sources.
  • Names the coding agents it covers: Lasso matches; Zscaler is not in our sources.
  • Decides on a tool call before it runs: Lasso matches; Zscaler is not in our sources.
  • Rolls out through EDR or device management you run: Lasso partly matches; Zscaler is not in our sources.
  • Can warn or ask instead of only blocking: Lasso partly matches; Zscaler is not in our sources.
  • Has a watch-only or simulation mode: Lasso partly matches; Zscaler is not in our sources.
  • Records who or what took each action: Lasso partly matches; Zscaler is not in our sources.
  • Also covers SaaS, cloud or homegrown AI: Lasso matches; Zscaler partly matches.
  • Has a public price or tiers (vendor site or marketplace): Lasso partly matches; Zscaler is not in our sources.

Choose Lasso if

  • You want controls in several places at once: browser, proxy, MCP gateway and coding agent hooks
  • You prefer an open-source MCP gateway you can inspect

Choose Zscaler if

  • You already route traffic through Zscaler and want GenAI controls there
  • Your main risk is sensitive data pasted or uploaded into GenAI web apps

Which limits should you check?

Lasso

  • Several components to deploy and run.
  • Asking the user before an action is not described, and the only public price covers its chatbot product on AWS Marketplace.

Zscaler

  • Coding agents, MCP servers and local agent actions are not described on the page we read.
  • Warn or ask responses are not described, and no pricing is published.

Questions people ask

Is Lasso or Zscaler better for AI endpoint control?

Neither is scored on this site. Lasso describes 3 of four product control types and Zscaler 1 on the pages we read, and they differ on 11 recorded facts. Which fits depends on the AI tools people use, your devices, where the work happens and whether you block or guide; the finder checks those.

Which of the two decides on a tool call before it runs?

Lasso: Matches. Zscaler: Not in our sources. Warn or ask: Lasso Partly, Zscaler Not in our sources.

Do Lasso or Zscaler publish prices?

Lasso: Marketplace list price: Lasso for Employees, annual commit for GenAI chatbots, $20,000 for 12 months on AWS Marketplace. Other products: not published. Zscaler: Not published (demo request).