Is GitGuardian worth it?
What middleBrick covers
- Black-box scanning with no agents or code access
- Risk scoring from A to F with prioritized findings
- Coverage aligned to OWASP API Top 10, PCI-DSS, SOC 2
- OpenAPI 3.x and Swagger 2.0 parsing with ref resolution
- Authenticated scanning with strict header allowlist
- Continuous monitoring with diff detection and alerts
Scope and approach compared to API security scanners
middleBrick is a black-box API security scanner. You submit a URL and receive a risk score from A to F with prioritized findings. It uses read-only methods (GET and HEAD) plus text-only POST for LLM probes, and scans complete in under a minute. Because it requires no agents, SDKs, or code access, it works with any language, framework, or cloud. This approach contrasts with tools that rely on instrumentation or agent-based monitoring, which can introduce complexity and maintenance overhead.
Detection coverage aligned to recognized standards
The scanner covers 12 categories aligned to the OWASP API Top 10 (2023). Detection capabilities include authentication bypass and JWT misconfigurations, broken object level authorization and IDOR, broken function level authorization and privilege escalation, property authorization and over-exposure, input validation issues such as CORS misconfigurations and dangerous HTTP methods, rate limiting and resource consumption indicators, data exposure including PII patterns and API key leak detection, encryption hygiene, SSRF indicators, inventory and versioning issues, unsafe consumption surface, and LLM/AI security probes across multiple tiers. It maps findings to OWASP API Top 10, PCI-DSS 4.0, and SOC 2 Type II. It also supports audit evidence for other frameworks through alignment, without claiming certification or compliance guarantees.
OpenAPI analysis and authenticated scanning constraints
middleBrick parses OpenAPI 3.0, 3.1, and Swagger 2.0 with recursive $ref resolution, cross-referencing spec definitions against runtime behavior to identify undefined security schemes, sensitive fields, deprecated operations, and missing pagination. Authenticated scanning is available from the Starter tier upward, supporting Bearer, API key, Basic auth, and Cookie. Domain verification is enforced via DNS TXT records or HTTP well-known files so only domain owners can run authenticated scans. Header forwarding is limited to Authorization, X-API-Key, Cookie, and X-Custom-* to reduce noise and risk.
Product features, monitoring, and pricing transparency
The Web Dashboard provides scan management, report viewing, score trends, and downloadable branded compliance PDFs. The CLI via the middlebrick npm package supports commands such as middlebrick scan <url> with JSON or text output. A GitHub Action can gate CI/CD, failing the build when the score drops below a chosen threshold. The MCP Server enables scanning from AI coding assistants. Continuous monitoring in the Pro tier includes scheduled rescans every 6 hours to monthly, diff detection for new and resolved findings, email alerts rate-limited to one per hour per API, and HMAC-SHA256 signed webhooks that auto-disable after five consecutive failures. Pricing includes a Free tier at zero cost with three scans per month and CLI access, Starter at 99 dollars per month for 15 APIs with dashboard and alerts, Pro at 499 dollars per month for 100 APIs plus continuous monitoring and CI/CD integration, and Enterprise at 2000 dollars per month for unlimited APIs with custom rules and SLA-backed support.
Limitations and what the scanner does not do
middleBrick is a detection and reporting tool and does not fix, patch, block, or remediate findings. It does not perform active SQL injection or command injection testing, which requires intrusive payloads outside its scope. It does not detect business logic vulnerabilities, which typically demand human understanding of your domain workflows. Blind SSRF is out of scope due to the absence of out-of-band infrastructure detection. It does not replace a human pentester for high-stakes audits. The tool focuses on surface-level security misconfigurations and known attack patterns, not on nuanced logic flaws or advanced adversarial behaviors that require contextual analysis.