Apigee for Enterprise organizations

What middleBrick covers

  • Black-box scanning with under one minute completion time
  • Risk scoring on A to F scale with prioritized findings
  • Authenticated scans with Bearer, API key, Basic, and Cookie
  • OpenAPI 3.0/3.1 and Swagger 2.0 spec-aware analysis
  • Continuous monitoring with scheduled rescans and diff detection
  • Integrations via dashboard, CLI, GitHub Action, MCP, and API

Overview for enterprise API programs

Apigee serves enterprise organizations as an API management layer and is often paired with security gateways and developer portals. From a security review standpoint, middleBrick operates as a black-box scanner that assesses runtime behavior without requiring code access or agents. In under a minute it returns a risk score on an A to F scale and a prioritized list of findings aligned to the OWASP API Top 10 (2023), enabling teams to compare current posture against common industry benchmarks.

Security coverage and mapping to frameworks

middleBrick scans for 12 security categories and maps findings directly to PCI-DSS 4.0, SOC 2 Type II, and OWASP API Top 10 (2023). Detection capabilities include authentication bypasses and JWT misconfigurations such as alg=none, weak key assumptions, and expired tokens; authorization flaws like BOLA and BFLA; over-exposed properties and mass-assignment surfaces; CORS wildcards and dangerous HTTP methods; rate-limit indicators and oversized responses; PII and sensitive data patterns including Luhn-validated card numbers and API key formats; HTTPS and HSTS misconfigurations; SSRF indicators involving internal IP probing; inventory issues such as missing versioning; unsafe consumption surfaces including webhook callbacks; and LLM/AI security probes spanning system prompt extraction, instruction override, and token smuggling.

Authenticated scanning and domain verification

With Starter tier and above, authenticated scanning supports Bearer tokens, API keys, Basic auth, and cookies. Before credentials are accepted, a domain verification gate confirms ownership via DNS TXT record or an HTTP well-known file, ensuring only the domain owner can submit authenticated scans. The scanner forwards a restricted allowlist of headers, including Authorization, X-API-Key, Cookie, and X-Custom-* headers, to minimize credential exposure while validating backend behavior.

OpenAPI and spec-aware analysis

middleBrick parses OpenAPI 3.0, 3.1, and Swagger 2.0 documents with recursive $ref resolution. It cross-references the spec definitions against runtime observations to highlight undefined security schemes, unexpected sensitive fields, deprecated operations, and missing pagination. This helps teams identify deviations between documented contracts and actual runtime behavior without requiring access to source code or internal repositories.

Continuous monitoring and integrations

Pro tier enables scheduled rescans at intervals of six hours, daily, weekly, or monthly, with diff detection to surface new findings, resolved issues, and score drift. Alerts are rate-limited to one email per hour per API and can be delivered via HMAC-SHA256 signed webhooks that auto-disable after five consecutive failures. The platform integrates into existing workflows through a web dashboard for report viewing and trend tracking, a CLI via the middlebrick npm package with JSON or text output, a GitHub Action that can fail builds when scores drop below a threshold, an MCP server for AI coding assistants, and a programmable API for custom integrations.

Scope, limitations, and data handling

middleBrick is a read-only scanner that does not modify, patch, or block systems. Destructive payloads are never sent, and private IPs, localhost, and cloud metadata endpoints are blocked at multiple layers. Scan data is deletable on demand and purged within 30 days of cancellation, and it is never sold or used for model training. The tool does not perform active SQL injection or command injection testing, does not detect business logic vulnerabilities that require domain understanding, does not identify blind SSRF without out-of-band infrastructure, and does not replace a human pentester for high-stakes audits. It surfaces findings relevant to compliance evidence and helps you prepare for audits, but it is not an auditor and cannot certify compliance.

Frequently Asked Questions

Can authenticated scans be run with CI/CD credentials?
Yes, authenticated scanning supports CI/CD credentials such as tokens and keys, provided the domain is verified through DNS or HTTP ownership proof. Only a restricted set of headers is forwarded to reduce risk.
How are false positives handled in the results?
Findings include contextual markers such as HTTP method, response codes, and response snippets to help triage. Teams can mark findings as resolved within the dashboard to refine future scans and reduce noise.
Does scanning require SDK installation or code changes?
No. middleBrick is a black-box scanner that requires no agents, SDKs, or code modifications. It works with any language, framework, or cloud environment by interacting with the public API surface.
Are compliance reports aligned with specific standards?
Reports map findings to PCI-DSS 4.0, SOC 2 Type II, and OWASP API Top 10 (2023). For other frameworks, the tool supports audit evidence collection and aligns with described security controls but does not certify compliance.