Alternatives to 42Crunch in SaaS

What middleBrick covers

  • Black-box scanning without agents or code access
  • Risk score A–F with prioritized findings
  • Detection aligned to OWASP API Top 10 (2023)
  • OpenAPI 3.x and Swagger 2.0 parsing with ref resolution
  • Authenticated scanning with strict header allowlist
  • Continuous monitoring and diff detection across scans

Black-box scanning for any API stack

This tool is a self-service API security scanner that operates as a black-box solution. You submit a target URL and receive a risk score ranging from A to F along with prioritized findings. It does not require agents, SDKs, or code access, and works with any language, framework, or cloud environment. Scan completion typically occurs in under a minute, exercising read-only methods such as GET and HEAD, with text-only POST support for LLM probes.

Detection aligned to OWASP API Top 10 and related frameworks

The scanner covers 12 categories aligned to OWASP API Top 10 (2023). It maps findings to this standard to validate controls relevant to API security. Detection capabilities include authentication bypass and JWT misconfigurations, BOLA and IDOR via sequential ID enumeration, BFLA and privilege escalation attempts, property over-exposure, input validation issues such as CORS wildcard usage, rate-limiting characteristics, data exposure patterns including PII and API key formats, encryption misconfigurations, SSRF indicators, and inventory management gaps. An additional category addresses LLM/AI Security through adversarial probes across multiple scan tiers.

OpenAPI specifications in versions 3.0, 3.1, and Swagger 2.0 are parsed with recursive $ref resolution. The scanner cross-references spec definitions against runtime observations to identify undefined security schemes, sensitive fields, deprecated operations, and missing pagination. These capabilities help you prepare for compliance evidence under SOC 2 Type II and PCI-DSS 4.0 by surfacing findings relevant to those frameworks.

Authenticated scanning and safety controls

Authenticated scanning is available from the Starter tier upward, supporting Bearer tokens, API keys, Basic authentication, and cookies. Domain verification is enforced through DNS TXT records or an HTTP well-known file to ensure only the domain owner can scan with credentials. A strict header allowlist is applied, forwarding only Authorization, X-API-Key, Cookie, and X-Custom-* headers.

The scanner maintains a strict read-only posture, never sending 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 is not used for model training and is never sold.

Product offerings and integration options

The Web Dashboard provides a centralized location to run scans, review reports, track score trends, and download branded compliance PDFs. The CLI, distributed as an npm package, enables commands such as middlebrick scan <url> with JSON or text output. A GitHub Action is available for CI/CD gating, failing builds when the score drops below a defined threshold. An MCP Server allows scanning from AI coding assistants including Claude and Cursor, and a full API client supports custom integrations.

Continuous monitoring in the Pro tier includes scheduled rescans at intervals of six hours, daily, weekly, or monthly. Diff detection highlights new findings, resolved findings, and score drift. Security alerts are rate-limited to one per hour per API and delivered by email, with HMAC-SHA256 signed webhooks that auto-disable after five consecutive failures. Teams and Slack integrations are available at higher tiers.

Limitations and complementary testing practices

This tool does not fix, patch, block, or remediate issues; it detects and reports with remediation guidance. It does not perform active SQL injection or command injection testing, as those activities fall outside the read-only scope. Business logic vulnerabilities are not detected, as they require domain-specific human analysis. Blind SSRF and other out-of-band infrastructure issues are out of scope, and the scanner does not replace a human pentester for high-stakes audits.

Frequently Asked Questions

What scan outcomes can I expect from the risk score?
The scanner assigns a risk score from A to F and returns prioritized findings with remediation guidance. Higher tiers increase scan depth and coverage.
Can I integrate scanning into my CI/CD pipeline?
Yes, the GitHub Action can fail builds when the score drops below your configured threshold, enabling automated gating.
How does authenticated scanning work?
Authenticated scanning uses Bearer tokens, API keys, Basic auth, or cookies. Domain ownership is verified before credentials are accepted.
Is my scan data retained or used for training models?
Scan data is never sold and is not used for model training. Data is deletable on demand and purged within 30 days of cancellation.