42Crunch for Platform engineers

What middleBrick covers

  • Black-box scanning with a risk score and prioritized findings
  • Detection aligned to OWASP API Top 10, PCI-DSS, and SOC 2
  • OpenAPI 3.0/3.1 and Swagger 2.0 parsing with $ref resolution
  • Authenticated scanning with header allowlist and domain verification
  • Continuous monitoring with diff detection and webhook alerts
  • Integrations including CLI, GitHub Action, MCP server, and API

Black-box scanning for platform teams

middleBrick is a self-service API security scanner that operates as a black-box tool. You submit a URL and receive a risk score from A to F with prioritized findings. The scanner uses only read-only methods such as GET and HEAD, and text-only POST where necessary for LLM probes. Scan completion typically occurs in under a minute, and no agents, SDKs, or code access are required. Because it does not rely on language-specific instrumentation, it works with any framework or cloud environment.

Detection aligned to industry standards

The scanner covers 12 security categories aligned to the OWASP API Top 10 (2023). Findings include issues in authentication, broken object level authorization, broken function level authorization, property authorization, input validation, rate limiting and resource consumption, data exposure, encryption, server-side request forgery, inventory management, unsafe consumption, and LLM/AI security. For compliance reporting, middleBrick 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 and supports audit evidence relevant to security controls described in regulations such as HIPAA, GDPR, ISO 27001, NIST, CCPA, and others.

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 behavior to identify undefined security schemes, sensitive field exposure, deprecated operations, and missing pagination. 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 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, you can schedule rescans every 6 hours, daily, weekly, or monthly. The system detects diffs between scans, highlighting new findings, resolved issues, and score drift. Alerts are rate-limited to one email per hour per API and can be sent via email, Slack, or Teams. HMAC-SHA256 signed webhooks are supported, with auto-disable after 5 consecutive failures. The tool integrates into existing workflows through a web dashboard, a CLI (middlebrick scan <url>), a GitHub Action that fails the build when the score drops below a threshold, an MCP server for AI coding assistants, and a programmable API for custom integrations.

Safety posture and limitations

middleBrick follows a read-only safety posture and never sends destructive payloads. Private IPs, localhost, and cloud metadata endpoints are blocked at multiple layers. Customer data can be deleted on demand and is purged within 30 days of cancellation. 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 testing, does not detect business logic vulnerabilities, and does not perform blind SSRF testing. It is not a replacement for a human pentester in high-stakes audits.

Frequently Asked Questions

What does the risk score from A to F represent?
The score summarizes the security posture of the API based on detected issues and their severity. Lower letters indicate stronger security, while higher letters indicate findings that require attention.
Can I scan APIs behind authentication using middleBrick?
Yes, authenticated scanning is supported from the Starter tier onward with Bearer, API key, Basic auth, and cookies. Domain ownership must be verified before credentials are accepted.
How are compliance mappings specified in reports?
Findings are mapped directly to PCI-DSS 4.0, SOC 2 Type II, and OWASP API Top 10 (2023). For other frameworks, reports highlight alignment and support audit evidence.
What happens to my scan data after I cancel?
Customer data is deletable on demand and is purged within 30 days of cancellation. It is never sold and is not used for model training.