HEAD-TO-HEAD · FACTS ONLY
Lasso vs Zscaler: AI endpoint control facts side by side
Short answer
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?
- 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)
What are the facts, side by side?
| Fact | Lasso | Zscaler |
|---|---|---|
| Owner | None | None |
| Positioning | An 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 devices | Several 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 controlDiffers | Partly 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 extensionDiffers | DescribedAI 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 proxy | DescribedProxy 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 gatewayDiffers | DescribedAn 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 coversDiffers | MatchesClaude 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 runsDiffers | MatchesInspects 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 AI | MatchesUsage 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 runDiffers | PartlyClaude 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 blockingDiffers | PartlyAlert 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 action | MatchesBlock, 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 modeDiffers | PartlyAlert without blocking. Source: Lasso Security: MCP security · Read 27 Sep 2026 | Not in our sources |
| Records who or what took each actionDiffers | PartlyAudit-ready reports. Source: Lasso Security: AI usage control · Read 27 Sep 2026 | Not in our sources |
| Also covers SaaS, cloud or homegrown AIDiffers | MatchesDiscovery 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)Differs | PartlyAWS 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 into | None | None |
| Works with | The 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 |
| Price | Marketplace 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.