Lasso Security AI runtime security
Lasso publishes numbers where most vendors do not. It says gateway enforcement, which blocks, masks or alerts, completes in under 50 ms, and SiliconANGLE reported on 2 Sep 2026 a CPU-only guardrail returning a verdict in under 5 ms, per Lasso's own benchmarks. Coverage spans model requests and responses, gateway-fronted applications, agent tool calls and on-device hooks for Claude Code. Lasso says it starts in hours with one line of code, and it streams audit trails to a SIEM. Gaps: fail-open or fail-closed behavior, package install blocking, network call blocking, public documentation and a price are all none found on 16 Nov 2026.
Facts read on .
Strength and weakness for AI Runtime Security Tools
Strength: Publishes inline block, mask or alert enforcement with under 50 ms and a sub-5 ms CPU guardrail claim (lasso-security-7, lasso-security-6, lasso-security-14).
Weakness: No fail-open or fail-closed behavior published and package install and network call blocking not named (lasso-security-9; none found on 2026-11-16).
Scores and evidence
Lasso Security is 3rd in the overall ranking at 63.5 of 100. Each score below lists the fact ids behind it; the facts follow further down with their sources and read dates.
| Criterion | Score | Weight | Why | Facts |
|---|---|---|---|---|
| Action types stopped before they complete | 7 of 10 | 30 | The vendor claims blocking of out-of-scope tool calls, prompt injection, sensitive uploads, credential leakage in tool calls and responses before they return. All of it is vendor-only. | lasso-security-12, lasso-security-18, lasso-security-21, lasso-security-17, lasso-security-23, lasso-security-14, lasso-security-10 |
| Layers covered | 7 of 10 | 20 | The vendor claims model request and response inspection, gateway coverage for applications, agent tool calls and on-device hooks. All of it is vendor-only. | lasso-security-15, lasso-security-16, lasso-security-12, lasso-security-28, lasso-security-29 |
| Latency and failure mode | 5 of 10 | 15 | The vendor publishes under 50 ms gateway enforcement and third-party press reports under 5 ms per the vendor's benchmarks. Fail-open or fail-closed behavior: none found. | lasso-security-07, lasso-security-06, lasso-security-09 |
| Deployment | 7 of 10 | 15 | The vendor says it starts in hours with one line of code via gateway, API or SDK, plus hooks through enterprise management. All of it is vendor-claimed. | lasso-security-47, lasso-security-48, lasso-security-46, lasso-security-16, lasso-security-29 |
| Detection and response | 7 of 10 | 5 | The vendor claims audit trails, SIEM streaming, alerts with trace context and an execution graph. SOAR or ticketing: none found. | lasso-security-25, lasso-security-41, lasso-security-11, lasso-security-38, lasso-security-40, lasso-security-42 |
| Transparency | 3 of 10 | 10 | Research is published. Public documentation and a published price: none found. | lasso-security-49, lasso-security-50, lasso-security-51, lasso-security-52 |
| Proof | 8 of 10 | 5 | Third-party press confirms funding and names customers, and analyst recognition is vendor-reported. | lasso-security-02, lasso-security-03, lasso-security-04 |
Where it ranks
Product, deployment, price and owner
- Product assessed: Lasso AI Detection & Response with Intent Security Engine and LEAP/RAPID guardrails
- Deployment: Agentless (read-only CI and cloud integrations), API, SDK, gateway or firewall integration, browser extension, and Claude Code lifecycle hooks via enterprise management
- Time to deploy: Lasso says start in hours, not weeks, and usage control in minutes
- Price: none found on 2026-11-16
- Owner: Lasso Security Ltd.
- Website: lasso.security
Facts and sources
lasso-security-01 (vendor): Lasso says its AI Security Platform gives enterprises visibility, control and protection across AI models, agents and apps.
Quote: "Lasso's AI Security Platform gives enterprises visibility, control, and protection across AI models, agents, and apps."
Source: lasso.security, read .
lasso-security-02 (third-party): SiliconANGLE reports that Lasso Security Ltd. was founded in 2023 by Schulman and Dror and has raised more than $37 million in total, including a $30 million round announced on 2026-09-02 led by ClearSky Advisors.
Quote: "Investors have now put more than $37 million into the company."
Source: siliconangle.com, read .
lasso-security-03 (third-party): SiliconANGLE names BMW, eToro, Fiverr and the U.S. Department of Homeland Security as Lasso customers (reported 2026-09-02).
Quote: "BMW AG is a customer, and so are eToro Group Ltd., Fiverr International Ltd. and the U.S. Department of Homeland Security."
Source: siliconangle.com, read .
lasso-security-04 (vendor): On 2026-09-15 Lasso said Latio Tech's 2026 AI Security Market Report named it a platform leader (vendor's own account of a third-party report).
Quote: "In the report, Lasso is named as one of the major Platform Leaders."
Source: lasso.security, read .
lasso-security-05 (third-party): On 2026-09-01 TechCentral (a promoted article by NEWORDER) said NEWORDER is Lasso's official partner in South Africa and that Lasso is certified to ISO 27001 and SOC 2.
Quote: "Lasso Security was founded in Tel Aviv in 2023, is certified to ISO 27001 and SOC 2, and has customers across Europe, the US and Israel."
Source: techcentral.co.za, read .
lasso-security-06 (third-party): On 2026-09-02 SiliconANGLE reported Lasso's new LEAP guardrail returns a verdict in under five milliseconds on CPUs, per Lasso's own benchmarks.
Quote: "LEAP is transformer-free and returns a verdict in under five milliseconds, the company said, at thousands of times the throughput of existing guardrails."
Source: siliconangle.com, read .
lasso-security-07 (vendor): Lasso says its gateway enforcement (block, mask or alert) completes in under 50 ms.
Quote: "All enforcement executes in under 50ms, with no manual intervention required."
Source: lasso.security, read .
lasso-security-08 (vendor): Lasso says its LLM-as-judge enforcement runs 570 times faster than standard LLM inference, with no latency impact on the user.
Quote: "Lasso’s LLM as a judge operates at 570x the speed of standard LLM inference, so enforcement is contextual and intent-aware with no latency impact on the user experience."
Source: lasso.security, read .
lasso-security-09 (none-found): None found on 2026-11-16: fail-open or fail-closed behavior, or timeout behavior when the control fails, searched on the AI Detection & Response page and the gateway, LEAP and endpoint pages.
Source: lasso.security, read .
lasso-security-10 (vendor): Lasso says it enforces policy inline so a harmful agent action can be stopped before it executes, and that it can block or quarantine an action.
Quote: "preventing unauthorized actions requires inline enforcement that can stop a harmful action before it executes and limit what each agent is permitted to do."
Source: lasso.security, read .
lasso-security-11 (vendor): Lasso says on detection it can block or quarantine an action before it executes, alert with trace context, and feed findings to SIEM.
Quote: "Lasso can block or quarantine an action before it executes, alert security teams with full trace context for investigation, and feed findings into your existing SIEM and observability workflows."
Source: lasso.security, read .
lasso-security-12 (vendor): Lasso says it inspects every coding-agent tool call before execution and flags or blocks anything outside the permitted scope.
Quote: "Lasso inspects every tool call before it is executed."
Source: lasso.security, read .
lasso-security-13 (vendor): Lasso says its coding-assistant coverage addresses agents that read codebases, execute shell commands and call MCP servers (Claude Code, Cursor, Codex, OpenCode).
Quote: "Claude Code, Cursor, and Codex read your codebase, executes shell commands, calls MCPs, and takes actions on your behalf."
Source: lasso.security, read .
lasso-security-14 (vendor): Lasso says gateway mode can block an interaction before it reaches the model or before a response returns, mask sensitive data in transit, or allow and alert.
Quote: "block the interaction before it reaches the model or before a response is returned, mask sensitive data in transit, or allow and alert where interruption would affect a critical workflow"
Source: lasso.security, read .
lasso-security-15 (vendor): Lasso says it inspects every request before it reaches the model and every response before it returns.
Quote: "Inspect every request inline before it reaches the model and every response before it returns."
Source: lasso.security, read .
lasso-security-16 (vendor): Lasso says it integrates with Kong, Envoy AI Gateway, TrueFoundry, Portkey, LiteLLM and other AI gateways without source code changes.
Quote: "Lasso integrates with Kong, Envoy AI Gateway, TrueFoundry, Portkey, LiteLLM, and others."
Source: lasso.security, read .
lasso-security-17 (vendor): Lasso says it detects sensitive data (PII, PCI) in prompts and file uploads and masks it before the prompt reaches third-party models.
Quote: "Detect and monitor in real time if PII, PCI, or any other sensitive data is shared in prompts or file uploads, and mask those contents before the prompt is sent"
Source: lasso.security, read .
lasso-security-18 (vendor): Lasso says it blocks injected or guardrail-bypassing inputs and decodes over 3,000 obfuscation techniques at the intent layer.
Quote: "Lasso decodes over 3,000 obfuscation techniques and detects threats at the intent layer. It blocks inputs designed to bypass safety guardrails or trick agents into performing unauthorized actions"
Source: lasso.security, read .
lasso-security-21 (vendor): Lasso says it scans MCP tool descriptions for hidden instructions and blocks prompt injection at the connection layer.
Quote: "Scan MCP server tool descriptions for hidden instructions. Detect and block prompt injection attempts at the connection layer."
Source: lasso.security, read .
lasso-security-22 (vendor): Lasso says it monitors every MCP tool call in real time and can mask sensitive data before it reaches external servers.
Quote: "Monitor every MCP tool call in real-time to identify indirect prompt injection, memory poisoning, and other AI threats or attack techniques."
Source: lasso.security, read .
lasso-security-23 (vendor): Lasso says it detects PII, API keys and credentials shared through MCP tool calls and masks them before they reach external servers.
Quote: "Detect and monitor in real-time if PII, API keys, credentials, or any other sensitive data is shared through MCP tool calls. Mask sensitive contents before they reach external servers."
Source: lasso.security, read .
lasso-security-25 (vendor): Lasso says it keeps audit trails of every MCP connection and tool call and exports logs to a SIEM.
Quote: "Maintain complete audit trails of every MCP connection and tool call. Export logs to your SIEM."
Source: lasso.security, read .
lasso-security-26 (vendor): Lasso says it governs AI activity on employee endpoints agentlessly, so visibility into AI tools, coding agents and MCP connections starts on day one.
Quote: "Lasso governs AI activity on employee endpoints through an agentless approach, so security teams get visibility into AI tools, coding agents, and MCP connections from day one"
Source: lasso.security, read .
lasso-security-28 (vendor): Lasso says policy enforcement happens at the execution layer on the device itself.
Quote: "Policy enforcement happens at the execution layer on the device itself, so protection holds even when an agent's activity would not otherwise pass through a monitored network path."
Source: lasso.security, read .
lasso-security-29 (vendor): Lasso says it attaches to Claude Code, Cursor and Codex through lifecycle hooks deployed by the enterprise management platform, with no agent to install.
Quote: "Lasso deploys through the enterprise management platform, so there is no agent to install and no code to change."
Source: lasso.security, read .
lasso-security-30 (none-found): None found on 2026-11-16: supported operating systems and a time to deploy for MCP discovery on developer machines, searched on the MCP security, coding assistants and endpoint pages.
Source: lasso.security, read .
lasso-security-33 (vendor): Lasso says its discovery is agentless and read-only, using CI pipelines and native cloud and agent-builder integrations.
Quote: "Agentless, read-only integration into CI pipelines and native integrations with cloud providers and third-party agent builder tools."
Source: lasso.security, read .
lasso-security-36 (vendor): Lasso says AI usage control deploys through a browser extension, proxy integrations and data integrations, and can be running in minutes.
Quote: "Enable full AI usage control in minutes through Lasso’s lightweight deployment paths like our browser extension, proxy integrations, and data integrations."
Source: lasso.security, read .
lasso-security-38 (vendor): Lasso says it maps tool calls, RAG retrievals and sub-agent communications into an execution graph.
Quote: "Lasso monitors every interaction across your AI stack, from tool calls and RAG retrievals to sub-agent communications."
Source: lasso.security, read .
lasso-security-40 (vendor): Lasso says exportable audit trails are updated on every interaction and mapped to NIST AI RMF, OWASP, EU AI Act, ISO 42001 and others.
Quote: "Exportable audit trails are updated on every interaction, not generated on demand when an audit request arrives."
Source: lasso.security, read .
lasso-security-41 (vendor): Lasso says alerts and audit logs can be viewed in Lasso or streamed to a SIEM.
Quote: "View alerts and audit logs directly in Lasso, or stream findings into your SIEM to investigate agent incidents alongside the rest of your security telemetry."
Source: lasso.security, read .
lasso-security-42 (none-found): None found on 2026-11-16: documented ticketing or identity-provider integrations, or SOAR export, searched on the detection and response, usage control and MCP pages.
Source: lasso.security, read .
lasso-security-46 (vendor): Lasso says it deploys via API, firewall or AI gateway integration with no architectural changes.
Quote: "Deploy via API, Firewall, or AI Gateway Integration"
Source: lasso.security, read .
lasso-security-47 (vendor): Lasso says it runs from the Lasso tenant and starts in hours, not weeks, with no agents or code changes.
Quote: "No agents. No code changes. No source code access. Run from the Lasso tenant and start in hours, not weeks."
Source: lasso.security, read .
lasso-security-48 (vendor): Lasso says it deploys with a single line of code via Gateway, API or SDK and ships policy templates aligned to OWASP, MITRE and NIST.
Quote: "Lasso deploys with a single line of code via Gateway, API, or SDK."
Source: lasso.security, read .
lasso-security-49 (vendor): On 2026-09-17 Lasso published research on how LLM text watermarking changes refusals and agent tool calling.
Quote: "We find that it does, in both model refusal behavior and agent tool calling."
Source: lasso.security, read .
lasso-security-50 (vendor): On 2026-09-09 Lasso published a technical post on LEAP, its CPU-based guardrail, with benchmark claims.
Quote: "Introducing LEAP: CPU-based AI Security Guardrails with GPU-Class Accuracy"
Source: lasso.security, read .
lasso-security-51 (none-found): None found on 2026-11-16: a published price; the pricing URL returns a 404 page and the site routes to Book a Demo.
Source: lasso.security, read .
lasso-security-52 (none-found): None found on 2026-11-16: public product documentation; docs.lasso.security loads only a sign-in dashboard titled Lasso Security - Dashboard.
Source: docs.lasso.security, read .
lasso-security-53 (vendor): Lasso says its detection covers indirect prompt injection in files, web responses and MCP outputs before they reach the coding agent.
Quote: "detect injected payloads or hidden instructions in files, web responses, and MCP outputs before they reach the coding agent’s decision layer"
Source: lasso.security, read .