Lasso Security pricing
What middleBrick covers
- Transparent scan results for API risk assessment
- Mapping findings to PCI-DSS 4.0 and SOC 2
- Covers requirements of OWASP API Top 10 (2023)
- Supports audit evidence collection
- Aligns with security controls for compliance
- Performs authenticated and unauthenticated scans
Lasso Security pricing transparency
Lasso Security does not publish a public price list on its website. The publicly available information indicates that pricing is quote-based and influenced by factors such as the number of APIs, required scan frequency, authentication methods, and whether continuous monitoring or compliance reporting is requested. Because the pricing model is not transparent, organizations must contact the vendor to receive a formal estimate tailored to their environment.
What drives Lasso Security pricing
When a vendor does not disclose detailed pricing, quotes typically scale with the number of endpoints, the complexity of authentication flows, and the depth of testing (for example, the choice between quick checks versus more extensive coverage). If continuous monitoring or scheduled rescans are requested, the offering is commonly priced as a subscription with tiers based on API count or volume. Additional factors include required integrations such as CI/CD gates, ticketing or SIEM connectors, and the level of reporting detail expected by auditors or compliance stakeholders.
Per-seat and per-scan models in context
Some security tools are sold using a per-seat license for the management console combined with a per-scan or per-API charge for each target. When pricing is not disclosed, it is common for entry-level access to be limited to a small number of scans per period, with higher tiers unlocking more frequent testing, dashboard history, and alerting. Organizations should clarify whether a quote includes infrastructure overhead, support SLAs, and any caps on scan volume that could affect large-scale API portfolios.
Enterprise and compliance considerations
Enterprise arrangements often bundle features such as single sign-on, audit logs, custom rule definitions, and dedicated support. If your environment requires mappings to security frameworks or evidence for audits, the cost typically reflects the engineering effort to configure scans, maintain schedules, and produce reports aligned with PCI-DSS 4.0, SOC 2 Type II, and OWASP API Top 10 (2023). Because these capabilities are often optional add-ons or higher-tier offerings, pricing variability is expected.
Evaluating cost versus coverage
Before committing to a quote, consider how the offering covers the full lifecycle of API security, including discovery, scanning, and ongoing monitoring. Ask whether the price includes onboarding assistance, help with authentication schemes, and guidance for remediation. Understanding the number of APIs included at each tier, the frequency of rescans, and the availability of integrations will help you compare options and avoid unexpected costs as your API surface grows.