Is Apigee worth it?

What middleBrick covers

  • Black-box scanning with no agents or SDK dependencies
  • Detection aligned to PCI-DSS 4.0, SOC 2 Type II, OWASP API Top 10
  • Under-one-minute scans with prioritized risk findings
  • Authentication support for Bearer, API key, Basic, and cookies
  • Dashboard, CLI, GitHub Action, and MCP server options
  • Continuous monitoring with diff detection and alerts

Scope and approach compared to API security standards

middleBrick maps findings to PCI-DSS 4.0, SOC 2 Type II, and OWASP API Top 10 (2023) through its detection set. The scanner is a black-box tool that submits read-only requests to an API surface and returns a risk score with prioritized findings. It does not perform intrusive exploitation such as active SQL injection or command injection, and it does not test business logic in a domain-specific manner. For controls that require proof of configuration or runtime behavior, the scanner surfaces findings relevant to audit evidence but does not replace an auditor or a human pentester for high-stakes assessments.

Detection capabilities and runtime behavior

The scanner runs in under a minute and supports authentication via Bearer tokens, API keys, Basic auth, and cookies after domain verification. It uses read-only methods (GET and HEAD) plus text-only POST for LLM probes, and blocks private IPs, localhost, and cloud metadata endpoints at multiple layers. Detection categories include authentication bypass and JWT misconfigurations, broken object level authorization (BOLA/IDOR), broken function level authorization (BFLA/privilege escalation), property authorization exposure, input validation issues such as CORS wildcard usage and dangerous HTTP methods, rate limiting and resource consumption signals, data exposure including PII patterns and API key formats, encryption and transport misconfigurations, SSRF indicators, inventory and versioning issues, unsafe consumption surface, and LLM/AI security probes across Quick, Standard, and Deep tiers. The LLM testing includes system prompt extraction, instruction override, DAN and roleplay jailbreaks, data exfiltration attempts, token smuggling, and other adversarial techniques across defined tiers.

OpenAPI analysis and authenticated scanning constraints

The tool parses OpenAPI 3.0, 3.1, and Swagger 2.0 documents with recursive $ref resolution and cross-references spec definitions against runtime observations. This comparison can highlight undefined security schemes, sensitive fields, deprecated operations, and missing pagination. For authenticated scans, only a limited header allowlist is forwarded: Authorization, X-API-Key, Cookie, and X-Custom-* headers. Domain verification is enforced through DNS TXT records or an HTTP well-known file to ensure only the domain owner can submit credentials. These constraints keep the scan read-only but also limit the depth of stateful interaction that a full API contract might require.

Management, monitoring, and integration options

Results are accessed through a web dashboard that supports scan management, score trend tracking, and downloadable branded compliance PDFs. The CLI offers a straightforward command such as middlebrick scan <url> with JSON or text output. A GitHub Action can gate CI/CD, failing the build when the score drops below a set threshold. The MCP server enables scanning from AI coding assistants. For ongoing monitoring, the Pro tier provides scheduled rescans, diff detection across runs, email alerts rate-limited to one per hour per API, and HMAC-SHA256 signed webhooks that auto-disable after five consecutive failures. These features help integrate security checks into existing workflows without claiming to remediate issues automatically.

Pricing tiers and data handling

Free tier offers three scans per month and CLI access. Starter at 99 dollars per month supports 15 APIs, monthly scans, dashboard access, email alerts, and the MCP server. Pro at 499 dollars per month covers 100 APIs with additional APIs billed separately, continuous monitoring, GitHub Action gates, CI/CD integration, Slack and Teams alerts, compliance reports, and signed webhooks. Enterprise at 2000 dollars per month or more provides unlimited APIs, custom rules, SSO, audit logs, an SLA, and dedicated support. Customer scan data is deletable on demand and purged within 30 days of cancellation; data is never sold and is not used for model training.

Frequently Asked Questions

Is Apigee a good choice for teams that need deep, intrusive security testing?
No. The scanner is intentionally read-only and does not perform active SQL injection, command injection, or deep business logic exploitation. Teams requiring intrusive testing or deep logic reviews will still need a human pentester or specialized tools.
Who is Apigee worth it for in a comparison context?
It is worth considering for teams that need frequent, standardized scans across many public-facing APIs, want continuous monitoring without maintaining infrastructure, and require evidence aligned to PCI-DSS 4.0, SOC 2 Type II, and OWASP API Top 10. It is less suitable for organizations that rely on intrusive testing as part of their core security validation or that need certification-level guarantees.
What are the main limitations to keep in mind?
The tool does not fix or patch issues, only detects and reports with remediation guidance. It cannot detect blind SSRF or most business logic vulnerabilities, and it does not replace a human pentester for high-risk audits. Its read-only nature also limits deep stateful interactions with complex APIs.
How does the tool integrate into development pipelines?
It integrates via a CLI and a GitHub Action that can fail builds based on score thresholds. The Pro tier adds scheduled rescans and diff detection, while webhooks and email alerts support ongoing monitoring. These integrations focus on surfacing findings early rather than automating fixes.