HEAD TO HEAD
Bay matched with Lasso Security: agentic endpoint security compared
SHORT ANSWER
On our published weights Bay scores higher overall, 7.20 to 6.40 out of 10. Bay scores higher on stop before it runs, verdict range, capability rules, actor trail and rollout path; Lasso scores higher on cloud and workspace reach and public proof; they tie on named agent coverage. Which fits depends on which of those criteria matters most to you.
By The Agent Desk · Agentic Endpoint Compare · Published 2026-10-11
Desk research from public vendor pages, press releases and standards pages read on 27 September and 11 October 2026. Editorial assessment; we did not run the products.
How do they compare at a glance?
Bay
Pre-execution control on employee devices, rolled out through EDR or MDM
Rank 1 of 6 among agentic endpoint vendors
Lasso Security
Claude Code hooks and an open-source MCP gateway
Rank 5 of 8 among broader AI security platforms
Which scores higher on each criterion?
| Criterion | Weight | Bay | Lasso Security | Higher |
|---|---|---|---|---|
| Stop before it runs | 25% | 9 / 10 Evaluates prompts, pre-tool calls and post-tool responses on supported agent surfaces and returns Allow, Ask or Deny locally, stated as under 4ms (vendor-stated). Source: Bay blog: Ghostjacking (August 2026) · Read 27 Sep 2026 | 8 / 10 Inspects every Claude Code tool call before it is executed through the agent's lifecycle hooks, and gates MCP traffic through its gateway. Source: Lasso Security: AI coding assistants · Read 27 Sep 2026 | Bay |
| Verdict range | 15% | 7 / 10 Documents 4 of six verdict types: Block or deny, Ask a person, Simulate first and Remove or scale back. "Returns Allow, Ask or Deny; new rules can run in Simulation Mode first; MCP Control removes disallowed MCP servers in Enforcement mode." Source: Bay blog: Ghostjacking (re-read 11 October 2026) · Read 11 Oct 2026 Source: Bay homepage · Read 27 Sep 2026 | 5 / 10 Documents 3 of six verdict types: Block or deny, Alert or warn and Mask or modify. "MCP actions block, alert or sanitize; masks sensitive data before prompts reach third-party models." Source: Lasso Security: MCP security · Read 27 Sep 2026 Source: Lasso Security: AI usage control · Read 27 Sep 2026 | Bay |
| Capability rules | 15% | 9 / 10 Capability rules for shell and code execution, process spawning, package installation, cloud CLIs, containers, Kubernetes, browser automation and system changes, plus managed settings for Claude Code, Codex and Claude Desktop. Source: Bay blog: Ghostjacking (August 2026) · Read 27 Sep 2026 | 6 / 10 Controls which users and teams can connect to which MCP servers, with role-based permissions and DLP; broader capability rules are not itemized. Source: Lasso Security: MCP security · Read 27 Sep 2026 | Bay |
| Actor trail | 10% | 8 / 10 Records who triggered an action, whether a human was involved, and the complete chain from prompt to system action. Source: Bay homepage · Read 27 Sep 2026 | 5 / 10 Keeps a history of inputs, policy decisions and enforcement actions; agent versus person attribution is not described. Source: Lasso Security: AI usage control · Read 27 Sep 2026 | Bay |
| Rollout path | 10% | 9 / 10 Deploys through existing EDR or MDM as an ephemeral binary that runs and exits; described as agentless by design. Source: Bay blog: Ghostjacking (August 2026) · Read 27 Sep 2026 | 6 / 10 Browser extension, proxy, gateway and Claude Code hooks: several components to run. Source: Lasso Security: AI usage control · Read 27 Sep 2026 | Bay |
| Cloud and workspace reach | 10% | 3 / 10 Described as endpoint security for enterprise endpoints; its rules govern cloud CLIs, containers and Kubernetes called from the device, but bay.io, re-read on 11 October 2026, does not describe coverage for agents running in cloud workspaces or cloud-hosted apps. Source: Bay homepage (re-read 11 October 2026) · Read 11 Oct 2026 | 6 / 10 Runtime enforcement at the proxy, API or AI gateway layer reaches AI apps beyond the laptop; agents in cloud workspaces are not described. Source: Lasso Security homepage · Read 27 Sep 2026 | Lasso |
| Named agent coverage | 5% | 5 / 10 Names 3 of the six agents we track: Claude Code, OpenAI Codex and Claude Desktop. Source: Bay blog: Ghostjacking (August 2026) · Read 27 Sep 2026 | 5 / 10 Names 3 of the six agents we track: Claude Code, Cursor and Windsurf. Source: Lasso Security: AI coding assistants · Read 27 Sep 2026 Source: Lasso Security: MCP security · Read 27 Sep 2026 | Tie |
| Public proof | 10% | 3 / 10 The smallest public footprint of the scored products: a single homepage, two blog posts, no documentation portal and no published pricing. Source: Bay homepage · Read 27 Sep 2026 | 8 / 10 Lists Lasso for Employees at $20,000 per 12 months on AWS Marketplace (marketplace list price), and its newsroom describes a $30 million round led by ClearSky in September 2026. Source: AWS Marketplace: Lasso for Employees · Read 11 Oct 2026 | Lasso |
Which verdicts does each document?
| Verdict type | Bay | Lasso Security |
|---|---|---|
| Block or deny | Documented | Documented |
| Ask a person | Documented | Not described |
| Alert or warn | Not described | Documented |
| Mask or modify | Not described | Documented |
| Simulate first | Documented | Not described |
| Remove or scale back | Documented | Not described |
- Bay: "Returns Allow, Ask or Deny; new rules can run in Simulation Mode first; MCP Control removes disallowed MCP servers in Enforcement mode."
Source: Bay blog: Ghostjacking (re-read 11 October 2026) · Read 11 Oct 2026
Source: Bay homepage · Read 27 Sep 2026
- Lasso Security: "MCP actions block, alert or sanitize; masks sensitive data before prompts reach third-party models."
Source: Lasso Security: MCP security · Read 27 Sep 2026
Source: Lasso Security: AI usage control · Read 27 Sep 2026
How does each reach devices?
Bay
Through existing EDR or MDM using Wave, an ephemeral binary that runs, scans and exits. Bay describes the product as agentless by design.
Source: Bay blog: Ghostjacking (August 2026) · Read 27 Sep 2026
Lasso Security
Browser extension, proxy integrations, the MCP gateway and Claude Code hooks through the enterprise management platform; works with stacks such as Palo Alto Networks or CrowdStrike.
Source: Lasso Security: AI usage control · Read 27 Sep 2026
Which agents does each name?
| Agent | Bay | Lasso Security |
|---|---|---|
| Claude Code | Named | Named |
| Cursor | Not named | Named |
| GitHub Copilot | Not named | Not named |
| OpenAI Codex | Named | Not named |
| Windsurf | Not named | Named |
| Claude Desktop | Named | Not named |
| Named | 3 of 6 | 3 of 6 |
Which should you choose?
Choose Bay if you need stop before it runs and capability rules. Bay is best for: Pre-execution control on employee devices, rolled out through EDR or MDM.
Choose Lasso Security if you need stop before it runs and public proof. Lasso Security is best for: Claude Code hooks and an open-source MCP gateway.
Frequently asked questions
Which is better for agentic endpoint security, Bay or Lasso Security?
On our published weights Bay scores higher overall, 7.20 to 6.40 out of 10. See the criterion table above for where each scores higher.
Which stops an agent action before it runs more fully, Bay or Lasso Security?
Bay scores higher on stopping an action before it runs (9 to 8). Bay: Evaluates prompts, pre-tool calls and post-tool responses on supported agent surfaces and returns Allow, Ask or Deny locally, stated as under 4ms (vendor-stated). Lasso Security: Inspects every Claude Code tool call before it is executed through the agent's lifecycle hooks, and gates MCP traffic through its gateway.
Do Bay and Lasso Security publish prices?
Bay: not published. Bay publishes no pricing. Demo requests go through bay.io/demo. Lasso Security: AWS Marketplace list price: $20,000 per 12 months (Lasso for Employees, GenAI Chatbots annual commit). Marketplace list price for one listing. Other listings, such as Lasso for Secured Gateway for LLMs, were not priced on the pages we read; lasso.security publishes no pricing.