Alternatives to APIsec on Rocket

What middleBrick covers

  • Black-box scanning with no agents or code access
  • Risk scoring from A to F with prioritized findings
  • 12 categories aligned to OWASP API Top 10 (2023)
  • OpenAPI 3.0/3.1 and Swagger 2.0 parsing with $ref resolution
  • Authenticated scanning with header allowlist controls
  • LLM adversarial testing across multiple scan tiers

Black-box scanning for any API stack

middleBrick is a self-service API security scanner that operates as a black-box solution. 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 source code, making it applicable to any language, framework, or cloud environment. Scan completion typically occurs in under a minute, using read-only methods such as GET and HEAD, with text-only POST allowed for LLM probes.

Coverage aligned to OWASP API Top 10

The scanner detects findings across 12 categories aligned to OWASP API Top 10 (2023). It identifies authentication bypasses and JWT misconfigurations such as alg=none, weak key selection, expired tokens, and missing claims. It probes for BOLA and IDOR via sequential ID enumeration and active adjacent-ID testing, and checks for BFLA and privilege escalation through admin endpoint discovery and role leakage. Additional categories include property authorization over-exposure, input validation issues like CORS wildcards and dangerous HTTP methods, rate limiting and resource consumption indicators, data exposure patterns including PII and API key formats, encryption misconfigurations, SSRF indicators, and inventory management gaps.

OpenAPI analysis and authenticated scanning

The tool parses OpenAPI 3.0, 3.1, and Swagger 2.0 documents with recursive $ref resolution, cross-referencing spec definitions against runtime observations to identify undefined security schemes, sensitive fields, deprecated operations, and missing pagination. Authenticated scanning is available from the Starter tier and above, supporting Bearer tokens, API keys, Basic auth, and cookies. Domain verification is enforced through DNS TXT records or an HTTP well-known file to ensure only domain owners can scan with credentials. A strict header allowlist limits forwarded headers to Authorization, X-API-Key, Cookie, and X-Custom-*.

Product capabilities and integrations

The Web Dashboard centralizes scan management, report viewing, score trend tracking, and branded compliance PDF generation. The CLI, distributed as an npm package, enables commands such as middlebrick scan <url> with JSON or text output. A GitHub Action provides CI/CD gating, failing builds when scores fall below configured thresholds. An MCP Server allows scanning from AI coding assistants, and a programmable API supports custom integrations. Continuous monitoring on the Pro tier offers scheduled rescans, diff detection across scans, email alerts, HMAC-SHA256 signed webhooks, and auto-disable after consecutive failures.

LLM security and safety posture

LLM / AI Security testing includes 18 adversarial probes across Quick, Standard, and Deep scan tiers. These cover system prompt extraction, instruction override, DAN and roleplay jailbreaks, data exfiltration attempts, cost exploitation, encoding bypass techniques, translation-embedded injection, few-shot poisoning, markdown injection, multi-turn manipulation, indirect prompt injection, token smuggling, tool abuse, nested instruction injection, and PII extraction. The scanner maintains a strict safety posture by using read-only methods only, blocking private IPs, localhost, and cloud metadata endpoints at multiple layers, and allowing customer data deletion on demand within 30 days of cancellation.

Mapping to compliance frameworks

middleBrick maps findings directly to PCI-DSS 4.0, SOC 2 Type II, and OWASP API Top 10 (2023). For other regulations, the tool helps you prepare for and aligns with security controls described in relevant frameworks, supporting audit evidence without asserting certification or compliance. Because it is a scanning tool, middleBrick does not fix, patch, block, or remediate issues, nor does it perform intrusive injection testing or replace a human pentester for high-stakes audits.

Frequently Asked Questions

Does the scanner perform active exploitation such as SQL injection?
No. The scanner focuses on detection and reporting using read-only methods and does not execute destructive or active injection payloads.
Can it authenticate to APIs using OAuth2?
Authenticated scanning supports Bearer tokens, API keys, Basic auth, and cookies. OAuth2 workflows are not natively handled.
How are false positives handled in findings?
Findings are prioritized by risk indicators observed during scanning. Manual review and contextual validation are recommended to confirm true positives.
Is sensitive customer data retained after a scan?
Customer scan data is deletable on demand and purged within 30 days of cancellation. Data is never sold or used for model training.