HEAD-TO-HEAD · FACTS ONLY
Noma vs Zscaler: AI endpoint control facts side by side
Short answer
Noma describes 1 of the four product control types on the pages we read and Zscaler describes 1; they differ on on-device control and network or SSE proxy. On decisions, Noma describes some control over tool calls 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?
- Filled or hatched marker: Noma
- 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 | Noma | Zscaler |
|---|---|---|
| Owner | None | None |
| Positioning | An AI security platform with AI-SPM, Agent Access Control, AI detection and response and AI red teaming, covering agents on endpoints, in SaaS and in homegrown apps. | 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 | Discovers endpoint agents through your existing EDR or MDM, with no new endpoint agent to deploy. Source: Noma Security: endpoint agents · 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 | DescribedDiscovers endpoint agents such as Claude Code, Cursor and Codex with their MCP servers and skills, blocks unauthorized and malicious ones, and inspects activity at runtime. Source: Noma Security: endpoint agents · Read 27 Sep 2026 | Not in our sourcesNot described on the pages we read. |
| Browser extension | Not in our sourcesNot described on the pages we read. | Not in our sourcesNot described on the pages we read. |
| Network or SSE proxyDiffers | Not in our sourcesNot described on the pages we read. | 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 gateway | Not in our sourcesNot described on the pages we read. | Not in our sourcesNot described on the pages we read. |
| Names the coding agents it coversDiffers | MatchesNames Claude Code, Cursor and Codex. Source: Noma Security: endpoint agents · Read 27 Sep 2026 | Not in our sources |
| Decides on a tool call before it runsDiffers | PartlyRuntime inspection of the event, the session, the identity behind the agent and the data it reaches; decisions on individual tool calls are described less specifically. Source: Noma Security: endpoint agents · Read 27 Sep 2026 | Not in our sources |
| Controls what goes into browser AIDiffers | Not in our sources | 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 | MatchesThrough your existing EDR or MDM, with no new endpoint agent. Source: Noma Security: endpoint agents · Read 27 Sep 2026 | Not in our sources |
| Can warn or ask instead of only blockingDiffers | PartlyStates that runtime decisions can route to a human. Source: Noma Security: endpoint agents (re-read) · Read 13 Oct 2026 | Not in our sources |
| Can block an agent, tool or action | MatchesBlocks unauthorized and malicious agents. Source: Noma Security: endpoint agents · 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 mode | Not in our sources | Not in our sources |
| Records who or what took each actionDiffers | PartlyKeeps a live registry of allowed agents, MCP servers and skills and inspects the identity behind each agent. Source: Noma Security: endpoint agents · Read 27 Sep 2026 | Not in our sources |
| Also covers SaaS, cloud or homegrown AIDiffers | MatchesCovers endpoint, SaaS and homegrown agents. Source: Noma 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 | MatchesAWS Marketplace lists the Noma Security Platform at $200,000 for a 12-month contract (marketplace list price); noma.security has no pricing page. Source: AWS Marketplace: Noma Security Platform · Read 11 Oct 2026 | Not in our sources |
| Built into | None | None |
| Works with | None in our sources | None in our sources |
| Price | Marketplace list price: $200,000 for a 12-month contract on AWS Marketplace. No pricing page on noma.security. Source: AWS Marketplace: Noma Security Platform · 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: Noma describes it; Zscaler is not in our sources.
- Network or SSE proxy: Noma is not in our sources; Zscaler describes it.
- Names the coding agents it covers: Noma matches; Zscaler is not in our sources.
- Decides on a tool call before it runs: Noma partly matches; Zscaler is not in our sources.
- Controls what goes into browser AI: Noma is not in our sources; Zscaler matches.
- Rolls out through EDR or device management you run: Noma matches; Zscaler is not in our sources.
- Can warn or ask instead of only blocking: Noma partly matches; Zscaler is not in our sources.
- Records who or what took each action: Noma partly matches; Zscaler is not in our sources.
- Also covers SaaS, cloud or homegrown AI: Noma matches; Zscaler partly matches.
- Has a public price or tiers (vendor site or marketplace): Noma matches; Zscaler is not in our sources.
Choose Noma if
- Agents run on laptops, in SaaS and in apps you build, and you want one place to see them
- You want discovery through existing EDR or MDM without a new agent
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?
Noma
- A watch-only or simulation mode is not described on the pages we read.
- Decisions on individual tool calls are described less specifically than discovery, and the only public price is a $200,000 a year marketplace listing.
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.