Alternatives to 42Crunch for DORA ICT risk evidence

What middleBrick covers

  • Black-box API scanning with under one minute scan time
  • Risk score A–F with prioritized findings
  • 12 categories aligned to OWASP API Top 10 (2023)
  • OpenAPI 3.x and Swagger 2.0 parsing with $ref resolution
  • Authenticated scanning with header allowlist and domain verification
  • Continuous monitoring with diff detection and webhook alerts

Purpose and scope for DORA ICT risk evidence

middleBrick is a self-service API security scanner designed to surface findings that support DORA ICT risk evidence. Submit a URL, receive a letter-grade risk score and prioritized findings. The scanner is black-box: no agents, no code access, and no SDK integration are required. It operates via read-only methods (GET and HEAD) and text-only POST for LLM probes, completing a scan in under a minute.

Detection aligned to major frameworks

middleBrick maps findings directly to three frameworks: PCI-DSS 4.0, SOC 2 Type II, and OWASP API Top 10 (2023). These mappings let you use findings as audit evidence for common compliance expectations. The scanner also helps you prepare for other security frameworks by aligning with security controls described in their requirements, while clearly noting that it does not certify or guarantee any compliance outcome.

Detection covers 12 categories, including Authentication bypasses, JWT misconfigurations such as alg=none and expired tokens, BOLA and IDOR via sequential ID enumeration, BFLA and privilege escalation through admin endpoint probing, sensitive data exposure including PII patterns and API key formats, input validation issues like CORS wildcard usage, rate-limiting and oversized response detection, encryption checks including HTTPS redirect and HSTS, SSRF probes against URL-accepting parameters, inventory issues such as missing versioning, unsafe consumption surfaces, and LLM / AI security adversarial probes across Quick, Standard, and Deep 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 findings to highlight undefined security schemes, sensitive fields, deprecated operations, and missing pagination. For deeper validation, authenticated scanning is available at Starter tier and above, supporting Bearer, API key, Basic auth, and Cookie credentials.

Authenticated scans require a domain verification gate, such as a DNS TXT record or an HTTP well-known file, ensuring only the domain owner can scan with credentials. The scanner forwards a restricted header allowlist limited to Authorization, X-API-Key, Cookie, and X-Custom-* headers.

Continuous monitoring and integrations

Pro tier enables scheduled rescans at intervals of 6 hours, daily, weekly, or monthly, with diff detection across scans to surface new findings, resolved findings, and score drift. Alerts are delivered via email at a rate-limited frequency of 1 per hour per API, and HMAC-SHA256 signed webhooks auto-disable after 5 consecutive failures.

The scanner integrates with common workflows through a Web Dashboard for scanning and report management, a CLI via the middlebrick npm package using middlebrick scan <url> with JSON or text output, a GitHub Action that fails the build when the score drops below a threshold, an MCP Server for use with AI coding assistants such as Claude and Cursor, and a programmatic API client for custom integrations.

Limitations and safety posture

middleBrick is a scanning tool and does not fix, patch, block, or remediate. It does not perform active SQL injection or command injection testing, does not detect business logic vulnerabilities, and does not detect blind SSRF due to the absence of out-of-band infrastructure. It is not a replacement for a human pentester in high-stakes audits.

The scanner follows a strict safety posture by using read-only methods only and blocking private IPs, localhost, and cloud metadata endpoints at multiple layers. Customer scan data is deletable on demand and purged within 30 days of cancellation; data is never sold and never used for model training.

Frequently Asked Questions

Does middleBrick map findings to HIPAA or GDPR?
middleBrick does not claim HIPAA or GDPR compliance. Findings may help you prepare for audits and align with security controls described in those frameworks, but the tool does not certify or guarantee any compliance outcome.
Can authenticated scans be run in CI?
Yes, authenticated scanning is supported from Starter tier onward. You must provide a domain verification record and limit headers to the allowlist; scans can be integrated into CI pipelines via the CLI, GitHub Action, or API client.
How often are scans performed with continuous monitoring?
Continuous monitoring supports scheduled rescans every 6 hours, daily, weekly, or monthly, with diff notifications and rate-limited email alerts.
What happens to scan data after cancellation?
Customer scan data is deletable on demand and fully purged within 30 days of cancellation. The data is not retained for model training or sold to third parties.
Does the scanner detect business logic flaws?
No. The scanner does not detect business logic vulnerabilities; these require human expertise that understands your domain and workflows.