Pricing alternative to GitGuardian

What middleBrick covers

  • Black-box scanning with no agents or SDK integration
  • Under one minute scan time for quick feedback
  • Read-only GET and HEAD methods for safe execution
  • Detection of twelve OWASP API Top 10 categories
  • OpenAPI 3.x and Swagger 2.0 spec parsing with $ref resolution
  • Compliance mapping to PCI-DSS, SOC 2, and OWASP API Top 10

Pricing model and included capabilities

Compare sticker prices and operational factors when evaluating a scanning tool. The free tier supports three scans per month and command line usage, which is suitable for small teams or initial assessments. The Starter plan at 99 dollars per month covers fifteen APIs, monthly scanning, a dashboard for score trends, email alerts, and an MCP server. The Pro plan at 499 dollars per month supports one hundred APIs with additional units billed at 7 dollars each, adding continuous monitoring, GitHub Action gates, CI/CD integration, Slack and Teams alerts, compliance reporting, and signed webhooks. The Enterprise plan at 2000 dollars per month provides unlimited APIs, custom rules, SSO, audit logs, an SLA, and dedicated support.

What the scanner detects and its mapping to major frameworks

The scanner operates as a black-box tool and maps findings directly to PCI-DSS 4.0, SOC 2 Type II, and OWASP API Top 10 (2023). It detects issues across twelve categories aligned to OWASP API Top 10, including authentication bypass and JWT misconfigurations, broken object level authorization and IDOR, broken function level authorization and privilege escalation, excessive data exposure, input validation such as CORS misconfigurations and dangerous methods, rate limiting and resource consumption, sensitive data exposure including PII patterns and API key formats, encryption issues, SSRF indicators, inventory management problems, unsafe consumption surfaces, and LLM/AI security probes across multiple scan tiers.

OpenAPI analysis and authenticated scanning requirements

The tool parses OpenAPI 3.0, 3.1, and Swagger 2.0 with recursive $ref resolution and cross-references spec definitions against runtime findings such as undefined security schemes or missing pagination. Authenticated scanning requires Bearer, API key, Basic auth, or cookies and is available from Starter tier upward. Domain verification is enforced through DNS TXT records or an HTTP well-known file so that only the domain owner can scan with credentials. The scanner forwards a restricted allowlist of headers including Authorization, X-API-Key, Cookie, and X-Custom-*.

Operational safety and data handling

The scanner uses read-only methods such as GET and HEAD, and text-only POST for LLM probes, avoiding destructive payloads. Private IPs, localhost, and cloud metadata endpoints are blocked at multiple layers. Customer scan data can be deleted on demand and is purged within 30 days of cancellation. It does not perform active SQL injection or command injection testing, does not detect business logic vulnerabilities, and does not replace a human pentester for high-stakes audits.

What the scanner does not do and compliance framing

The tool detects and reports with remediation guidance but does not fix, patch, block, or remediate findings. It does not perform active exploit testing outside its scope. Findings align with security controls described in PCI-DSS 4.0, SOC 2 Type II, and OWASP API Top 10 (2023). For other frameworks, it helps you prepare for audits and supports audit evidence without guaranteeing compliance.

Frequently Asked Questions

How many scans are included in the free plan?
The free plan includes three scans per month with CLI access.
Does the scanner perform active injection tests like SQLi or command injection?
No. The scanner focuses on detection and reporting and does not perform active SQL injection or command injection testing.
Can authenticated scans be performed with CI/CD pipelines?
Yes. Authenticated scanning with tokens and headers is supported from the Starter tier and works in CI/CD workflows via the GitHub Action.
How is scan data handled after cancellation?
Customer scan data is deletable on demand and purged within 30 days of cancellation. It is not sold and is not used for model training.