Alternatives to 42Crunch on Hanami

What middleBrick covers

  • Black-box API security scanning with risk score A–F
  • 12 OWASP API Top 10 (2023) detection categories
  • OpenAPI 3.0/3.1 and Swagger 2.0 parsing with ref resolution
  • Authenticated scans with header allowlist and domain gate
  • CI/CD integration via GitHub Action and CLI
  • Continuous monitoring with diff detection and HMAC-SHA256 webhooks

Black-box scanning for Hanami and other Ruby frameworks

middleBrick is a self-service API security scanner that operates as a black-box tool. You submit a target URL and receive a risk score from A to F along with prioritized findings. It requires no agents, no SDK integration, and no access to your source code. The scanner supports any language and framework, including Hanami, Sinatra, Rails, and other Ruby stacks. It only issues read-only methods such as GET and HEAD, and text-only POST for LLM probes, completing most scans in under a minute.

Detection coverage aligned to OWASP API Top 10

The scanner covers 12 categories aligned to OWASP API Top 10 (2023). It detects authentication bypasses and JWT misconfigurations such as alg=none, weak algorithms, expired tokens, and missing claims. It identifies BOLA and IDOR via sequential ID enumeration and active adjacent-ID probing. BFLA and privilege escalation are found through admin endpoint probing and role/permission field leakage. Property over-exposure, input validation issues like CORS wildcard usage, rate-limit header inconsistencies, and data exposure patterns including PII and API keys are also surfaced. Other categories include encryption misconfigurations, SSRF indicators, inventory issues, unsafe consumption surfaces, and LLM/AI security probes across multiple tiers.

OpenAPI analysis and authenticated scanning

middleBrick parses OpenAPI 3.0, 3.1, and Swagger 2.0 documents with recursive $ref resolution. It cross-references spec definitions against runtime findings to highlight undefined security schemes, sensitive fields, deprecated operations, and missing pagination. For authenticated scans, it supports Bearer tokens, API keys, Basic auth, and cookies. Domain verification is enforced through DNS TXT records or an HTTP well-known file, ensuring only the domain owner can scan with credentials. The scanner forwards a restricted set of headers, including Authorization, X-API-Key, Cookie, and X-Custom-*.

Product features and continuous monitoring

The Web Dashboard provides scan management, score trend tracking, and downloadable branded compliance PDFs. The CLI, available as an npm package, supports commands such as middlebrick scan <url> with JSON or text output. A GitHub Action can gate CI/CD pipelines, failing when the score drops below a defined threshold. The MCP Server enables scanning from AI coding assistants. Continuous monitoring in Pro tier includes scheduled rescans, diff detection for new and resolved findings, email alerts rate-limited to one per hour per API, and HMAC-SHA256 signed webhooks with auto-disable after five consecutive failures.

Safety posture and limitations

middleBrick adopts a read-only posture and never sends destructive payloads. Private IPs, localhost, and cloud metadata endpoints are blocked at multiple layers. Customer scan data is deletable on demand and purged within 30 days of cancellation. The tool does not fix, patch, block, or remediate issues. 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, blind SSRF relying on out-of-band infrastructure, or replace human pentesters for high-stakes audits. Its role is to detect and report findings with remediation guidance.

Frequently Asked Questions

Does middleBrick map findings to compliance frameworks?
Yes. It maps findings directly to PCI-DSS 4.0, SOC 2 Type II, and OWASP API Top 10 (2023). For other frameworks, it helps you prepare for audits by surfacing findings relevant to those controls.
Can it scan Hanami applications behind authentication?
Yes. Authenticated scans are supported with Bearer tokens, API keys, Basic auth, and cookies, provided domain verification is completed.
Is middleBrick suitable for continuous integration?
Yes. The GitHub Action can enforce score thresholds in CI/CD pipelines, and the CLI supports automated execution with machine-readable output.
Does the tool perform active exploitation like SQL injection?
No. It does not perform active SQL injection or command injection, as those require intrusive payloads outside the scanner's scope.
What happens to scan data after cancellation?
Customer scan data is deletable on demand and fully purged within 30 days of cancellation. It is never sold or used for model training.