No solution approach in the current research connects this vendor to this use case.
Vendor research
Lasso Security
Review what this vendor says publicly, the security topics those statements may support, what remains unverified, and factual company context. This is not an assessment of product effectiveness or fit.
Use-case context
How this vendor relates to the selected use case
These links show approaches associated with this vendor. The relationship label describes how the approach maps to the use case—not product effectiveness, complete requirement coverage, or fit.
Company scale
Emerging?
EmergingAn early-stage provider with less than $25M in known funding, or 50 or fewer employees without at least $50M in known funding.This is a company-scale signal, not a product-quality rating.
?
EmergingAn early-stage provider with less than $25M in known funding, or 50 or fewer employees without at least $50M in known funding.This is a company-scale signal, not a product-quality rating.A descriptive band derived from retained public revenue, workforce, ownership, or funding signals.
- $6M known funding
- 11-50 employees
- Founded 2023
- Private-company revenue and profitability not sourced
Company context
Private, VC-backed
Early-stage AI security platform focused on large language model (LLM), AI app, and agent protection
Research coverageCounts describe available public research, not product quality.View details
- Vendor statements
- 19 records
- Source-checked records
- 13
- Evaluation requirements
- 19 in this research model
- Unresolved requirements
- 5
Company intelligence
Who is behind the product
Company facts provide evaluation context. Each signal is kept separate because tenure, workforce, funding, and hiring answer different questions.
Lasso Security
- Known funding
- $6M
- Operating scale
- Early-stage AI security platform focused on LLM, AI app, and agent protection
- Backing context
- $6M seed led by Entree Capital with participation from Samsung Next
Seed · $6M · 2023-11-20
Entrée Capital · Samsung Next
- Elad SchulmanCurrent role listed
CEO & Co-Founder
- Ophir DrorCurrent role listed
CPO & Co-Founder
- Lior ZivCurrent role listed
CTO & Co-Founder
- Yuval AbadiCurrent role listed
COO & Co-Founder
There is no combined company rating. The company-scale label uses stated size thresholds; product features and effectiveness require separate evidence.
- Company tenure
- 2023
- Workforce scale
- 11-50
- Hiring activity
- Not displayed
A current count requires a retained, clickable source URL.
Core company facts have supporting public sources.
Company sources and research limits3 linked public sources
Only company facts supported by retained public sources are shown. Missing values remain unknown, and company scale does not establish product effectiveness.
Solution areas
These areas describe how the vendor approaches enterprise AI security. They do not establish product quality or fit.
Buyer context
- Buyer diligence should validate reference maturity and roadmap depth because public funding signal is still early-stage.
- May be relevant where the buyer needs AI application/agent lifecycle security rather than software as a service (SaaS) discovery alone.
Related frameworks
Where public vendor statements relate to framework requirements
11 related frameworks · expand when needed
Related frameworks
Where public vendor statements relate to framework requirements
- Requirements with public support
- 13
- Related requirements
- 11
- References
- 58
- Requirements with public support
- 13
- Related requirements
- 14
- References
- 71
- Requirements with public support
- 13
- Related requirements
- 12
- References
- 35
- Requirements with public support
- 13
- Related requirements
- 12
- References
- 71
- Requirements with public support
- 13
- Related requirements
- 13
- References
- 39
- Requirements with public support
- 13
- Related requirements
- 12
- References
- 39
- Requirements with public support
- 13
- Related requirements
- 12
- References
- 31
- Requirements with public support
- 13
- Related requirements
- 11
- References
- 27
- Requirements with public support
- 13
- Related requirements
- 13
- References
- 31
- Requirements with public support
- 13
- Related requirements
- 13
- References
- 25
- Requirements with public support
- 2
- Related requirements
- 3
- References
- 3
Evaluation questions
What to verify beyond public claims
These questions come from security requirements with some public support. Use them as starting points for demonstrations, documentation review, customer references, or a buyer-observed pilot.
- 01Unapproved AI use discovery
An unmanaged AI app used by a test user appears in discovery inventory with user, app or domain, and timestamp.
- 02Unapproved AI use discovery
The test user's AI usage activity can be filtered or exported with AI-specific context.
- 03Controls for unapproved AI use
A policy blocks, coaches, redirects, or contains a test interaction with an unapproved AI destination.
- 04Controls for unapproved AI use
The control event records policy reason, user, destination, action, and timestamp.
- 05Sensitive-data protection for generative AI
Sensitive prompt, response, or file test data is detected and classified during an AI interaction.
- 06Sensitive-data protection for generative AI
A policy redacts, blocks, coaches, or records the sensitive data event before it leaves the approved path.
- 07Generative AI application security
A test large language model (LLM) application event records prompt, application programming interface (API), model, retrieval, or tool interaction context.
- 08Generative AI application security
A prompt-injection or unsafe-output test is detected, blocked, or flagged by the guardrail or large language model (LLM) firewall.
Detailed security-requirement research18 evaluation items · supporting evidence and open research are shown separatelyExpand
Discover and monitor workforce AI tools, accounts, prompts, domains, models, users, and usage outside approved controls.
An unmanaged AI app used by a test user appears in discovery inventory with user, app or domain, and timestamp.
Inventory software as a service (SaaS) applications that embed AI features, expose enterprise data to AI capabilities, or create AI-driven data movement.
A software as a service (SaaS) app with an embedded AI feature appears in the software as a service (SaaS) AI inventory with app, provider, and feature context.
Monitor approved AI workspaces, tenants, gateways, and model platforms such as ChatGPT Enterprise, Claude Enterprise, Gemini, Microsoft Copilot, Vertex AI, Elvex, or internal AI gateways.
Approved AI workspace activity appears with user, workspace or tenant, model or provider, and timestamp.
Block, coach, redirect, or contain non-approved AI use and policy-violating AI interactions.
A policy blocks, coaches, redirects, or contains a test interaction with an unapproved AI destination.
Detect, classify, redact, or block sensitive data in prompts, responses, files, retrieval, memory, and AI-connected workflows.
Sensitive prompt, response, or file test data is detected and classified during an AI interaction.
Apply session-level controls in browser and software as a service (SaaS) workflows, including uploads, downloads, copy/paste, sharing, and identity-aware access decisions.
A session-level policy controls upload, download, copy, paste, sharing, or form submission in a browser or software as a service (SaaS) workflow.
Protect enterprise-built large language model (LLM) applications, retrieval-augmented generation (RAG) systems, prompts, application programming interfaces (APIs), model calls, tools, and production runtime behavior.
A test large language model (LLM) application event records prompt, application programming interface (API), model, retrieval, or tool interaction context.
Inventory AI systems and owners, translate policy and regulatory obligations into governed workflows, assess risk, manage approvals and exceptions, and retain audit evidence across the AI lifecycle.
A test AI system is registered with owner, intended use, risk tier, lifecycle state, and applicable obligations.
Test models, applications, retrieval-augmented generation (RAG) systems, and agents before release and continuously thereafter using adversarial probes, evaluation suites, attack simulation, and security release gates.
A controlled test campaign exercises an AI model, application, or agent against named AI attack classes.
Discover, inventory, scan, validate, and monitor models, datasets, model artifacts, registries, dependencies, and AI development assets for tampering, unsafe serialization, provenance gaps, or malicious content.
A test model or AI artifact appears in inventory with origin, version, hash or provenance, and deployment context.
Mediate model, agent, tool, application programming interface (API), connector, and Model Context Protocol (MCP) traffic through an enforcement point that applies identity-aware policy, content controls, routing, rate limits, and auditable allow or deny decisions.
A model, agent, tool, or Model Context Protocol (MCP) request passes through a named policy enforcement point.
Observe and govern agent plans, memory, tool calls, delegated tasks, autonomy, runtime decisions, and outcomes.
A test agent run captures plan, steps, tool calls, outcome, and timestamps.
Authorize, log, and control agent-to-agent, agent-to-tool, Model Context Protocol (MCP), connector, and tool-chain handoffs.
An agent, tool, connector, or Model Context Protocol (MCP) handoff logs source identity, destination, and authorization decision.
Inventory, least privilege, credential hygiene, monitoring, and lifecycle management for non-human identities, workloads, service accounts, application programming interface (API) keys, and machine credentials.
A test service account, agent identity, or non-human identity appears in inventory with owner and privileges.
Register AI agents as accountable identities, bind them to owners and delegating users, authorize task- and tool-level access, issue short-lived credentials, review access, and revoke or suspend agent authority.
A test agent is registered with a unique identity, accountable owner, purpose, and permitted resources.
Discover and govern AI coding agents, integrated development environment (IDE) assistants, command-line agents, skills, hooks, extensions, Model Context Protocol (MCP) tools, filesystem access, commands, network activity, secrets, and software-supply-chain actions on developer workstations and build environments.
A test coding agent and its skills, hooks, extensions, or Model Context Protocol (MCP) tools appear in an attributable inventory.
Visibility, attribution, budgeting, rate limiting, anomaly detection, and optimization for AI usage and spend across models, agents, workflows, and owners.
A controlled AI usage event is attributed to user, team, model, workflow, or owner with cost or token metrics.
Publicly discoverable commercial model such as per user, per seat, per app, per token, per integration, or enterprise platform license.
The vendor can map the sourced commercial model to per-user, per-seat, per-app, per-token, per-integration, or platform packaging.
Public sources
Vendor statements and quoted evidence
Showing the first 6 of 19 source records. Open additional records only when needed.
Lasso claims continuous agent discovery, AI bill of materials (AI-BOM) inventory, risk scoring, ownership, intent-aware policy, compliance mapping, audit logs, and cross-platform governance from code to runtime.
A single source of truth for governing agentic AI from code to runtime.
Lasso claims automated agentic red teaming with static, multi-turn, and high-agency attacks, deployment-pipeline integration, adaptive policy generation, and one-click testing.
Stress-test application logic through static, multi-turn, and high-agency attack to uncover vulnerabilities and build adaptive guardrails.
Lasso claims an AI bill of materials (AI-BOM) spanning models, prompts, tools, Model Context Protocol (MCP) servers, frameworks, databases, services, guardrails, identity boundaries, and authorization policies, with continuous CI updates and supply-chain risk assessment.
Inventory every AI component, including models, MCP servers, delegated agents, databases, third-party tool connectors, identity boundaries, and authorization policies.
Lasso claims an Model Context Protocol (MCP) security gateway and intent-aware runtime policy enforcement across agent actions, tools, application programming interfaces (APIs), external connections, indirect prompt injection, memory poisoning, permissions, and data loss prevention (DLP).
Lasso's open-source MCP Gateway provides a security layer for MCP connections.
Lasso claims inventory of identity boundaries and authorization policies, ownership context, role-based permissions, and risk-scored governance of agent access to Model Context Protocol (MCP) servers, application programming interfaces (APIs), and tools.
Inventory every AI component, including identity boundaries and authorization policies.
Lasso claims risk scoring, management, and blocking of Model Context Protocol (MCP) servers, application programming interfaces (APIs), and external tool connections across Claude Code, Claude Desktop, Cursor, and Codex.
Manage or block high-risk tools across Claude Code and Desktop, Cursor, and Codex.
Show 13 additional evidence records
Lasso Security platform materials reviewed did not provide a public product claim for AI usage-cost attribution, token or spend metrics, budgets, chargeback, or cost-aware model routing.
No quoted source text is recorded for this claim.
Lasso Security claims it discovers AI agents and homegrown AI applications via platform integration and CI.
Discover AI agents via platform integration. Connect via CI to automatically discover homegrown applications.
No public claim found for this capability.
No quoted source text is recorded for this claim.
No public claim found for this capability.
No quoted source text is recorded for this claim.
Lasso Security claims runtime policy enforcement through proxy, application programming interface (API), or AI gateway controls.
Enforce policies inline at the proxy, API, or AI Gateway layer with runtime protection that adapts as your application evolves.
Lasso Security claims it analyzes what sensitive data agents can reach and enforces policies inline at the proxy, application programming interface (API), or AI Gateway layer.
Analyze your security posture by understanding what your agents are exposed to, what actions they can perform, what sensitive data can they reach, and more.
Lasso Security claims it maps models, system prompts, tools, and guardrails and provides full context on attacks including which agent was targeted.
Maps models, system prompts, tools and guardrails
Lasso Security claims AI detection and response coverage for agent threats, including tool-chain manipulation and abnormal AI behavior.
what actions they can perform, what sensitive data can they reach
Lasso Security claims AI agent inventory includes exposed actions and sensitive data reachability to support agent risk analysis.
what actions they can perform, what sensitive data can they reach
No public claim found for this capability.
No quoted source text is recorded for this claim.
Lasso Security claims it enforces policies inline at the proxy, application programming interface (API), or AI Gateway layer with runtime protection that adapts as the application evolves.
Enforce policies inline at the proxy, API, or AI Gateway layer with runtime protection that adapts as your application evolves.
No public claim found for this capability.
No quoted source text is recorded for this claim.
No public claim found for this capability.
No quoted source text is recorded for this claim.