APIsec for Enterprise organizations

What middleBrick covers

  • Black-box scanning with under-one-minute results
  • 12 OWASP API Top 10 categories plus LLM adversarial probes
  • OpenAPI 3.x and Swagger 2.0 parsing with ref resolution
  • Authenticated scans with strict domain verification
  • CI/CD integration via GitHub Action and CLI
  • Continuous monitoring with diff and alerting

Scope and approach for enterprise assessment

Enterprises manage a large surface area of APIs across teams and clouds. This scanner performs a black-box assessment, requiring no agents, SDKs, or code access. You submit an API endpoint, and within a minute you receive a risk score and prioritized findings. The scan is read-only for standard methods plus text-only probes for LLM endpoints, ensuring no destructive payloads are ever sent.

Detection aligned to major frameworks

The scanner maps findings to three key frameworks: PCI-DSS 4.0, SOC 2 Type II, and OWASP API Top 10 (2023). Detection covers authentication bypasses, JWT misconfigurations such as alg=none and expired tokens, BOLA and IDOR via sequential ID probing, BFLA and privilege escalation attempts, over-exposed properties and mass-assignment surfaces, CORS wildcard misconfigurations, rate-limit header inconsistencies, and data exposure including PII patterns and API key leaks. For other frameworks, the tool helps you prepare for and aligns with security controls described in HIPAA, GDPR, ISO 27001, NIST, CCPA, NIS2, DORA, FedRAMP, DPDP, APPI, PDPA, PIPEDA, PIPA, UK DPA, LGPD, SOX, GLBA, FERPA by surfacing findings relevant to audit evidence.

Authenticated scanning and safety controls

Authenticated scans are available with Bearer tokens, API keys, Basic auth, and cookies, gated by domain verification using DNS TXT records or an HTTP well-known file to ensure only the domain owner can scan with credentials. The scanner forwards a restricted allowlist of headers and blocks private IPs, localhost, and cloud metadata endpoints at multiple layers. Customer data is deletable on demand and purged within 30 days of cancellation; it is never sold or used for model training.

LLM and OpenAPI specific analysis

The scanner parses OpenAPI 3.0, 3.1, and Swagger 2.0 definitions with recursive $ref resolution, cross-referencing spec definitions against runtime behavior to identify undefined security schemes, sensitive fields, deprecated operations, and missing pagination. For LLM security, it runs 18 adversarial probes across Quick, Standard, and Deep tiers, testing system prompt extraction, instruction override, DAN and roleplay jailbreaks, data exfiltration, cost exploitation, encoding bypasses, prompt injection variants, token smuggling, tool abuse, and nested instruction injection.

Products, integrations, and limitations

Deployment options include a Web Dashboard for scan management and trend tracking, a CLI via an npm package, a GitHub Action for CI/CD gating, an MCP Server for AI coding assistants, and a programmable API for custom integrations. Continuous monitoring on Pro tiers supports scheduled rescans, diff detection, email alerts, and signed webhooks. The scanner does not fix, patch, block, or remediate; it does not perform active SQL or command injection; it does not detect business logic vulnerabilities or blind SSRF; and it does not replace a human pentester for high-stakes audits.

Frequently Asked Questions

How does authenticated scanning work?
You provide credentials for Bearer, API key, Basic auth, or cookies. The scanner validates domain ownership through DNS TXT or a well-known file, then probes only safe methods with a restricted header allowlist.
What frameworks does the scanner map findings to?
Findings map directly to PCI-DSS 4.0, SOC 2 Type II, and OWASP API Top 10 (2023). Other frameworks are supported through alignment, not certification.
Can the scanner detect business logic or blind SSRF issues?
No. These require human-led testing and out-of-band infrastructure that are outside the scope of automated scanning.
What happens to scan data after cancellation?
Customer data is deletable on demand and fully purged within 30 days. Data is never sold or used to train models.
Does the scanner provide remediation fixes?
No. It detects and reports with guidance, but does not apply patches or modify your infrastructure.