APIsec vs Detectify

What middleBrick covers

  • Black-box API scanning with no agents or code access
  • Supports Bearer, API key, Basic auth, and cookie authentication
  • Maps findings to PCI-DSS 4.0, SOC 2 Type II, and OWASP API Top 10
  • LLM/AI security probes across Quick, Standard, and Deep scan tiers
  • OpenAPI 3.0/3.1 and Swagger 2.0 parsing with $ref resolution
  • Continuous monitoring with scheduled rescans and diff detection

Target audience and deployment model

Both tools position as scanner-first solutions for security and developer teams, but their deployment assumptions differ. Detectify operates as a SaaS probe that sends requests from its infrastructure and expects a reachable endpoint. middleBrick is a self-service scanner that runs from your execution context with no agents, SDKs, or code access. Black-box scanning supports any language, framework, or cloud, and only read-only methods are used.

Feature scope and detection coverage

Detectify focuses on common web and API misconfigurations and provides templated checks tuned for classic web attack chains. middleBrick maps findings to three frameworks: PCI-DSS 4.0, SOC 2 Type II, and OWASP API Top 10 (2023), and it explicitly limits scope to what can be observed without authentication or intrusive testing. Where Detectify covers standard web vulnerabilities, middleBrick adds OWASP API Top 10 categories such as authentication bypass, BOLA, BFLA, property authorization, unsafe LLM/AI probes across three depth tiers, and OpenAPI contract analysis that cross-references spec definitions against runtime behavior.

Authentication and scanning posture

Detectify supports standard web login flows and cookie-based sessions, with options to exclude administrative probes. middleBrick adds explicit support for Bearer tokens, API keys, Basic auth, and cookies, gated by a domain ownership verification step using DNS TXT records or an HTTP well-known file. Only a defined allowlist of headers is forwarded, and destructive payloads are never sent. Both tools limit intrusive testing, but middleBrick enforces read-only methods and blocks private IPs, localhost, and cloud metadata endpoints at multiple layers.

Integration, automation, and programmability

Detectify provides web dashboards and standard notifications for status tracking. middleBrick offers a broader integration surface: a CLI (middlebrick scan <url>) with JSON or text output, a GitHub Action that can fail builds based on score thresholds, an MCP server for AI coding assistants, and a programmatic API for custom workflows. Continuous monitoring in the Pro tier includes scheduled rescans, diff detection for score and finding changes, email alerts rate-limited to one per hour per API, and HMAC-SHA256 signed webhooks with auto-disable after repeated failures.

Pricing model and compliance framing

Detectify typically uses seat-based or scan-count pricing with a free tier for limited use. middleBrick uses a tiered model: Free for three scans per month and CLI access; Starter at $99 per month for 15 APIs, dashboard, email alerts, and MCP Server; Pro at $499 per month for 100 APIs with continuous monitoring, CI/CD gates, and compliance reports; Enterprise at $2,000 per month for unlimited APIs, custom rules, SSO, audit logs, and dedicated support. middleBrick maps findings to compliance evidence for PCI-DSS 4.0, SOC 2 Type II, and OWASP API Top 10, and it helps prepare for or supports audit evidence around other security frameworks without claiming certification or compliance guarantees.

Frequently Asked Questions

Can either tool perform active exploitation like SQL injection or command injection?
No. Both tools avoid intrusive exploitation. middleBrick explicitly does not perform active SQL injection or command injection, as those require payloads outside its scope.
Does either tool guarantee compliance with HIPAA, GDPR, ISO 27001, or other regulations?
No. Neither tool certifies or guarantees compliance. middleBrick may help you prepare for audits and supports evidence collection for frameworks such as PCI-DSS 4.0, SOC 2 Type II, and OWASP API Top 10.
How do the tools handle authentication during scans?
Detectify relies on session cookies or recorded login flows. middleBrick supports Bearer tokens, API keys, Basic auth, and cookies, with domain verification to ensure only the domain owner can scan with credentials.
What limits does each tool place on destructive testing?
Both tools operate read-only. middleBrick blocks private IPs, localhost, and cloud metadata endpoints and never sends destructive payloads.