Burp Suite for Seed-stage startups

What middleBrick covers

  • Self-service black-box API security scanning under a minute
  • Risk score A–F with prioritized findings
  • Detection aligned to OWASP API Top 10, PCI-DSS 4.0, SOC 2 Type II
  • OpenAPI 3.x and Swagger 2.0 parsing with $ref resolution
  • Authenticated scanning with strict header allowlist
  • Continuous monitoring, diff detection, and webhook alerts

What this scanner is and how it works

This is a self-service API security scanner. You submit a URL and receive a risk score from A to F along with prioritized findings. It is a black-box scanner that requires no agents, no code access, and no SDK integration. It works with any language, framework, or cloud. Scan time is under a minute and the methods used are read-only (GET and HEAD) plus text-only POST for LLM probes.

Detection scope aligned to industry standards

The scanner detects issues in 12 categories aligned to the OWASP API Top 10 (2023). It maps findings to PCI-DSS 4.0 and SOC 2 Type II, and supports audit evidence for these frameworks. Detection areas include authentication bypass, JWT misconfigurations such as alg=none or expired tokens, BOLA and IDOR via sequential ID enumeration, BFLA and privilege escalation attempts, property over-exposure and mass-assignment surfaces, input validation issues like CORS wildcard usage, rate-limiting characteristics, data exposure including PII patterns and API key formats, encryption misconfigurations, SSRF indicators in URL-accepting parameters, and inventory management problems like missing versioning.

OpenAPI analysis and authenticated scanning

The scanner parses OpenAPI 3.0, 3.1, and Swagger 2.0 with recursive $ref resolution. It cross-references spec definitions against runtime findings to flag undefined security schemes, sensitive fields, deprecated operations, and missing pagination. Authenticated scanning is available from the Starter tier upward, supporting Bearer, API key, Basic auth, and Cookie credentials. Domain verification is enforced so only the domain owner can scan with credentials, and a strict header allowlist limits forwarded headers to Authorization, X-API-Key, Cookie, and X-Custom-*.

Continuous monitoring and integrations

With Pro tier and above, scheduled rescans run every 6 hours, daily, weekly, or monthly. Diff detection highlights new findings, resolved findings, and score drift between scans. Alerts are sent via email at a rate-limited pace of 1 per hour per API, and webhooks are HMAC-SHA256 signed with auto-disable after 5 consecutive failures. The tool integrates into existing workflows through a web dashboard for reports and score trends, a CLI via an npm package for on-demand scans, a GitHub Action that can gate CI/CD builds, an MCP Server for AI coding assistants, and a programmable API for custom integrations.

Limitations and safety posture

The scanner 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 detect blind SSRF that relies on out-of-band infrastructure. It is not a replacement for a human pentester in high-stakes audits. Safety measures include read-only methods only, blocking of private IPs, localhost, and cloud metadata endpoints at multiple layers, and a clear data policy where customer scan data is deletable on demand and never sold or used for model training.

Frequently Asked Questions

Can this scanner replace a penetration test?
No. It is a scanning tool that detects and reports issues with remediation guidance, but it does not replace a human pentester for high-stakes audits or business logic testing.
How does authenticated scanning work?
Authenticated scanning allows the use of Bearer, API key, Basic auth, and Cookie credentials after domain verification. Only specific headers are forwarded, and only the domain owner can scan with credentials.
What frameworks does it map findings to?
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 and supports audit evidence.
How often are scans performed with Pro tier?
Pro tier enables scheduled rescans every 6 hours, daily, weekly, or monthly, with diff detection and alerting.
Is sensitive data stored or used for model training?
No. Scan data is deletable on demand, purged within 30 days of cancellation, never sold, and never used for model training.