APIsec for Education

What middleBrick covers

  • Black-box scanning with under one minute completion time
  • Risk scoring from A to F with prioritized findings
  • Detection aligned to OWASP API Top 10 (2023)
  • OpenAPI 3.x and Swagger 2.0 spec analysis
  • Authenticated scans with header allowlist and domain verification
  • Continuous monitoring with diff detection and alerts

Black-box API Security Scanning

middleBrick is a self-service API security scanner that operates as a black-box solution. You submit a URL and receive a risk score graded A through F, along with prioritized findings. The scanner uses only read-only methods, including GET and HEAD, plus text-only POST for LLM probes, and completes in under a minute. It requires no agents, no code access, and no SDK integration, making it applicable to any language, framework, or cloud environment.

Detection Coverage and OWASP Alignment

The scanner detects issues across 12 categories aligned to the OWASP API Top 10 (2023). It identifies authentication bypasses and JWT misconfigurations such as alg=none, HS256, expired tokens, missing claims, and sensitive data in claims. Other categories include BOLA and IDOR via sequential ID enumeration, BFLA and privilege escalation through admin endpoint probing, property authorization over-exposure, input validation issues like CORS wildcard usage, rate limiting header detection, data exposure including PII and API key formats, encryption misconfigurations, SSRF probes against URL-accepting parameters, inventory management gaps, unsafe consumption surfaces, and LLM security probes across tiered scan depths. For each finding, the tool maps findings to OWASP API Top 10 (2023) to help you validate controls.

OpenAPI Analysis and Authenticated Scanning

middleBrick parses OpenAPI 3.0, 3.1, and Swagger 2.0 definitions with recursive $ref resolution, cross-referencing spec definitions against runtime observations. This comparison highlights undefined security schemes, sensitive fields, deprecated operations, and missing pagination. Authenticated scanning supports Bearer, API key, Basic auth, and Cookie methods. Domain verification is enforced through DNS TXT records or an HTTP well-known file so that only the domain owner can scan with credentials. A strict header allowlist is applied, forwarding only Authorization, X-API-Key, Cookie, and X-Custom-* headers.

Product Integrations and Continuous Monitoring

The Web Dashboard provides a central location to view scans, track score trends, download branded compliance PDFs, and manage findings. The CLI, available as an npm package, supports commands such as middlebrick scan <url> with JSON or text output. A GitHub Action can gate CI/CD pipelines and fail builds when the score drops below a defined threshold. The MCP Server enables scanning from AI coding assistants like Claude and Cursor. For ongoing oversight, the Pro tier offers scheduled rescans at intervals ranging from every 6 hours to monthly, diff detection across scans, email alerts rate-limited to one per hour per API, and HMAC-SHA256 signed webhooks that auto-disable after 5 consecutive failures.

Safety Posture and Limitations

The scanner employs a read-only posture and never sends destructive payloads. Private IPs, localhost, and cloud metadata endpoints are blocked 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. 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, which falls outside its scope. Business logic vulnerabilities require human expertise, and blind SSRF is out of scope due to the lack of out-of-band infrastructure. The scanner does not replace a human pentester for high-stakes audits.

Frequently Asked Questions

What compliance frameworks does middleBrick map findings to?
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 audits and aligns with security controls described in relevant standards.
Can the scanner access internal or private APIs?
Access to private APIs depends on network reachability from the scanning location and proper domain verification for authenticated scans. The scanner enforces strict header allowlists and blocks private IPs at multiple layers.
How are scan results delivered and stored?
Results are available in the Web Dashboard and via CLI or API output. Scan data is stored only as long as needed to provide the service, and it is deleted on demand within 30 days of account cancellation.
Does the scanner test for SQL injection or command injection?
No. The scanner focuses on non-intrusive detection of misconfigurations and does not send payloads designed to exploit SQL injection or command injection vulnerabilities.
What happens when a scan identifies a new sensitive API key?
The finding is surfaced in the dashboard with remediation guidance. You can assign severity, add notes, and track remediation status as part of ongoing security management.