Is Invicti worth it?
What middleBrick covers
- Black-box scanning without agents or SDK dependencies
- Risk scoring on A–F scale with prioritized findings
- Detection aligned to OWASP API Top 10 (2023)
- Authenticated scans with strict header allowlists
- Continuous monitoring and diff tracking in Pro tier
- CI/CD integration via GitHub Action and MCP Server
Scope and approach of black-box scanning
The platform is a self-service API security scanner that submits a URL and returns a risk score on an A–F scale with prioritized findings. It operates as a black-box scanner, meaning it does not require agents, SDKs, or access to source code. It works across languages, frameworks, and cloud environments, and scans complete in under a minute. The scanner uses read-only methods, including GET and HEAD, plus text-only POST for LLM probes. Because it does not modify state or send destructive payloads, it is suitable for environments where intrusive testing is not permissible.
Detection coverage aligned to recognized standards
The scanner covers 12 categories aligned to the OWASP API Top 10 (2023), including Authentication bypass and JWT misconfigurations such as alg=none, HS256, expired tokens, missing claims, and sensitive data in claims. It identifies BOLA and IDOR via sequential ID enumeration and active adjacent-ID probing, and BFLA and privilege escalation through admin endpoint probing and role/permission field leakage. Additional categories include Property Authorization over-exposure, Input Validation issues like CORS wildcard configurations and dangerous HTTP methods, Rate Limiting and resource consumption detection, and Data Exposure for PII and API key formats. The tool also covers SSRF indicators, Inventory Management gaps, unsafe consumption surfaces, and LLM/AI Security probes across tiered scan depths.
For compliance framing, findings map directly to PCI-DSS 4.0, SOC 2 Type II, and OWASP API Top 10 (2023). For other frameworks, the scanner helps you prepare for and supports audit evidence, but it does not certify or guarantee compliance with HIPAA, GDPR, ISO 27001, NIST, CCPA, or similar regulations.
Authenticated scanning and safety controls
Authenticated scanning is available from the Starter tier and above, supporting Bearer tokens, API keys, Basic auth, and Cookies. Domain verification is enforced through a DNS TXT record or an HTTP well-known file, ensuring that only the domain owner can scan with credentials. The scanner forwards a restricted allowlist of headers, including Authorization, X-API-Key, Cookie, and X-Custom-* headers. Safety is designed into the process: only read-only methods are used, destructive payloads are never sent, and private IPs, localhost, and cloud metadata endpoints are blocked at multiple layers. Customer scan data is deletable on demand and purged within 30 days of cancellation, and it is never sold or used for model training.
Product integrations and continuous monitoring
The platform offers several integration options for different workflows. The Web Dashboard centralizes scans, report viewing, score trend tracking, and branded compliance PDF downloads. The CLI, distributed as an npm package, supports commands such as middlebrick scan <url> with JSON or text output. A GitHub Action acts as a CI/CD gate, failing the build when the score drops below a defined threshold. An MCP Server enables scanning from AI coding assistants such as Claude and Cursor. For ongoing risk management, the Pro tier provides scheduled rescans every 6 hours, daily, weekly, or monthly, diff detection across scans, email alerts rate-limited to one per hour per API, and HMAC-SHA256 signed webhooks that auto-disable after 5 consecutive failures.
Limitations and when to consider alternatives
This scanner does not fix, patch, block, or remediate findings; it detects and reports with remediation guidance. It does not perform active SQL injection or command injection testing, as those require intrusive payloads outside its scope. Business logic vulnerabilities are not detected, as they demand domain context that automated tools cannot replicate. Blind SSRF is out of scope due to the absence of out-of-band infrastructure, and the tool cannot replace a human pentester for high-stakes audits. If your primary need is active exploitation testing or deep business logic review, a dedicated manual assessment or specialized tools may be more appropriate.