Alternatives to 42Crunch on Spring Boot

What middleBrick covers

  • Black-box scanning with no agents or SDK dependencies
  • Risk scoring from A to F with prioritized findings
  • Detection aligned to OWASP API Top 10 (2023)
  • OpenAPI 3.0/3.1 and Swagger 2.0 parsing with spec-to-runtime comparison
  • Authenticated scans with header allowlist and domain verification
  • CI/CD integration via GitHub Action and MCP Server support

Black-box scanning for any stack

middleBrick is a self-service API security scanner that operates without agents, SDKs, or access to source code. You submit a target URL and receive a risk score from A to F with prioritized findings. Because it is black-box, it works with any language, framework, or cloud environment, including Spring Boot services.

Detection aligned to OWASP API Top 10

The scanner covers 12 categories aligned to OWASP API Top 10 (2023). It checks authentication bypasses and JWT misconfigurations such as alg=none, HS256 usage, expired tokens, missing claims, and sensitive data in claims. It probes BOLA and IDOR via sequential ID enumeration and active adjacent-ID probing, and BFLA and privilege escalation through admin endpoint probing and role/permission field leakage. Other categories include property authorization over-exposure, input validation issues like CORS wildcards and dangerous HTTP methods, rate limiting and resource consumption signals, data exposure including PII and API key formats, encryption and HTTPS hygiene, SSRF indicators, inventory issues such as missing versioning, unsafe consumption surfaces, and LLM/AI security probes across three scan tiers.

OpenAPI analysis and authenticated scanning

middleBrick parses OpenAPI 3.0, 3.1, and Swagger 2.0 with recursive $ref resolution, cross-referencing spec definitions against runtime behavior to surface undefined security schemes, sensitive fields, deprecated operations, and missing pagination. For authenticated scans on the Starter tier and above, Bearer, API key, Basic auth, and Cookie methods are supported. Domain verification is enforced through DNS TXT records or an HTTP well-known file so that only the domain owner can run authenticated scans. A strict header allowlist limits forwarded headers to Authorization, X-API-Key, Cookie, and X-Custom-*.

Continuous monitoring and integrations

With Pro tier, scans can be scheduled every 6 hours, daily, weekly, or monthly. Diff detection highlights new findings, resolved findings, and score drift between runs. Alerts are sent via email at a rate-limited frequency of 1 per hour per API, and HMAC-SHA256 signed webhooks disable automatically after 5 consecutive failures. The tool integrates into existing workflows through a web dashboard for reporting and trend tracking, a CLI via the middlebrick npm package, a GitHub Action that can fail CI/CD builds based on a score threshold, and an MCP Server for use with AI coding assistants. An API client enables custom integrations.

Limitations and scope

The 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, as those require intrusive payloads outside its scope. It does not detect business logic vulnerabilities, blind SSRF relying on out-of-band infrastructure, or replace a human pentester for high-stakes audits. Security findings should be validated within the context of your application and domain logic.

Frequently Asked Questions

How does the scanner validate API authentication during a scan?
Authenticated scans accept Bearer tokens, API keys, Basic auth, and Cookies. Domain ownership is verified through DNS TXT records or a well-known HTTP file before credentials are accepted.
Can the tool map findings to compliance frameworks?
Yes, findings map directly to PCI-DSS 4.0, SOC 2 Type II, and OWASP API Top 10 (2023). For other frameworks, it helps you prepare for and supports audit evidence related to security controls.
What happens to scan data after cancellation?
Customer scan data is deletable on demand and purged within 30 days of cancellation. Data is never sold and is not used for model training.
Does the scanner test for SQL injection or command injection?
No. The scanner focuses on API-specific issues and does not send intrusive payloads such as SQL injection or command injection tests.
How are false positives reduced in ongoing monitoring?
Ongoing monitoring uses diff detection across scans and rate-limited alerts to highlight meaningful changes in findings and score drift, reducing noise from transient issues.