Apigee for Backend engineers

What middleBrick covers

  • Black-box scanning with a risk score and prioritized findings
  • Detection aligned to OWASP API Top 10, PCI-DSS, and SOC 2
  • OpenAPI 3.x and Swagger 2.0 spec parsing with diff awareness
  • Authenticated scans with header allowlist and domain verification
  • Continuous monitoring with scheduled rescans and alerting
  • CI/CD integration via CLI, GitHub Action, and MCP server

API security posture for backend engineers

Backend engineers need a clear view of API risk that does not depend on changing application code. This scanner operates as a black-box tool, submitting only read-only methods and text-only POST probes to a target endpoint. You submit a URL and receive a risk score from A to F with prioritized findings. The approach works across languages, frameworks, and cloud providers without requiring agents, SDKs, or build pipeline changes.

Detection aligned to industry standards

The scanner evaluates APIs against three well defined frameworks, mapping findings to PCI-DSS 4.0, SOC 2 Type II, and OWASP API Top 10 (2023). It also aligns with security controls described in other regulations, helping you prepare audit evidence without claiming certification. Coverage includes authentication bypass, JWT misconfigurations such as alg=none or missing claims, BOLA and IDOR via sequential ID probing, BFLA through admin endpoint detection, and sensitive data exposure like API keys and PII patterns.

OpenAPI and spec driven analysis

The tool parses OpenAPI 3.0, 3.1, and Swagger 2.0 documents, resolving recursive $ref references and cross referencing definitions against runtime behavior. This highlights undefined security schemes, sensitive fields, deprecated operations, and missing pagination directly from the spec. Combined with read-only testing, the approach reduces noise while exposing configuration issues that often lead to excessive exposure or authorization gaps.

Authenticated scanning and safe execution

For endpoints that require identity, the scanner supports Bearer tokens, API keys, Basic auth, and cookies at the Starter tier and above. Domain verification is enforced through DNS TXT records or an HTTP well-known file so only the domain owner can submit credentials. The scanner enforces a strict header allowlist, forwarding only Authorization, X-API-Key, Cookie, and X-Custom-* headers. Safety measures include read-only methods only, blocking private IPs, localhost, and cloud metadata endpoints at multiple layers, and allowing data deletion on demand within 30 days of cancellation.

Continuous monitoring and integrations

Teams that need recurring assurance can use Pro tier features such as scheduled rescans every 6 hours, daily, weekly, or monthly. Findings are tracked with diff detection for new issues, resolved items, and score drift, with email alerts rate limited to one per hour per API. The tool integrates into existing workflows via a web dashboard, a CLI command like middlebrick scan <url> with JSON output, a GitHub Action that fails builds on low scores, an MCP server for AI coding assistants, and a programmable API for custom integrations.

Frequently Asked Questions

Can the scanner fix vulnerabilities automatically?
No. The tool detects and reports with remediation guidance, but it does not patch, block, or remediate issues.
Does it test for SQL injection or command injection?
No. Those tests require intrusive payloads and are outside the scope of this scanner.
Is it suitable for high-stakes audit requirements?
It supports audit evidence collection, yet it does not replace a human pentester for high-stakes assessments.
How are scan results stored and retained?