When New LLM feature launching

What middleBrick covers

  • Black-box API scanning with under one minute scan time
  • 12 OWASP API Top 10 detection categories
  • OpenAPI 3.0/3.1 and Swagger 2.0 spec parsing
  • Authenticated scans with header allowlist and domain verification
  • LLM adversarial probing across Quick, Standard, and Deep tiers
  • Continuous monitoring with diff detection and email alerts

Assess your API before exposing new LLM features

When you expose new LLM features, you introduce new endpoints, prompts, and data flows that expand the attack surface. Run a black-box scan before enabling features in production to establish a baseline risk score and a prioritized list of findings. The scanner operates without agents or code access, returning results in under a minute using read-only methods and text-only LLM probes.

Detection coverage aligned to OWASP API Top 10

The scanner evaluates 12 categories aligned to OWASP API Top 10 (2023). It checks authentication bypass and JWT misconfigurations, including alg=none and expired tokens. It probes for BOLA and IDOR via sequential and adjacent ID enumeration, and BFLA via admin endpoint discovery and role leakage. Property over-exposure, input validation issues such as CORS wildcard usage, and rate-limiting characteristics are assessed. Data exposure checks for PII patterns, API key formats, and error leakage. SSRF probes target URL-accepting parameters, and LLM security includes 18 adversarial probes across Quick, Standard, and Deep tiers for system prompt extraction, jailbreaks, and data exfiltration.

OpenAPI spec validation and authenticated scanning

The scanner parses OpenAPI 3.0, 3.1, and Swagger 2.0 with recursive $ref resolution, cross-referencing the spec against runtime behavior. It flags undefined security schemes, deprecated operations, and missing pagination. For authenticated scans, provide Bearer tokens, API keys, Basic auth, or cookies. Access is gated by domain verification, and only a restricted set of headers is forwarded. These capabilities support continuous monitoring with scheduled rescans and diff detection to track score drift and new findings over time.

Compliance mapping and transparency

Findings map directly to PCI-DSS 4.0, SOC 2 Type II, and OWASP API Top 10 (2023). For other frameworks, the scanner helps you prepare for and supports audit evidence by surfacing findings relevant to controls described in those frameworks. The tool is a scanner only; it does not fix, patch, or remediate, and it does not replace a human pentester for high-stakes audits. Private IPs, localhost, and cloud metadata endpoints are blocked at multiple layers, and scan data is deletable on demand and never used for model training.

Integrations and safe delivery

Use the Web Dashboard to review reports and download branded compliance PDFs. The CLI supports a simple command like middlebrick scan <url> with JSON or text output. The GitHub Action can gate CI/CD, failing the build when the score drops below your threshold. The MCP server enables scanning from AI coding assistants. An API client allows custom integrations, and Pro tier adds Slack or Teams alerts with rate-limited notifications and HMAC-SHA256 signed webhooks that auto-disable after five consecutive failures.

Frequently Asked Questions

Can I scan APIs that require authentication?
Yes. Provide Bearer tokens, API keys, Basic auth, or cookies. Authentication is only used for read-only requests, and domain verification ensures only the domain owner can scan with credentials.
Does the scanner perform intrusive testing like SQL injection?
No. It uses read-only methods and text-only LLM probes. Destructive payloads are never sent, and active SQL injection or command injection is out of scope.
How are findings related to compliance frameworks?
Findings map directly to PCI-DSS 4.0, SOC 2 Type II, and OWASP API Top 10 (2023). For other regulations, the scanner helps you prepare evidence and aligns with security controls described in those frameworks.
What happens to my scan data after I cancel?
Customer data is deletable on demand and purged within 30 days of cancellation. Data is never sold and is not used for model training.