Lasso Security
commercialThe section your link pointed to isn't on Lasso Security's page any more, so we've brought you to the top.
Lasso Security protects employee GenAI use, LLMLLMA large language model, a neural network trained on large amounts of text to recognize patterns and generate language. Applications use it for tasks such as answering, summarizing and writing code. applications and AI agents with runtime guardrails, data-leak prevention and CPUCPUThe main general-purpose processor in a computer. It runs application instructions and coordinates work with memory and other hardware.-only guardrail models.
Summary
Lasso Security is a commercial ai-security platform that enforces runtime guardrails, data-leak prevention, and CPU-only guardrail models for employee GenAI use, LLM applications, and AI agents. It runs as a service, making it suitable for organizations managing AI risk profiles, and its documentation positions it alongside other controls for data loss prevention. The project launched in 2023.
Lasso Security protects employee GenAI use, LLM applications and AI agents with runtime guardrails, data-leak prevention and CPU-only guardrail models.
How Lasso Security helps
Which employees are pasting sensitive data into GenAI tools?
monitors employee GenAI use at runtime and flags prompts containing sensitive data before they leave the organization
Which prompts sent to an LLM application are attempts at prompt injection?
applies runtime guardrails to inbound prompts and blocks or flags the ones matching prompt-injection patterns
Is a response from an AI agent about to leak data it shouldn't?
inspects outbound responses for sensitive data and stops the leak before it reaches the user
Can guardrails run against AI traffic without adding GPU infrastructure?
runs its guardrail models on CPU, so the checks sit inline with LLM traffic without provisioning specialized hardware
Where does AI risk sit alongside the rest of our data-loss-prevention controls?
positions its runtime guardrails and data-leak prevention as a layer that works alongside existing DLP controls rather than replacing them
Languages
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
Five scores for Lasso Security, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Lasso Security puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
2 entries
No entries match these filters.
- October 20261
- September 20261
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.
Choose a badge style and copy the code →