Is Lasso Security worth it?
What middleBrick covers
- Black-box scanning with no agents or SDK dependencies
- Under-one-minute scan time with read-only methods
- 12 OWASP API Top 10 aligned detection categories
- OpenAPI 3.x and Swagger 2.0 parsing with $ref resolution
- Authenticated scanning with strict header allowlist
- CI/CD integration via GitHub Action and MCP Server
Scope and testing approach
Lasso Security positions itself as a black-box API scanner that submits requests and analyzes responses without requiring code changes, agents, or SDKs. It supports any language, framework, or cloud target and limits requests to read-only methods plus text-only POST for LLM probes. Scan completion is under one minute, and the tool maps findings to three frameworks: PCI-DSS 4.0, SOC 2 Type II, and OWASP API Top 10 (2023).
Detection coverage and limitations
The tool detects 12 categories aligned to OWASP API Top 10, including authentication bypasses, JWT misconfigurations, BOLA and BFLA, property over-exposure, input validation issues such as CORS wildcards and dangerous methods, rate-limiting indicators, data exposure patterns including PII and API keys, encryption misconfigurations, SSRF indicators, inventory issues, unsafe consumption surfaces, and LLM/AI security probes across tiered scan depths. It parses OpenAPI 3.0, 3.1, and Swagger 2.0 with recursive $ref resolution and cross-references spec definitions against runtime behavior. The scanner does not perform active SQL injection or command injection testing, does not detect business logic vulnerabilities, does not identify blind SSRF, and does not replace a human pentester for high-stakes audits.
Authenticated scanning and safety controls
Authenticated scanning is available from the Starter tier onward, supporting Bearer tokens, API keys, Basic auth, and cookies. Domain verification is required via DNS TXT record or an HTTP well-known file to ensure credentials are only used by domain owners. A strict header allowlist is enforced, forwarding only Authorization, X-API-Key, Cookie, and X-Custom-* headers. Safety measures include read-only methods only, blocking of private IPs, localhost, and cloud metadata endpoints at multiple layers, and a data retention policy that allows deletion on demand with purging within 30 days of cancellation.
Product features, integrations, and pricing
The Web Dashboard centralizes scans, report views, score trends, and downloadable compliance PDFs. The CLI, distributed as an npm package, supports single commands with JSON or text output. A GitHub Action can gate CI/CD, failing builds when scores drop below a set threshold. The MCP Server enables scanning from AI coding assistants. Continuous monitoring in the Pro tier provides scheduled rescans, diff detection, hourly rate-limited email alerts, HMAC-SHA256 signed webhooks with auto-disable after five consecutive failures, and integrations with Slack and Teams. Pricing ranges from a free tier with three monthly scans and CLI access, to Starter at 99 dollars per month for 15 APIs, Pro at 499 dollars per month for 100 APIs with monitoring and CI/CD integration, and Enterprise at 2000 dollars per month for unlimited APIs, custom rules, SSO, audit logs, and dedicated support.
Who should and should not use this tool
Lasso Security is worth it for teams that need frequent, standardized API posture checks across many services and want automated scoring and trend tracking without reading-only intrusive testing. It is less suitable for organizations that require deep business logic validation, active injection testing, or formal compliance certification, since the tool surfaces findings and provides remediation guidance but does not fix, patch, or guarantee compliance. The main objections are the lack of active exploit validation, no support for blind SSRF or business logic issues, and the inability to replace human-led high-stakes audits.